Make (formerly Integromat) is a visual automation platform that connects dialnote to 2,200+ apps. You can build multi-step workflows—called scenarios—that trigger whenever a call finishes, a recording is ready, or a note gets created. It's a great fit if you want branching logic, data transformation, or more complex automations than simple point-to-point connections.

Connecting dialnote to Make#

dialnote connects to Make through webhooks. You'll set up a webhook in Make that receives real-time data from dialnote whenever events occur.

Here's how to get started:

1. In Make, create a new scenario and add a Webhooks module as your trigger
2. Choose Custom webhook and click Add to generate a unique webhook URL
3. Copy that URL
4. In dialnote, go to Settings → Webhooks
5. Click Add Webhook and choose Custom Webhook as the provider
6. Paste the Make webhook URL and give it a name (e.g., "Make - Call Automation")
7. Select which events should fire: call.completed, call.recording.completed, or note.created
8. Save the webhook

Building Your First Scenario#

Once the webhook module receives data, you can add any combination of actions and logic. Make's visual editor lets you drag modules onto a canvas and connect them.

Example: Log Calls to Google Sheets and Notify Slack#

This scenario does two things when a call ends: adds a row to a spreadsheet and pings a Slack channel.

1. Trigger: Webhooks → Custom webhook (receives dialnote call data)
2. Route 1: Google Sheets → Add a Row (map caller number, duration, status, timestamp)
3. Route 2: Slack → Create a Message (post a summary to your #calls channel)

Use Make's Router module to split the data into parallel paths. Both actions run at the same time, so there's no delay.

Example: Create CRM Contact After Call#

If a caller isn't already in your CRM, you can auto-create them:

1. Trigger: Webhooks → Custom webhook
2. Filter: Only proceed if call direction is "inbound"
3. Search: HubSpot → Search Contacts by phone number
4. Router: If no match found → HubSpot → Create Contact with the caller's number and name

Make's built-in filters save you from creating duplicate contacts. You can add conditions like minimum call duration or specific phone numbers to narrow what triggers downstream actions.

Available Webhook Data#

When dialnote fires a webhook, Make receives JSON data you can map to any module. The fields depend on which event you selected:

call.completed sends: call ID, direction (inbound/outbound), from/to phone numbers, caller names, duration in seconds, call status, and a timestamp.

call.recording.completed sends: all call fields plus the recording URL and AI-generated transcription summary.

note.created sends: the note content, associated contact info, and the team member who wrote it.

You can reference any of these fields in subsequent modules. For example, use the from_number field to look up a contact, or include duration in a formatted Slack message.

Popular Automation Ideas#

Make's strength is multi-step logic. Here are workflows dialnote users build:

• Smart follow-ups: Call ends → check if it lasted under 30 seconds → if yes, send an SMS follow-up via Twilio saying "Sorry we missed you"
• Lead scoring: New call recording → send transcription to OpenAI for sentiment analysis → update lead score in your CRM
• Ticket creation: Missed call → create a support ticket in Jira or Linear with the caller's details
• Daily digests: Schedule a daily scenario that pulls call stats from a Google Sheet (populated by another scenario) and emails a summary to your team

Troubleshooting#

If your Make scenario isn't receiving data, check these common issues:

• Webhook paused in dialnote: After 3 consecutive delivery failures, dialnote auto-disables the webhook. Go to Settings → Webhooks and re-enable it.
• Scenario turned off in Make: Make won't process incoming webhooks if the scenario is inactive. Toggle it on in the scenario editor.
• Wrong event selected: Double-check that you've enabled the right events on the dialnote webhook. A call.completed webhook won't fire for recordings—you need call.recording.completed for that.

You can view delivery history for each webhook in dialnote's Settings to spot failures and see exact error messages.