With Make, you can visualize, design, and automate your work. Use an easy drag-and-drop principle to create your integrations; they can be as simple or complex as you want them to be.
This article will cover everything you need to know to automate your workflows with Demodesk:
What is Make?
Make is a tool that helps you automate manual processes without needing code. The software makes it easy for you to connect apps and services.
So instead of needing a developer to write the code to link different actions, Make provides blocks that can be connected with a simple drag-and-drop. These blocks are called ‘Modules’, and the visual connections between them are ‘Scenarios’.
Once set up, Make runs 24-7, processing in the background with no maintenance required.
Make differentiates between different types of modules; the following ones are the most common modules:
Action Modules: A module that does something, like send an email, a Slack message, or create a document.
Search Modules: This module takes a search, and then returns the results. For example, get all your contacts called ‘John’ (if you want!)
Trigger Modules: Triggers run when data is updated. Make watches an app, then takes action when something happens. For example, when a new meeting is booked, your workflow could trigger.
What triggers the actions?
As mentioned in the section above, a trigger module is a module that takes action when a predefined event happens. These actions are API calls, and you can again choose one of the predefined blocks that Make provides.
But again, we distinguish between different types;
Instant triggers: Starts executing a scenario immediately after a given app or service sends information to Make about an event that occurred
Scheduled triggers: Asks a given app or service at regular intervals if new data is available. An example of such a service is email.
A key advantage of the instant triggers, compared to the scheduled ones, is that they save operations. With instant triggers, Make gets notified about new events and does not have to ask an application or a service repeatedly if there is new data available.
Uses Cases
You can use Make with Demodesk in a lot of different ways; here are some recommendations from our side:
Trigger actions from external apps to Demodesk:
Before a meeting:
New meetings: create a workflow such that whenever a meeting in your external app is booked, it will automatically show up in Demodesk as well
Change meetings: connect the external app such that changes will be adjusted in the Demodesk meeting as well (e.g., different guests)
Trigger actions from Demodesk to external apps:
Before a meeting:
New meetings: inform your team whenever a new meeting is booked, e.g, send a slack message when someone books a meeting on your homepage
Change meetings: automatically update the external app when you need to change something in your Demodesk meeting
Meeting rescheduled: update your external tools or notify stakeholders of the new time
During a meeting:
When a meeting starts: send out last-minute reminders to your team, e.g., via slack
When a meeting ends: create follow up actions
After a meeting:
Upload of a recording: automatically inform your team whenever you recorded an important meeting
Transcription finished: share the transcript with your team or store it in your internal documentation once the transcription is ready
Call notes updated: update CRM records or send a Slack notification whenever the meeting’s call note is changed
Meeting handed over: notify the new host or update ownership in external tools when a meeting is handed over to a different user
Meeting canceled: remove the canceled meeting from external tools or notify attendees
Event response changed: track RSVP changes in your CRM or reporting dashboards
FAQs
How can I get the meeting transcript using the recording token (after a webhook event)?
How can I get the meeting transcript using the recording token (after a webhook event)?
You can retrieve the transcript by making a GET request using the recording token (not the demo ID).
Make sure to:
Use the following URL structure:
/v1/recordings/{recording_token}/transcriptSet the HTTP method to
GETInclude the Accept header with value
text/plain
Example setup (in Make or custom API client):
GET /v1/recordings/20d3c4315a21f6ee/transcript
Accept: text/plain
This returns the transcript in plain text format after the postprocessing is complete.