Resources · Make integration

Trengo AI Journeys Make integrationAutomate Trengo AI Journeys with Make.

Your customer journeys can start the moment something happens elsewhere. The Trengo AI Journeys Make integration has 1 action module that launches a journey. This page shows you how to connect your account and build a first working scenario around it.

Try the Trengo AI Journeys integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Trengo AI Journeys Make integration do for you?

It lets another app decide when a Trengo AI Journeys journey begins. Make runs a scenario (the automation you build, a chain of steps), and the Trengo AI Journeys step inside it is a single module (one brick of the scenario) called Trigger Journey. Whatever event you put in front of it becomes the start signal for your journey.

Follow up on a purchase. An online store picks up a new order in its own app, and Trigger Journey launches the post-purchase conversation in Trengo, so nobody on the support team has to remember it.

React to a billing event. A finance team puts its invoicing tool first in the scenario. When a payment fails, the next step, Trigger Journey, starts the journey built for that case.

Welcome a new lead. A marketing team places a form or CRM module at the head of the scenario, and each new contact gets the right journey without a copy-paste between tools.

What Make does not give you here: there is no trigger for this app, so Make cannot react to what happens inside Trengo AI Journeys, and there is no Make an API Call module to reach other parts of the app. Make also warns that its own documentation for this app is limited. If you want a broader view of the platform first, read the Make review; when you hesitate between two tools, the n8n vs Make comparison sets out the criteria, and the Make pricing guide explains how runs are counted.

Connect

How do you connect Trengo AI Journeys to Make?

  1. 01

    Add the module

    In your scenario, search for Trengo AI Journeys, pick Trigger Journey, then click Create a connection. A connection is your Trengo AI Journeys account linked to Make once and reused by every module of this app.

  2. 02

    Name and authorize it

    Give the connection a name you will recognize later, handy if you manage several accounts. Then either approve Make on the page Trengo AI Journeys opens, or paste the key the app provides, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and every other scenario that uses Trengo AI Journeys can select it from the list instead of starting over.

First scenario

Your first scenario with Trengo AI Journeys

GoalWhen a new order arrives in your shop app, Make starts a journey in Trengo AI Journeys.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Since Trengo AI Journeys has no trigger, this first slot goes to the app where the event happens, such as your shop.

  2. 02

    Set up the starting app

    Pick that app's module, link its account with Create a connection, then fill in its fields. Make lists what it can read once the connection exists, so you choose from a menu rather than typing.

  3. 03

    Add Trigger Journey

    Click the + on the right of the first module and choose Trengo AI Journeys, then Trigger Journey. Connect your account and map data from the previous module into the fields Make shows you.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one order). Check that the journey started in Trengo.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or pick another interval your plan allows, then switch the scenario on.

Modules

What the Trengo AI Journeys module does

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

Trengo AI Journeys1

Trigger Journey

Action

In Make“Triggers a journey.”

You get a journey in Trengo AI Journeys that starts on its own as soon as the earlier steps of your scenario reach this module. As an action, it runs once per bundle it receives.

When to use it
place it after a module from another app whenever an event there, such as an order or a new form entry, should open a customer conversation.
Watch out
every bundle that reaches it counts as an operation, so filter upstream if only some records deserve a journey.
Need help

Need help automating Trengo AI Journeys with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Trengo AI Journeys Make integration free?
Yes, Trengo AI Journeys is a standard app, so it works from Make's Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each time Trigger Journey runs on one bundle, Make counts one operation against your plan. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. Your Trengo subscription is a separate matter.
02What do you need to connect Trengo AI Journeys to Make?
A Trengo AI Journeys account and a Make account are the starting point; the documentation lists no other prerequisite. You add the Trigger Journey module, click Create a connection, optionally name it, then either approve Make on the app's page or paste the key the app gives you, and click Save. Because Make flags its documentation for this app as limited, follow what the connection window asks for and confirm everything with Run once.
03Does Trengo AI Journeys trigger a Make scenario in real time?
No, not by itself, because the app has no trigger module in Make. Your scenario has to start elsewhere. You can open it with a trigger from another app: if that trigger is instant, meaning the app alerts Make through a webhook as soon as something happens, the journey follows right away. If it is scheduled, Make checks on the scenario's schedule, every 15 minutes by default and every 1 minute at best on a paid plan.
04What if Trengo AI Journeys lacks the module you need in Make?
It depends on what you are missing. Make offers only Trigger Journey for this app and no Make an API Call module, so there is no generic way to reach other features of Trengo from Make. Also note that Make describes its documentation for the app as limited. If you need to react to events inside Trengo, look for another app in Make that exposes them, or ask the team at Hack'celeration to review your case before you build around a gap.
05Should you use Make or n8n with Trengo AI Journeys?
It depends on your criteria rather than on a winner. With Make, you get one action module, Trigger Journey, and a visual editor where each step is a module you set up with menus. Many apps also have an n8n node, so check whether one exists for Trengo before choosing. Compare what each tool offers for this app, how each counts usage, and which one your team already runs. Neither choice is ranked here: pick the one that covers your use case.
Same platform

Other docs you might need on this stack.

Browse all integrations