Make.com

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 → Webhook Management
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"), up to 100 characters
7. Under Event Settings, pick the one event this webhook sends — Send call logs, Send call recordings, or Send notes
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 custom webhook, Make receives a JSON envelope you can map to any module:

{
  "id": "unique-event-id",
  "type": "call.completed",
  "timestamp": "2024-01-15T10:30:00Z",
  "organizationId": "your-org-id",
  "data": { "callSid": "call-id", "direction": "inbound", "fromNumber": "+15551234567", "toNumber": "+15559876543", "phoneNumber": { "id": "phone-number-id", "number": "+15559876543" }, "status": "completed", "duration": 180 }
}

The type tells you which event fired, and the data object holds the details for that event:

• call.completed — direction (inbound/outbound), from/to numbers, status, and duration in seconds
• call.recording.completed — the same call fields plus the recording URL and AI transcription summary
• note.created — the note content, the related contact, and the team member who wrote it

You can reference any of these fields in later modules. For example, pull data.fromNumber (the caller's number on an inbound call) to look up a contact, or drop data.duration into a formatted Slack message. Note data.phoneNumber is an object ({ id, number }) for the dialnote line, not the caller—use data.fromNumber / data.toNumber for the actual numbers.

For the full payload reference and signature details, see the Webhooks guide.

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 → Webhook Management and re-enable it once you've fixed the cause.
• 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: Each webhook sends a single event. A "Send call logs" webhook won't fire for recordings — create a separate "Send call recordings" webhook for that.
• Slow endpoint: Your scenario must accept the payload within 30 seconds, or dialnote counts it as a failure.

Each webhook card in Settings → Webhook Management shows the last delivery time, consecutive failure count, and the most recent error message.

What's Next#

• Webhooks — full payload reference, signature verification, and webhook management
• Zapier — a built-in, no-code path to 5,000+ apps
• n8n — another visual automation tool that accepts dialnote webhooks
• CRM integrations — push call activity to HubSpot, Salesforce, or Pipedrive without a custom endpoint