Allo Zapier integrationAutomate Allo with Zapier.
The Allo Zapier integration gives you 11 triggers, 11 actions and 8 searches, and all 11 triggers are instant. Calls, SMS, contacts, companies and the Power Dialer queue: what each operation does, what it costs you and where it trips people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Allo Zapier integration really does for your phone line
It links your Allo business phone account to the rest of your tools, without code. A call ends, an SMS comes in, a contact changes in the Allo CRM: Zapier hears about it and passes it on. Or the other way round: something elsewhere creates a person, tags a call, sends a text or feeds numbers into the Power Dialer.
Three results worth building first. A calling list that fills itself: Contact Created starts the Zap and Add Numbers to Power Dialer drops the number into the queue, so your reps open the dialer and the new lead is already there. Calls sorted without anyone clicking: Call Completed reports the finished call and Add Tags to Call labels it, which in turn can wake a second Zap on Tag Added. A text that goes out on its own: Send SMS (US) writes to a US number from one of your Allo lines, whatever app started the Zap.
Now the limits nobody spells out. The two SMS actions only reach French or US numbers: there is no generic send-anywhere action. Nothing in the catalog places a call for you either; the closest thing is loading numbers into the Power Dialer queue. And no action deletes a person or a company, so cleanup stays manual.
Shopping around? The same breakdown exists for the Allo Make integration, written to the same rules, so you can compare both line by line.
Zapier words you will meet on this page
Eight terms, plain English, then the page uses them without repeating the definition.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for exactly that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app such as Allo.
- Task
- The unit Zapier bills you for: one action that your Zap completes successfully. Your plan's monthly count is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming item matches the condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found, like an ID.
- Connection
- Your Allo account linked to Zapier once, then reused by every step of every Zap that touches Allo, with no new sign-in.
What Allo on Zapier costs you in tasks
Short version: the trigger is free, every action that works is billed, and Allo itself is not a premium app, so it runs on the free plan.
- TriggerFree, never counted as a task
- Action that works1 task each
- Action that failsNot counted
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, Allo works on the free plan
A call or an SMS coming in costs nothing; only a completed action counts as a task. An action that fails is not billed. A Zap with three actions eats three tasks per run. The free plan gives you 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and it becomes a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers, and Allo has none.
Connect your Allo account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A search box opens in a dialog: type Allo, then pick it from the results. That is the only app to choose at this stage.
- 02
Sign in to Allo
Click Add connection. A new tab opens on Allo: sign in with the account whose numbers, calls and contacts the Zap should work with. You need an Allo account for this.
- 03
Grant access
Allow Zapier to use the account. From then on this connection is reused by every Allo step you add. If the Zap must touch records you do not own, your account needs read or write access to them first.
Your first Zap: new contacts straight into the dialer queue
GoalEvery contact created in Allo that matches your rule lands in the Power Dialer queue, without anyone copying numbers.
- 01
Build: pick the trigger
Create a Zap, choose Allo as the app and Contact Created as the event. Select the connection you set up above so the Zap reads your own contacts.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts of your account, so you work on a real record instead of guessing what it looks like.
- 03
Add a filter
Click the plus icon, add Filter, then set the field to look at, the rule and the value. A text rule only works on text. This step makes the Zap multi-step, so a paid plan.
- 04
Add the dialer action
Add Allo again, event Add Numbers to Power Dialer. Map the phone number from the test contact into Phone Numbers. If no queue exists yet, the action creates one.
- 05
Test, then Publish
Test the action and check the number in the queue inside Allo. Then click Publish. From there, each new matching contact goes into the queue as it is created.
The 11 Allo triggers, one by one
11 events start a Zap when something happens in Allo, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.
Call Answered
Instant triggerIn Zapier“Triggers when a call is answered.”
This one waits for a person on your side to actually pick up. A call that only rings without being picked up never reaches it, which makes it the cleanest signal that a conversation started.
Call Completed
Instant triggerIn Zapier“Triggers when a call ends (includes result, duration, recording and AI summary).”
Starts the Zap once a call has ended, and the event carries the outcome, the duration, the recording and the AI summary that Allo produced. It is the richest of the call triggers for anything that needs to report on a conversation.
Call Received
Instant triggerIn Zapier“Triggers when an incoming call starts ringing.”
Fires while an incoming call is still ringing, before anyone has answered. You know who is calling before the conversation even exists, and the Zap can react whether the call gets picked up or not.
Call Triggered
Instant triggerIn Zapier“Triggers when an outbound call is initiated.”
The outbound counterpart: the Zap runs as soon as someone on the team starts dialing out from Allo. It tells you an attempt was made, not that the other side answered.
Contact Created
Instant triggerIn Zapier“Triggers when a new contact is created.”
Runs each time a new contact is created in Allo. It is the natural entry point for anything that should happen once per new person.
Contact Updated
Instant triggerIn Zapier“Triggers when a contact is updated.”
Watches existing contacts rather than new ones: any change to a contact record in Allo starts the Zap. Pair it with a filter when only one kind of change matters to you.
SMS Received
Instant triggerIn Zapier“Triggers when an SMS is received on one of your Allo numbers.”
Any text message arriving on one of your Allo numbers kicks off the Zap. Every inbound SMS counts, from a new prospect or from a customer you already know.
SMS Sent
Instant triggerIn Zapier“Triggers when an SMS is sent from one of your Allo numbers.”
The outgoing side of messaging: a text leaves one of your Allo numbers and the Zap begins.
Tag Added
Instant triggerIn Zapier“Triggers when a tag is added to a call.”
Reacts when someone puts a tag on a call in Allo. Tags become buttons your team presses after a conversation, and each press can launch its own follow-up.
Tag Removed
Instant triggerIn Zapier“Triggers when a tag is removed from a call.”
The reverse move: a tag comes off a call and the Zap runs. Useful when tags stand for a status and taking one away means the status ended.
New Event
Instant triggerIn Zapier“Triggers when a new call or SMS is received.”
A single trigger for both channels: it fires when a new call or a new SMS comes in. You choose what it listens to in the Interactions field, which you have to fill before the trigger works.
The 11 Allo actions, grouped by what you want done
Allo gives you 11 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Tags to Call
ActionIn Zapier“Adds one or more tags to a call.”
Labels a call with one or more tags already configured on your Allo team. You give it the Call ID and the tags.
Create Company
ActionIn Zapier“Creates a new company in your Allo CRM.”
Opens a company record in the Allo CRM. Only the name is mandatory, so it works even from a thin source.
Update Company
ActionIn Zapier“Updates an existing company. Only provided fields are changed.”
Changes the fields you fill on an existing company and nothing else. The Company ID is mandatory; use Find Company first to fetch it.
Add Numbers to Power Dialer
ActionIn Zapier“Appends phone numbers to a Power Dialer queue. Creates the queue if none exists.”
Appends one or more numbers to a Power Dialer queue, and creates the queue when none exists. Common formats are accepted and normalized to E.164, so you do not need to clean numbers beforehand.
Remove Numbers From Power Dialer
ActionIn Zapier“Removes numbers from a Power Dialer queue — by number, by position, or all not-yet-called numbers.”
Takes numbers out of a queue, either one number, one position, or every number not called yet. You choose the mode in What to remove.
Reset Power Dialer Queue
ActionIn Zapier“Creates a fresh, empty queue. The previous queue for the same assignee stops being active.”
Starts a fresh, empty queue. The previous queue of the same assignee stops being the active one, so the rep only sees the new list.
Update Power Dialer Queue Config
ActionIn Zapier“Creates or updates the configuration of a Power Dialer queue.”
Creates the settings of a Power Dialer queue if they do not exist, or updates them if they do, all in one action.
Create Person
ActionIn Zapier“Creates a new person in your Allo CRM.”
Adds a new person to your Allo CRM. At least one phone number is required, in international E.164 format.
Update Person
ActionIn Zapier“Updates an existing person. Only provided fields are changed.”
Edits an existing person and leaves untouched every field you leave blank. It needs the Person ID, which a Find Person step gets for you.
Send SMS (France)
ActionIn Zapier“Send an SMS message to a French phone number using a verified Sender ID.”
Sends a text to a French number, signed with an alphanumeric Sender ID instead of a phone number. The message runs from 1 to 1000 characters.
Send SMS (US)
ActionIn Zapier“Send an SMS message to a US phone number using one of your Allo phone numbers.”
Texts a US number from one of your own Allo numbers. You pick the sending line, the recipient in E.164 format and a message of 1 to 1000 characters.
The 8 Allo searches, and what happens when nothing matches
8 search steps look for data that already exists in Allo, so a later step can use it.
A search step finds a record that already exists in Allo and hands it to the next step. In the editor, Allo's searches sit at the bottom of the Action event list, under SEARCH. Allo offers no find-or-create variant. Three settings decide what happens when the result is not the one you expected.
Get Company by ID
SearchIn Zapier“Returns a single company by its ID (com-…).”
Fetches one company when you already hold its ID, the one that starts with com-. The Company ID field is mandatory, so this search only makes sense once an earlier step or another tool has stored that ID for you.
Find Company
SearchIn Zapier“Searches companies in your Allo CRM.”
Looks through the companies of your Allo CRM. Its main job in a Zap is handing the Company ID to Update Company, which cannot run without it.
List Conversations
SearchIn Zapier“Returns conversations grouped by contact number, sorted by most recent activity.”
Returns the conversations of one Allo number, grouped by contact and sorted by latest activity. The Allo Number field is mandatory; tick Unread Only to keep just the threads nobody has opened.
Find Calls & SMS
SearchIn Zapier“Searches calls and SMS across all conversations — keyword search on transcripts, summaries and messages, with rich filters.”
Searches calls and texts across every conversation, with keywords matched in transcripts, summaries and messages. Switch on Include Transcript and the full text of each call comes back as well.
Get Call or SMS by ID
SearchIn Zapier“Returns a single call (cll-…) or SMS message (msg-…) by its ID.”
Returns a single call (cll-) or SMS (msg-) from its ID, optionally with the transcript when the item is a call and you ask for it.
List Power Dialer Queue
SearchIn Zapier“Returns the numbers currently in a Power Dialer queue, ordered by position.”
Shows the numbers currently waiting in a Power Dialer queue, in their calling order, so a later step can read what is left.
Get Person by ID
SearchIn Zapier“Returns a single person by their ID (per-…).”
Brings back one person from the ID that starts with per-. The Person ID is mandatory, so this search suits Zaps where another tool stored it.
Find Person
SearchIn Zapier“Searches people in your Allo CRM (full-text and field filters).”
Searches people in your Allo CRM, with full text and field filters. It is the usual step before Update Person, since that action needs the Person ID it returns.
The three settings every search exposes
- Successful if no search results are found?Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switch it on and the Zap goes on with nothing in hand.
- Create X if it doesn't exist yet?Ticking it turns a search into a find-or-create. Allo exposes no such variant, so you will not meet this box on its searches.
- If multiple search results are found?Several matches: keep the first one (default), stop the Zap, or pass all of them on at once to the next steps.
When an Allo Zap breaks
Zapier attaches no help article to Allo, so the cases below come from Zapier's general rules plus the field requirements of the Allo steps.
A surprise here is rarely a bug: it often comes from a field Allo requires or from how Zapier treats events. If a run fails anyway, the Zapier troubleshooting page is the next stop.
The past is not picked up
A Zap only reacts to what happens after you switch it on. Last week's calls and texts stay where they are; moving that backlog is a separate job.A Zap that sets itself off
Contact Updated followed by Update Person on the same contact, or SMS Sent behind Send SMS: the Zap writes where it listens and burns tasks fast.Duplicate phone number
Create Person fails when the number already belongs to another person, unless you set Allow Duplicate Number. Search with Find Person first.No Sender ID, no French SMS
Send SMS (France) needs a Sender ID verified by the Allo team, from 3 to 11 letters or digits. Without it the step cannot run.Wrong sending number in the US
Send SMS (US) fails if the Allo number is not SMS-enabled or not in the same country as the recipient. Check the line before blaming Zapier.A sudden flood of events
A bulk import of contacts can return a huge batch at once, and Zapier's flood protection may hold it back.
Need help automating Allo with Zapier?
A person reads every message.



