Demodesk Make integrationAutomate Demodesk with Make.
What should happen the moment a sales meeting ends? The Demodesk Make integration gives you 10 instant triggers and 1 API module. This guide is for sales and revenue ops teams: connect your account, then build a first scenario step by step.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Demodesk Make integration do for you?
The Demodesk Make integration links your Demodesk account to Make, a no-code tool where you build scenarios (automations made of modules, one brick per step). Demodesk warns Make the moment a meeting or a recording changes, and Make passes that information to the rest of your stack.
Follow-ups that start on their own. With Watch Meeting Ended, a scenario runs as soon as a call wraps up. The next module can open a task in your project board or write a line in your CRM, so no rep has to remember the after-call chores.
Transcripts where people read them. Watch Recording Transcription Postprocessed fires once Demodesk has finished processing a transcript. That is the right moment to send the text to a shared document or to the deal record, instead of hunting for it later.
A calendar your team can trust. Watch Meeting Rescheduled, Watch Meeting canceled and Watch Meeting Handovered cover the changes that usually slip through: a new time, a lost slot, a different host. Each one can alert the right channel.
Know the limits before you start. Make's documentation for Demodesk is marked as limited, and the catalog lists no ready-made action besides Make an API Call. Anything outside the 10 triggers goes through that module and the Demodesk API. If you are weighing tools, the same app often exists as an n8n node too: our n8n vs Make comparison lays out the criteria. New to the editor? The Make training starts from the basics, and the Make pricing page explains how operations are counted.
How do you connect Demodesk to Make?
- 01
Add a Demodesk module
In a scenario, search for Demodesk and pick any module, for example Watch Meeting Ended. In the module panel, click Create a connection. The connection is your Demodesk account linked to Make once, then reused by every Demodesk module.
- 02
Name it and authorize Make
Give the connection a name if you manage several accounts (it is optional). Then authorize Make on the Demodesk page that opens, or paste the key Demodesk gives you, depending on what the window asks for.
- 03
Save and check
Click Save. The connection now shows in the module's dropdown, and any other Demodesk module you add later will offer it too, with no need to sign in a second time.
Your first scenario with Demodesk
GoalWhen a meeting ends in Demodesk, Make receives it instantly, then uses Make an API Call to fetch from Demodesk the related data the trigger does not carry.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + to place the first module. That first module is the trigger: the event that starts everything.
- 02
Place Watch Meeting Ended
Search for Demodesk, choose Watch Meeting Ended and pick the connection you created. It is an instant trigger, so Demodesk calls Make through a webhook as soon as a meeting closes.
- 03
Add Make an API Call
Click the + on the right of the trigger and add Make an API Call. It reuses your connection. Map the meeting data from the trigger into the request you need.
- 04
Test with Run once
Click Run once, then end a test meeting in Demodesk. Open each module to read the bundles it received: that is where you learn which details Demodesk actually sends.
- 05
Switch it on
When the test looks right, save and switch the scenario on. From then on, every finished meeting starts one run, and each module it passes through counts as an operation on your plan.
Which Demodesk events can start a scenario?
10 modules start a scenario when something happens in Demodesk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Demodesk as soon as it happens.
Watch Meeting Call Note Updated
Instant triggerIn Make“Triggers when a meeting's call not is updated”
Your scenario learns that someone edited the call note of a meeting, so the latest version of those notes can travel to where your team works. Each update arrives as one bundle, one item passed to the next module.
Watch Meeting canceled
Instant triggerIn Make“Triggers when a meeting is canceled”
This trigger tells Make that a meeting was called off, which lets you free the slot, warn a manager or reopen a lead before anyone notices the gap by accident.
Watch Meeting Ended
Instant triggerIn Make“Triggers when a Meeting Ends.”
Here is the cleanest starting point for after-call work: the scenario runs as soon as a meeting is over, with the meeting details in the bundle, ready for the next modules.
Watch Meeting Event Response Changed
Instant triggerIn Make“Triggers when an attendee's event response to the calendar event changes”
You get notified when an attendee changes their answer to the calendar invitation, so a declined or accepted invite never goes unnoticed before the call.
Watch Meeting Handovered
Instant triggerIn Make“Triggers when a meeting is handed over to a different host”
Make hears about it whenever a meeting moves to a different host, which keeps ownership clear when an SDR passes a booked call to an account executive.
Watch Meeting Rescheduled
Instant triggerIn Make“Triggers when a meeting is rescheduled”
When a meeting moves to a new date or time, this trigger passes the change to Make, so reminders, prep tasks and internal calendars stay aligned with what the prospect agreed to.
Watch Meeting Scheduled
Instant triggerIn Make“Triggers when a meeting is scheduled”
Every newly booked meeting can start a scenario, which is the natural entry point for anything that should happen before the call: prep work, a CRM activity, a heads-up to the team.
Watch Meeting Started
Instant triggerIn Make“Triggers when a meeting has started”
This one reacts when a meeting actually begins, not when it is booked, so your scenario works from calls that really took place.
Watch Recording Transcription Postprocessed
Instant triggerIn Make“Triggers when the transcription of a recording finished post-processing”
The scenario waits until Demodesk has finished processing the transcript of a recording, so the text you pass on is the final one, ready to be stored, shared or summarized by another app.
Watch Recording Uploaded
Instant triggerIn Make“Triggers when a recording for one of your meetings is uploaded”
Make is told as soon as a recording of one of your meetings is available, which lets you share the replay or archive it without waiting for anyone to go looking.
What else can Make do in Demodesk?
Demodesk gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This module opens the whole Demodesk API to your scenario, with the connection you already have, so you are not stuck with the triggers alone when you need to read or change something in Demodesk.
Need help automating Demodesk with Make?
A person reads every message.
