Resources · Make integration

Allo Make integrationAutomate Allo with Make.

Can Make pick up what happens in your Allo account and pass it on? The Allo Make integration gives you 2 modules: one trigger that watches events and one action that reads user info. This page shows how to link your account and build a first working scenario.

Try the Allo integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Allo Make integration do for you?

The Allo Make integration links your Allo account to Make, so a scenario (the automation you build in Make, a chain of small steps) can notice new events in Allo and fetch user details. You pick the steps from a list; no code is involved at any point.

Route new Allo activity to your other tools. Start with the Watch Events trigger, then hand each event to the app your team already reads, such as a spreadsheet or a chat channel. That hand-off uses the other app's own module, added right after the trigger.

Add context before anything moves on. Going by its name, Get the User Info reads the details of the user behind your connection (Make's help page gives no description). Put it after the trigger when the next step needs to know which Allo account produced the data.

Keep a simple running record. Every event the trigger finds becomes a bundle (one item that travels from step to step), so logging each one somewhere is a matter of mapping fields into the next module.

Keep the scope in mind. Make lists only these 2 modules for Allo, with no generic API module, and its help page for Allo says the text was generated from Allo's documentation and may contain mistakes. Check anything important with Allo. When a scenario misbehaves, the Make troubleshooting guide covers the usual causes, and the Make pricing breakdown explains what the plans include. If you also look at other automation tools, the n8n vs Make comparison sets the two side by side.

Connect

How do you connect Allo to Make?

  1. 01

    Generate an API key in Allo

    You need an active Allo account first. Inside Allo, open Settings, then API, and click Generate. Copy the key that appears on screen, since Make will ask for it in a moment.

  2. 02

    Add an Allo module and open the connection

    In your Make scenario, add any Allo module and click Create a connection. A connection is your Allo account linked to Make once, then reused by every Allo module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario with Allo in Make

GoalWhen a new event shows up in Allo, Make fetches the user info linked to your account and passes both along.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario, then click the large + to place the first module on the empty canvas.

  2. 02

    Set up the trigger

    Search for Allo, pick Watch Events and choose your connection, or click Create a connection if this is your first Allo module in Make.

  3. 03

    Add the user lookup

    Click the + to the right of the trigger, pick Get the User Info from the Allo app, and reuse the same connection. Data from the trigger stays available for mapping.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; read the bundles each module received and confirm the data looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks Allo (every 15 minutes by default), then turn the scenario on so it keeps running.

Triggers

What starts an Allo scenario

1 module starts a scenario when something happens in Allo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Allo as soon as it happens.

Allo1Watch Events

Watch Events

triggerIn the docs only

Watch Events hands your scenario each new event from your Allo account, so the rest of the chain can act on it without anyone copying data by hand. Every event arrives as its own bundle, ready to map into the next module.

How it fires
this is a scheduled trigger, so Make checks the app on the scenario's schedule, set with the clock on the module.
When to use it
whenever something that happens in Allo should reach another tool, like a shared sheet or a team channel.
Watch out
Make's help page for Allo does not describe which event types this module returns, so run it once and read the output before building on it.
Modules

What Make can do in Allo

Allo gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Allo1

Get the User Info

ActionIn the docs only

Judging by its name, Get the User Info returns the details of the Allo user tied to your connection, so later steps know whose account the data comes from. It is the only action Make offers for Allo.

When to use it
right after Watch Events, when the next app needs a name or identifier to label what it stores.
Watch out
Make's help page lists no fields for it, so check the bundle after Run once before mapping.
Need help

Need help automating Allo with Make?

A person reads every message.

FAQ

Allo and Make: common questions

01Is the Allo Make integration free?
Yes, on the Make side. Allo is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes, with files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. You still need an active Allo account, and Allo's own subscription is set by Allo, so check their pricing page for that part.
02What does the Allo Make integration require to connect?
An active Allo account and an API key. In Allo, go to Settings, then API, click Generate and copy the key shown on screen. In Make, add an Allo module, click Create a connection, give it a name if you like, and paste the key. The connection is stored once and every Allo module in your scenarios reuses it. If the account is inactive or the key was copied only in part, the connection will not save, so generate a new key and try again.
03Does the Allo trigger in Make fire instantly?
No. Watch Events is a scheduled trigger: Make checks Allo on the scenario's schedule instead of being called by Allo the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap allowed, while paid plans can go down to 1 minute. Each check that finds new events passes them on as bundles, and each module that processes a bundle counts as one operation on your plan. Pick the interval that matches how quickly your team needs the data.
04What if an Allo module is missing in Make?
Then the Allo app in Make will not cover it on its own. Make offers only 2 Allo modules, Watch Events and Get the User Info, and no generic module for calling the Allo API yourself. Make's help page also notes that its Allo content was generated from Allo's documentation and may contain mistakes, so confirm details with Allo. When you need more than these two modules, the practical route is to pair Allo with another app in the same scenario, or to ask the team for help designing the flow.
05Make or n8n: which suits Allo better?
It depends on the tool your team already works in. In Make, Allo gives you one scheduled trigger and one action, which is enough to push new events into other apps and add user details on the way. Many apps also have an n8n node, so if n8n is already part of your stack, check whether Allo is available there before choosing. Neither answer is universally better; the right pick is the platform where you can maintain the scenario, test it and share it with your colleagues without extra setup.
Same platform

Other docs you might need on this stack.

Browse all integrations