Resources · Make integration

Relevance Make integrationAutomate Relevance with Make.

Could your Relevance agents act on what lands in your other apps, with nobody forwarding it? The Relevance Make integration gives you 7 modules: 3 actions and 4 searches. This guide is for ops and growth builders, and it walks you from the API key to a first working scenario.

Try the Relevance integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Relevance Make integration let you automate?

The Relevance Make integration lets a Make scenario (the automation you build, a chain of steps) talk to your Relevance project. It can send a message to one of your agents, run one of your tools, and read back agents, tools, conversations and messages, all without writing code.

Feed an agent from your other apps. A form entry or a new CRM record lands in another app, and Message an Agent hands it to the right Relevance agent as the opening message of a new conversation, or as a follow-up in one that already exists.

Run a tool on demand. When a row changes in a spreadsheet, Execute a Tool starts one of the tools you built in Relevance with that data, so the tool works on real inputs instead of waiting for someone to paste them.

Archive what agents said. List an Agent's Conversations and List a Conversation's Messages pull the exchanges out of Relevance so you can store them in a sheet or a base like the one in the Airtable Make integration.

There is no trigger in this app: Relevance never starts a scenario by itself. The first module comes from another app or from the scenario's schedule. For anything the 7 modules skip, Make an API Call reaches the rest of the Relevance API. Before you commit, the Make review covers the tool as a whole, and n8n vs Make sets the two platforms side by side.

Connect

How do you connect your Relevance account to Make?

  1. 01

    Copy your Project ID and API key

    In Relevance, open the project selector at the top left of the dashboard and pick your project. Go to Settings in the left sidebar, then the API keys tab, and copy both the Project ID and the API key.

  2. 02

    Add a Relevance module in Make

    In your Make scenario, add any Relevance module and click Create a connection. The Connection name field is optional; a clear name helps when you later keep one connection per project.

  3. 03

    Paste the credentials and save

    Paste the Project ID and API key you copied, or follow the on-screen instructions, then confirm. The connection (your Relevance account linked to Make once) is now reused by every Relevance module you add.

First scenario

Build your first scenario with Relevance

GoalWhen a new record reaches another app, Make sends its content to a Relevance agent with Message an Agent.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Relevance has no trigger, so the first module (one brick of the scenario) comes from the app where your data starts, such as your CRM.

  2. 02

    Add Message an Agent

    Click the + to the right of that first module, search for Relevance and pick Message an Agent. Click Create a connection and paste your Project ID and API key.

  3. 03

    Choose the agent and map the text

    Once connected, Make lists the agents it can read. Pick one, then map the text from the first module into the message so each new record becomes a fresh conversation.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles (the items passed from one module to the next) that each module received. Check that the agent got the right text.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan does not go below that. Save, then switch the scenario on.

Modules

What can each Relevance module do in Make?

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

Relevance1

Execute a Tool

Action

In Make“Triggers a tool.”

You get a Relevance tool's work done the moment the data appears, with nobody copying inputs by hand: this action starts the tool you pick and hands it the data gathered earlier in the scenario.

When to use it
a tool already does the job in Relevance and you simply want it fed by a spreadsheet row or a form entry.
Watch out
each run counts as an operation, one execution of one module that Make counts on your plan.
Relevance2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your safety net: with the same connection, it calls any endpoint of the Relevance API that the six other modules do not cover. You keep the whole scenario in Make instead of stitching in another tool.

When to use it
you need a Relevance feature that has no module of its own in the list.
Watch out
you write the request yourself here, so keep the Relevance API documentation open while you set it up.
Relevance3

Message an Agent

Action

In Make“Sends a message to an agent to either start a new conversation or send an additional message to an existing conversation.”

This action puts a message in front of a Relevance agent. It either opens a brand new conversation or adds a message to one that already exists, so the agent keeps the thread.

When to use it
a lead, a ticket or an inbound question arrives elsewhere and you want the agent to handle it without anyone forwarding it.
Watch out
to continue a thread rather than start a new one, pass the existing conversation, which you can find with List an Agent's Conversations.
Relevance4

List a Conversation's Messages

Search

In Make“Returns a list of messages for a conversation.”

Pick one conversation and this search returns its messages, so you can read what the agent and the other side actually said, outside Relevance.

When to use it
copying a full exchange into a CRM note or a support record once the conversation is worth keeping.
Watch out
a search returns zero, one or many bundles, and every following module then runs once per message, which multiplies operations.
Relevance5

List Agents

Search

In Make“Returns a list of agents.”

This search gives you the agents in your Relevance project, one bundle per agent. It is handy when the scenario must pick an agent dynamically instead of being hard-wired to one.

When to use it
building an inventory of your agents in a sheet, or looping over each agent before listing its conversations.
Watch out
it only sees the project tied to your connection; agents from another project need their own connection.
Relevance6

List an Agent's Conversations

Search

In Make“Returns a list of conversations for an agent.”

Point it at one agent and it hands back that agent's conversations. It is the step between knowing which agent you care about and reading what was said.

When to use it
finding the thread to continue with Message an Agent, or feeding List a Conversation's Messages for an archive.
Watch out
an agent with plenty of conversations produces plenty of bundles, so add a filter before any module that writes somewhere.
Relevance7

List Tools

Search

In Make“Gets a list of tools.”

This search returns the tools available in your Relevance project, so a scenario can see what exists before it calls anything.

When to use it
keeping a shared catalog of tools up to date for your team, or choosing which tool Execute a Tool should run from data rather than by hand.
Watch out
like every search, it may return nothing; plan for an empty result before the next module expects a tool.
Need help

Need help automating Relevance with Make?

A person reads every message.

FAQ

Relevance and Make: frequent questions

01Is the Relevance Make integration free?
Yes, on the Make side. Relevance 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 of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and count usage in credits each month. Your Relevance subscription is separate: the Relevance account itself needs an active plan on their side, and its pricing page gives the details.
02What do you need to connect Relevance to Make?
An active Relevance account and an API key. In Relevance, choose your project from the selector at the top left, open Settings in the sidebar and go to the API keys tab, where you copy the Project ID and the API key. In Make, add a Relevance module, click Create a connection, optionally name it, and paste both values. The same connection then serves all 7 modules, so you only do this once per project.
03Does the Relevance Make integration react in real time?
No, not on its own, because Relevance has no trigger module in Make. The scenario always starts with something else: a trigger from another app, or the schedule set on the first module, which runs every 15 minutes by default. If that other app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, your Relevance agent gets the message right after the event. With a scheduled start, it waits for the next check.
04What if the Relevance module you need is missing in Make?
Use Make an API Call. It reuses your existing Relevance connection and can reach any endpoint of the Relevance API, which covers what the 3 actions and 4 searches leave out. You build the request yourself, so the Relevance API documentation is your reference. Keep in mind that Make's own documentation for this app is marked as AI-generated and may contain mistakes, so double-check anything important with Relevance directly before you rely on it.
05Should you use Make or n8n for Relevance?
It depends on where the rest of your automations live. On Make, Relevance comes with 7 ready modules, including Make an API Call for everything else, and it runs from the Free plan. Many apps also have an n8n node, so check whether one exists for Relevance before choosing. Neither tool is ranked here: compare the criteria that matter to your team, such as who builds the scenarios and which apps they already connect, and the n8n vs Make comparison on this site lays those criteria out.
Same platform

Other docs you might need on this stack.

Browse all integrations