Resources · Make integration

Exa Make integrationAutomate Exa with Make.

Can a Make scenario search the web with Exa and hand the results to your other tools? Yes. The Exa Make integration gives you 4 modules: three searches and one open API call. This guide is for ops and marketing builders, and it walks you from the connection to a tested first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Exa Make integration let you automate?

The Exa Make integration links your Exa account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Once linked, a scenario can send a query to Exa, read the matching pages, or look for sites close to a given URL, then pass every result to the next step.

Watch a market without reading it by hand. A content team keeps a list of topics in another app. For each topic, Perform a Search asks Exa for relevant results, and the scenario files them where the team already works. Each result travels as a bundle, meaning one item passed from one module to the next.

Map the neighbors of a competitor. A growth marketer drops a URL into the scenario and Search Similar Links returns sites that look like it. That list becomes a prospect sheet or a benchmark to review.

Fetch the text behind known documents. When you already hold Exa document IDs, List Contents brings back their content in one pass, ready for a summary step or an archive.

Exa has no trigger in Make, so nothing starts on its own from the Exa side: the scenario runs on a schedule or after another app. The Make documentation for Exa is itself flagged as AI generated, so check any detail that matters with Exa directly. For anything the three searches do not cover, Make an API Call reaches the rest of the Exa API. If you are weighing tools, read n8n vs Make, and when a scenario breaks, Make troubleshooting lists the usual fixes.

Connect

How do you connect your Exa account to Make?

  1. 01

    Copy your Exa API key

    You need an active Exa account first. In Exa, open your account settings, go to the API keys section and copy the key shown on screen. Keep it at hand: Make asks for it in a moment, and it is what proves the scenario may act for you.

  2. 02

    Add an Exa module in your scenario

    Log in to Make, add any Exa module to your scenario and click Create a connection. A connection is your Exa account linked to Make once, then reused by every Exa module you add later, so you only do this step one time.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several Exa accounts. Paste the API key you copied, or follow the on-screen instructions. The connection now appears in the module.

First scenario

Build your first scenario with Exa

GoalWhen a new topic lands in the tool that holds your list, Make asks Exa for relevant results and returns them to you.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here that first module belongs to the app that holds your topics, since Exa has no trigger of its own.

  2. 02

    Add Perform a Search

    Click the + on the right of that first module, search for Exa and pick Perform a Search. Select the connection you created, or click Create a connection if this is your first Exa module.

  3. 03

    Map the query

    Fill the module fields and map the topic coming from the previous module into the query. Mapping means you drag a value from an earlier step instead of typing it, so each topic gets its own search.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above Perform a Search and read the bundles it received: each one is a result Exa found for your topic.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. From now on Make checks for new topics on that rhythm and sends each one to Exa.

Modules

What can each Exa module do in Make?

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

Exa1

Make an API Call

Action

In MakePerforms an arbitrary authorized API Call.

This module lets your scenario reach any endpoint of the Exa API with the connection you already set up, so a feature missing from the list does not block you.

When to use it
Exa offers something none of the three search modules handles and you know which endpoint serves it.
Watch out
you describe the request yourself, so keep the Exa API documentation open while you fill it in.
Exa2

List Contents

Search

In MakeRetrieves a list of content of documents based on a list of document IDs.

Hand it a list of Exa document IDs and it gives you back the content of each document, ready to summarize, store or send on.

When to use it
an earlier step already collected document IDs and you now need the text behind them, not a fresh search.
Watch out
as a search module it can return zero, one or many bundles, so plan what the next module does with each one.
Exa3

Perform a Search

Search

In MakePerforms a search with a Exa prompt-engineered query and retrieves a list of relevant results.

Your query goes to Exa, which tunes it for its own engine, and you receive a list of relevant results to route anywhere in the scenario.

When to use it
you start from a topic, a question or a keyword, for example a theme your editorial team wants covered, and need sources about it.
Watch out
each result becomes its own bundle, and every module after it runs once per bundle, which counts as operations on your Make plan.
Exa4

Search Similar Links

Search

In MakeReturns a list of similar links to the URL provided.

Give it one URL and Exa answers with links that resemble it, a quick way to widen a list of competitors, partners or reference sites.

When to use it
you hold one good example page and want more like it, rather than describing what you look for in words.
Watch out
the answer is a list, so an empty result is possible; test with Run once on a URL you know before you schedule the scenario.
Need help

Need help automating Exa with Make?

A person reads every message.

FAQ

Exa and Make: frequently asked questions

01Is the Exa Make integration free?
Yes on the Make side: Exa is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 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, meaning operations, each month. You still need an active Exa account with an API key, and Exa sets its own subscription terms on its pricing page.
02What do you need to connect Exa to Make?
An active Exa account and its API key. In Exa, open your account settings, go to the API keys section and copy the key. In Make, add an Exa module to a scenario, click Create a connection, give it a name if you like, and paste the key. That connection is then shared by every Exa module in your scenarios, so you set it up only once and never paste the key again in each module.
03Can Exa start a Make scenario in real time?
No. Exa has no trigger module in Make, neither scheduled nor instant, so nothing on the Exa side can launch a scenario. You start it another way: put a module of another app first, for instance the tool where new topics or URLs arrive, or let the schedule on the first module run the scenario, every 15 minutes by default on a new scenario. Exa then works as a step inside the flow, answering each query the scenario sends it.
04What if the Exa module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Exa API with the same connection as the other modules, so a feature without its own module stays within reach. You write the request yourself, which asks for a look at the Exa API documentation. Keep in mind that the Make documentation for Exa is marked as AI generated and may contain mistakes, so confirm important details with Exa before you rely on them in a live scenario.
05Make or n8n for Exa?
It depends on the tool your team already uses. On Make, Exa comes with four modules: three searches and Make an API Call for the rest of its API, all on one connection. The same app often has an n8n node too, so check the n8n side for Exa before you decide. Pick the platform where your other scenarios already live, and compare what each one offers for Exa on the modules you actually need rather than on general claims.