Skip to main content

What this integration does

The Allo-Make integration lets you build powerful custom workflows using your call data. Connect Allo to thousands of apps and services through Make’s visual automation platform. Perfect for teams that need custom integrations beyond standard CRM sync. Key benefits:
  • Custom workflow automation
  • Connect Allo to 1000+ apps
  • Use call data to trigger actions
  • No coding required
Make (formerly Integromat) is a no-code automation platform. You’ll need a Make account (free tier available).

Setup

Get your Allo webhook URL

1

Create Make account

Sign up at make.com (free tier available)
2

Create new scenario

Click Create a new scenario
3

Add webhook trigger

  1. Click the + button
  2. Search for Webhooks
  3. Select Custom webhook
4

Create webhook

Click Create a webhook and give it a name like “Allo Calls”
5

Copy webhook URL

Make generates a unique webhook URL. Copy it.

Connect Allo to Make

1

Open Allo app

Launch Allo on mobile or desktop
2

Go to Integrations

Navigate to Settings > Integrations
3

Find Make

Locate Make in the integrations list and tap Connect
4

Paste webhook URL

Enter the webhook URL you copied from Make
5

Select events

Choose which events to send:
  • Calls - Call recordings and summaries
  • SMS - Text messages
  • Contacts - Contact changes
  • All events - Everything (recommended for testing)
6

Save and test

Tap Save. Make a test call to verify the connection.
After your first call, return to Make and click Determine data structure to see available call data fields.

How it works

https://mintcdn.com/themobilefirstcompany/4JKVqOLduvlaK6pG/media/integrations/Allo.png?fit=max&auto=format&n=4JKVqOLduvlaK6pG&q=85&s=de5eaa45a01e052c9506804098dbb8ce

Event triggers

Allo sends webhook events to Make when calls, SMS, or contact changes occur.
https://mintcdn.com/themobilefirstcompany/uKjDJQBHEPpQWHkX/media/integrations/Make.svg?fit=max&auto=format&n=uKjDJQBHEPpQWHkX&q=85&s=21cf8f58284c278bf14b5f691b59e7c8

Custom actions

Build workflows with Make’s visual editor to process Allo data.
https://mintcdn.com/themobilefirstcompany/uKjDJQBHEPpQWHkX/media/integrations/Make.svg?fit=max&auto=format&n=uKjDJQBHEPpQWHkX&q=85&s=21cf8f58284c278bf14b5f691b59e7c8

Multi-app automation

Connect Allo to any of Make’s 1000+ supported apps.
https://mintcdn.com/themobilefirstcompany/4JKVqOLduvlaK6pG/media/integrations/Allo.png?fit=max&auto=format&n=4JKVqOLduvlaK6pG&q=85&s=de5eaa45a01e052c9506804098dbb8ce

Data transformation

Use Make’s tools to filter, format, and transform call data.

Available data

When Allo sends a webhook to Make, you receive: Call events:
  • Call ID
  • Contact name and phone number
  • Call direction (inbound/outbound)
  • Call duration
  • Call timestamp
  • Call outcome (answered, voicemail, missed)
  • Recording URL
  • Transcript text
  • AI summary
  • Contact tags
SMS events:
  • Message ID
  • Sender and recipient
  • Message text
  • Timestamp
  • Direction (sent/received)
Contact events:
  • Contact ID
  • Name and phone number
  • Email address
  • Tags and notes
  • Event type (created, updated, deleted)

Example workflows

Log calls to Airtable

  1. Trigger: Allo call webhook
  2. Action: Create record in Airtable
  3. Map fields: Call data to Airtable columns

Send Slack notifications

  1. Trigger: Allo call webhook
  2. Filter: Only calls over 10 minutes
  3. Action: Send Slack message to sales channel

Create Trello cards

  1. Trigger: Allo call webhook
  2. Filter: Missed calls only
  3. Action: Create Trello card with callback task

Update Google Sheets

  1. Trigger: Allo call webhook
  2. Action: Add row to Google Sheet
  3. Include: Call summary and recording link

Multi-step automation

  1. Trigger: Allo call webhook
  2. Action 1: Log to Airtable
  3. Action 2: Send email summary
  4. Action 3: Create task in Asana
  5. Action 4: Post to Slack

What syncs

  • Allo to Make
  • Make to Allo
From Allo to Make:
  • All call events with complete metadata
  • Call recordings (URL links)
  • Call transcripts (full text)
  • AI summaries
  • SMS messages (sent and received)
  • Contact changes (create, update, delete)
  • Custom event data

Troubleshooting

Common causes:
  • Webhook URL copied incorrectly
  • Scenario not activated in Make
  • Wrong events selected in Allo
Solutions:
  • Verify the full webhook URL in both Make and Allo
  • Make sure your Make scenario is turned ON
  • Select “All events” in Allo for testing
  • Make a test call to trigger the webhook
How to fix:
  1. Make sure integration is connected in Allo
  2. Make a test call or send a test SMS
  3. Return to Make and click Determine data structure
  4. Make will capture the data fields automatically
Check execution history:
  1. Open your scenario in Make
  2. Click on the scenario name to see execution history
  3. Review error messages for failed runs
  4. Common issues: missing field mappings, API limits, authentication errors
Verify access:
  • Recording URLs require authentication
  • Use Make’s HTTP module to fetch recordings with proper headers
  • Contact Allo support for recording access instructions
Free tier limits:
  • 1,000 operations/month
  • 15-minute scenarios max
Solutions:
  • Upgrade to paid Make plan
  • Add filters to reduce operations
  • Combine multiple actions into fewer operations
To reconnect the integration:
  1. In Allo: Go to Settings > Integrations > Make
  2. Tap Disconnect
  3. Generate a new webhook in Make
  4. Follow connection steps with new URL

Manage your integration

Disconnect Make

To disconnect the integration:
  1. Open Allo app
  2. Go to Settings > Integrations
  3. Select Make
  4. Tap Disconnect
Disconnecting stops webhook events to Make. Your Make scenarios will no longer receive Allo data.

Update webhook URL

If you need to change the webhook URL:
  1. Create a new webhook in Make
  2. Disconnect the Make integration in Allo
  3. Reconnect with the new webhook URL

Multiple webhooks

To send Allo data to multiple Make scenarios:
  1. Create multiple webhook connections in Allo
  2. Each can have different event filters
  3. Build separate workflows for different purposes

Need help?