Overview
When integrating Demodesk with automation tools like Make (formerly Integromat), it’s essential to understand the difference between webhook calls and API requests. Each serves a different role, and using the right one ensures you capture the data you need effectively.
1. Webhook Calls
What they are
Event-based notifications sent by Demodesk when something happens, like
recording.transcription_postprocessed.
How they work
You subscribe to an event, and Demodesk sends a payload containing key identifiers (e.g.,
recordingToken,demoToken) to your specified endpoint.
Limitations
Webhooks don’t include all available data fields.
Webhooks serve as triggers, not comprehensive data sources.
For full details on available webhook events and payload formats, see our API Reference.
2. API Requests
What they are
Direct queries to Demodesk’s API endpoints to retrieve all supported data.
Example
GET
/scheduled_demos/{demoToken}returns complete meeting properties including CRM IDs and custom fields.
Advantages
Full access to all available data.
Returns real-time information on demand.
When to use
When needed data isn’t part of the webhook payload.
When you want to retrieve or update details at runtime.
3. Common Pitfall in Make Integrations
A frequent issue: using the webhook module (e.g., "Watch Recording Transcription Postprocessed") alone in a scenario, then finding that key fields aren’t available later in the flow.
Solution:
Trigger on the webhook to capture
demoTokenorrecordingToken.Immediately follow with an API module that fetches complete meeting data.
Use returned fields (like
HubspotMeetingID,PrimaryAISummary) for downstream steps.
For a step-by-step setup in Make, check out our Make Integration Guide.
4. Example Flow in Make
Trigger Module: Webhook
recording.transcription_postprocessedAPI Module: GET
https://demodesk.com/api/v1/scheduled_demos/{demoToken}Use Output: Map full meeting details into further actions (CRM updates, emails, etc.)
5. Summary
Feature Type | Purpose | Best Use Case |
Webhook | Event alert + key IDs | Trigger automation flows |
API Request | Fetch full dataset | Retrieve missing or custom data |
Recommended Strategy | Webhook + API combo | Best for complete, reliable integrations |