Resources · Make integration

Omnichat Make integrationAutomate Omnichat with Make.

Can Make put new leads into Omnichat and greet them without code? The Omnichat Make integration gives you 4 action modules: create a contact, update it, send a direct message, or call the API. This page covers the connection and a first working scenario.

Try the Omnichat integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Omnichat Make integration do for you?

The Omnichat Make integration links your Omnichat account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that reads or writes data in one app. On the Omnichat side, every module is an action, so Omnichat always comes after something else that starts the flow.

Every new lead becomes a contact. A form, a CRM or a spreadsheet starts the scenario, and Creates a Contact records the person in Omnichat with the details it received. Each item that travels from one module to the next is called a bundle: here, one bundle is one lead.

A first message goes out on its own. Chain Sends a Direct Message right after the contact is created, and the welcome note leaves without anyone copying and pasting. Each module run on a bundle counts as one operation on your Make plan.

Contact records follow your other tools. When something about a customer changes in your CRM, Updates a Contact carries the change over to Omnichat.

What Make does not do here: the Omnichat app has no trigger in Make, so nothing that happens inside Omnichat can start a scenario through these modules. For whatever the listed modules skip, Make an API call reaches the rest of the Omnichat API. New to the editor? The Make training starts from zero, Make pricing explains how operations are counted, and n8n vs Make helps if you are weighing the two tools.

Connect

How do you connect Omnichat to Make?

  1. 01

    Copy your API key from Omnichat

    In Omnichat, open Settings in the left menu, then Integrations and API. Click Add, fill in the pop-up, confirm with Add, and copy the key shown in the Access key field.

  2. 02

    Add an Omnichat module in Make

    In your scenario, add any Omnichat module and click Create a connection. A connection is your Omnichat account linked to Make once. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key into the connection window and confirm. Once saved, the same connection appears in the list of every other Omnichat module you add, so you set it up a single time.

First scenario

Your first scenario: from new lead to welcome message

GoalWhen a new lead arrives in another app, Make creates the contact in Omnichat and sends a first direct message.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your leads land first, a form tool or a CRM, and its trigger module.

  2. 02

    Add Creates a Contact

    Click the + on the right of that first module, search for Omnichat and choose Creates a Contact. Select your connection, or click Create a connection the first time.

  3. 03

    Map the lead's data

    Fill the contact fields by picking values that came out of the first module. Make lists the data it received, so you click on values instead of typing them.

  4. 04

    Chain the message

    Click the + again, add Sends a Direct Message and write your welcome text. Map the recipient from the data the earlier modules passed along.

  5. 05

    Test with Run once

    Click Run once, then send a test lead through the first app. Open each module to read the bundles it received, and check the new contact in Omnichat.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default on a new scenario, then switch the scenario on. Every new lead now gets the same treatment.

Modules

What each Omnichat module does

Omnichat gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Omnichat1

Creates a Contact

ActionIn the docs only

Creates a Contact adds a new person to your Omnichat contacts, filled with data mapped from an earlier module, so a lead captured elsewhere is ready for a conversation.

When to use it
right after the module that brings in a new lead, when that person is not in Omnichat yet.
Watch out
the Omnichat app has no search module in Make, so no ready-made module checks first whether the person exists; make sure the first app sends each lead only once.
Omnichat2

Make an API call

ActionIn the docs only

With Make an API call, you reach any endpoint of the Omnichat API from your scenario, using the connection you already set up, for everything the three other modules leave out.

When to use it
when you need an Omnichat action that has no ready-made module in Make.
Watch out
you describe the request yourself, so keep Omnichat's API documentation open to pick the right endpoint.
Omnichat3

Sends a Direct Message

ActionIn the docs only

Your contact gets a message from Omnichat the moment the scenario reaches Sends a Direct Message: a welcome note, a confirmation, a follow-up after an event in another tool.

When to use it
when something in another app, a paid order or a booked call, should be followed by a word to the person concerned.
Watch out
the module acts once per bundle it receives, so test with a single record through Run once before switching the scenario on.
Omnichat4

Updates a Contact

ActionIn the docs only

Keep an Omnichat contact in line with your other tools: Updates a Contact changes the details of a person who already exists, so the record matches what your CRM says today.

When to use it
when something about a customer changes elsewhere and Omnichat has to follow.
Watch out
the module works on an existing contact, and the app offers no search module, so plan where the reference to that contact comes from before you build.
Need help

Need help automating Omnichat with Make?

A person reads every message.

FAQ

Omnichat and Make: common questions

01Is the Omnichat Make integration free?
Yes on the Make side: Omnichat is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. On the Omnichat side, you need an active account with an API key; Omnichat's own pricing page covers its subscription.
02What do you need to connect Omnichat to Make?
An active Omnichat account and an API key. To get the key, open Settings in Omnichat's left menu, then Integrations and API, click Add, fill in the pop-up and confirm. The key then shows in the Access key field. In Make, add any Omnichat module, click Create a connection, give it a name if you like, and paste the key. All 4 Omnichat modules reuse that connection, so this is a one-time setup.
03Can Omnichat start a Make scenario in real time?
No, not through its own modules: the Omnichat app in Make has no trigger, neither scheduled nor instant. The scenario starts another way. The usual route is the trigger of the app where the event happens, such as a form, a CRM or an online shop, followed by the Omnichat modules. You can also let the schedule of the first module start it, every 15 minutes by default and down to 1 minute on paid plans. Omnichat then sits at the end of the flow, as its destination.
04What if the Omnichat module you need is missing in Make?
Use Make an API call. With the same connection, it reaches any endpoint of the Omnichat API, so an action without a dedicated module is still within reach. The catch is that you write the request yourself, based on Omnichat's API documentation. Make's page on this app also warns that its content is AI-generated and may contain mistakes, so check any detail that matters against Omnichat's docs or ask Omnichat. If Omnichat cannot do it at all, another app in the same scenario might.
05Should you use Make or n8n for Omnichat?
It depends on where your other automations already live. In Make, Omnichat offers 4 action modules, one of which calls its API directly, and no trigger, so the scenario always starts in another app or on a schedule. Many apps also have an n8n node; check whether Omnichat has one before choosing, and compare what each side covers for your exact case. If your team already runs its scenarios in Make, keeping Omnichat there avoids splitting your flows across two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations