Resources · Make integration

AssistLoop Make integrationAutomate AssistLoop with Make.

What happens when a support chat needs a person instead of a bot? The AssistLoop Make integration gives you 7 modules, 6 of them triggers, to push what happens in AssistLoop into the rest of your stack. This page walks you from connection to a working first scenario.

Try the AssistLoop integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AssistLoop Make integration do for your support team?

The AssistLoop Make integration links your AssistLoop account to Make so that a scenario, the automation you build in Make as a chain of modules, can react to what happens in your support workspace. Make offers 6 scheduled triggers and 1 action for AssistLoop, and no search module.

Get a person on the chat fast. Start a scenario with Watch Human Handoff Requested and send the details to whatever tool your agents already watch, so a customer who asked for a human is not left waiting behind the bot.

Keep an eye on the plumbing. Watch API Errors, as its name suggests, is the trigger to reach for when you want failures surfaced somewhere visible instead of discovered by an unhappy customer. Pair it with Watch Workspaces or Watch Agents if you also track who and what is set up in AssistLoop.

Build a record of conversations. Watch Conversations and Watch Messages bring chat activity into Make, where each item becomes a bundle, one piece of data handed from module to module, that you can store or forward.

Know the limits before you start. Make's own documentation for AssistLoop is marked as limited, because little public information about the app exists, so field names are only visible once your connection is live. There is no Make an API Call module either. If you are still weighing platforms, the n8n vs Make comparison lays out the differences, and Make pricing explains how operations are counted. When a scenario misbehaves, start with Make troubleshooting.

Connect

How do you connect AssistLoop to Make?

  1. 01

    Add an AssistLoop module

    In your scenario, click the +, search for AssistLoop and pick any of its modules. Then click Create a connection. A connection is your AssistLoop account linked to Make once and reused by every AssistLoop module afterward.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when several workspaces are involved. Then either approve Make on the AssistLoop page that opens, or paste the key AssistLoop gives you, depending on what the connection window asks for.

  3. 03

    Save and check the fields

    Click Save. Once the account is linked, Make can list what it reads in AssistLoop inside the module fields. Look through them: that is where you discover which options the app really exposes to your scenarios.

First scenario

Your first scenario with AssistLoop and Make

GoalWhen a customer asks for a human in AssistLoop, Make picks up the request and records a new conversation event.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Everything you build next hangs off this starting point.

  2. 02

    Pick the handoff trigger

    Search for AssistLoop, choose Watch Human Handoff Requested and select the connection you created. If you have not made one yet, Create a connection sits right in the module.

  3. 03

    Add the action

    Click the + on the right of the trigger and add New Conversation Event. Map data from the trigger into its fields; Make shows you the values the previous module can hand over.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubbles above each module to read the bundles they received and confirm the handoff data landed where you expected.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two runs.

Triggers

What can start an AssistLoop scenario?

6 modules start a scenario when something happens in AssistLoop. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by AssistLoop as soon as it happens.

AssistLoop1Watch API Errors

Watch API Errors

triggerIn the docs only

Gives you a scenario that starts from API errors on the AssistLoop side, judging by the module name, so problems show up in your tools rather than in a customer complaint. Make publishes no description for it, so read the first bundle before relying on its content.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment an error occurs.
When to use it
when whoever looks after your AssistLoop setup wants failures passed to a channel they actually read.
Watch out
every check that finds data costs operations, the unit Make counts on your plan.
AssistLoop2Watch Agents

Watch Agents

triggerIn the docs only

Hands you the agents of your AssistLoop account as bundles, which is handy for keeping a list of who or what answers customers in sync elsewhere. The name points to agents; Make gives no further description, so confirm with Run once what an agent record holds.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
when a new agent is set up and a spreadsheet or directory should reflect it.
Watch out
the documentation does not say whether edits to an existing agent count, so test that case before you depend on it.
AssistLoop3Watch Conversations

Watch Conversations

triggerIn the docs only

Turns AssistLoop conversations into items your scenario can store, tag or forward, which gives you a trail of support activity outside the app. Treat the exact scope as something to verify: the module is only listed by name in Make's documentation.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
when you want a conversation-level log in a CRM or database rather than every single message.
Watch out
on the Free plan you only get 2 active scenarios, so choose between this and Watch Messages if you are testing there.
AssistLoop4Watch Human Handoff Requested

Watch Human Handoff Requested

triggerIn the docs only

Lets you act when a customer asks to talk to a person, which is usually the moment speed matters most in support. The name says as much; the fields it returns are only visible once you run it with your own account.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a request waits until the next check.
When to use it
when your human agents live in another tool and need to be alerted there.
Watch out
with the default schedule of every 15 minutes, a request can wait up to one full interval; paid plans allow a check every minute.
AssistLoop5Watch Messages

Watch Messages

triggerIn the docs only

Brings individual chat messages into Make, one bundle per message, so you can analyse or archive the actual wording customers use. Its behavior is inferred from the name, since Make's AssistLoop documentation offers no description of it.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
when the text itself matters, for example to feed a knowledge base or a review queue.
Watch out
busy chats produce many bundles, and each module that processes one uses an operation, so this trigger can eat your plan faster than Watch Conversations.
AssistLoop6Watch Workspaces

Watch Workspaces

triggerIn the docs only

Surfaces the workspaces in your AssistLoop account, which helps when you manage several brands or teams and want each new one registered somewhere automatically. As with the other triggers, Make lists it without a description, so check the output first.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
when an agency or a multi-brand company opens a workspace and wants setup tasks created elsewhere.
Watch out
the connection is tied to one account, so confirm with Run once which workspaces it can actually see.
Modules

What can Make do in AssistLoop?

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

AssistLoop1

New Conversation Event

ActionIn the docs only

The only AssistLoop action in Make, and the one way a scenario writes back into the app instead of only reading it. The name suggests it records an event on a conversation; Make's documentation adds nothing more, so open the module after connecting to see which fields it expects.

When to use it
right after a trigger, to leave a trace in AssistLoop that the scenario handled the case.
Watch out
avoid pairing it with Watch Conversations in a way that makes the scenario react to its own writes.
Need help

Need help automating AssistLoop with Make?

A person reads every message.

FAQ

AssistLoop and Make: frequent questions

01Is the AssistLoop Make integration free?
Yes, AssistLoop is a standard app in Make, so you can use it on the Free plan. That plan has real limits though: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans, from Core up to Enterprise, lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in credits, meaning operations, each month. AssistLoop's own pricing is a separate question this page does not cover.
02What do you need to connect AssistLoop to Make?
Mostly an AssistLoop account you can sign in to. Make's documentation for AssistLoop lists no prerequisites and no official connection steps, so you follow the generic flow: add any AssistLoop module, click Create a connection, optionally name it, then approve Make on the AssistLoop page or paste the key AssistLoop provides, and click Save. Because the documentation is marked as limited, the connection window itself is the best guide to which of those two methods applies to your account.
03Do AssistLoop triggers in Make react in real time?
No. All 6 AssistLoop triggers are scheduled, and none is instant. Make checks AssistLoop on the scenario's schedule, which is every 15 minutes by default and cannot be shorter than 15 minutes on the Free plan. On a paid plan you can bring it down to 1 minute. So a handoff request or a new message waits until the next check before your scenario runs. Keep that in mind for anything customers are actively waiting on.
04What if the AssistLoop module you need is missing in Make?
It depends on what is missing. Make offers 7 AssistLoop modules and no Make an API Call module, so you cannot send a custom request to AssistLoop from a scenario. The documentation is also flagged as limited, which means some options only appear once your connection is live. If a need is not covered, check whether another app in your stack can handle that step, or ask the Hack'celeration team to look at your case.
05Should you use Make or n8n for AssistLoop?
It depends on the tool your team already uses. On the Make side, AssistLoop offers 7 modules: 6 scheduled triggers and 1 action, available on every plan including Free. Many apps also have an n8n node, but this page does not confirm one for AssistLoop, so check n8n's own node list before deciding. Compare the modules each tool actually offers for your use case rather than general reputations, and pick the platform where your other automations already run.
Same platform

Other docs you might need on this stack.

Browse all integrations