You can integrate Claap with your existing tools thanks to webhooks. These enable seamless automations by sending meeting data directly to other apps or automation platforms like Zapier, Make, or n8n. With Claap’s webhooks, you can automatically send meeting summaries, action items, key insights, and more, to your team's preferred tools.
What are webhooks?
A webhook is a way for one app to immediately and automatically notify another app when something important happens - kind of like how your phone sends you a notification when you get a new message. Instead of you having to constantly check for updates, the app sends an instant alert with the relevant information to wherever you want it to go. With Claap, webhooks can notify another app when a new meeting recording is added to your Library, or when a meeting recording is updated.
Webhook setup
Please contact support@claap.io to register a webhook for your workspace.
In your request, please provide:
The destination URL you would like to connect (if you intend to use Zapier or any other automation platform, please see below how to retrieve your destination URL)
The event triggers you would like to register to
Create your automation with Zapier (or Make, n8n, ...)
Automation platforms like Zapier, Make or n8n help you connect Claap to thousands of other applications.
⚠️ In the steps below we will use Zapier to create an automation, but these steps would be similar when using other automation platforms.
Generate the destination URL
Log in to your Zapier account and click on Create Zaps
Click on Trigger and search for and select Webhooks by Zapier
For Event choose Catch Hook and click on Continue.
Leave the Child Key empty
Copy the Webhook URL: Zapier will generate a webhook URL. This is your destination URL. Copy it and include it as part of your request to support@claap.io.
Tutorial
Here is a short video tutorial covering the setup of a Zapier automation which uses channel filters, the transcript, OpenAI prompts, and connects to Notion:
Accessing and using meeting information in your automation steps
Any meeting information included in the payload can be extracted and used as variables in your automation steps. Available information includes details such as title, date, channel, participants, action items, company and deal information, insights, etc.
You can use any of these as dynamic variables to filter which meetings you want your automation to process, or simply to use them in any action step or to export them to connected apps.
The complete list of fields available in the payload for a meeting is provided here: Claap Webhooks & API documentation
To have a glimpse at some simple automations you can create with your automation platform, check out Ways to use Claap webhooks.
Retrieving the transcript for a meeting
If you need to use the meeting transcript in your automation, you will need to retrieve it first with a specific automation step.
In Zapier, you will need to first extract the transcripts.url from the payload, and then add a specific step which will fetch the transcript itself from the extracted URL:
Add a Run Python step with the Code by Zapier app
In the Configure tab, select the transcript url as your Input Data
Add the following snippet of code in the Code section:
import requests
url = input_data.get(‘url’, ‘’)
# Send a GET request to the specified URL
try:
response = requests.get(url)
response.raise_for_status() # Raise an error for bad responses
# Get the text content from the response
output = {‘text’: response.text}
except requests.RequestException as e:
# Handle any request exceptions and return an empty output
output = {‘error’: str(e)}This step will then output the transcript as a new dynamic variable which you can use in the next steps of your automation.
Create your automation with your own destination endpoint
You can set up your own service endpoint which will receive webhooks from Claap directly.
Check out the Claap Webhooks & API documentation for details about the webhook, entities schema, and event triggers in order to setup your endpoint so it can successfully handle Claap webhooks.