Resources · Make integration

Jepto Make integrationAutomate Jepto with Make.

Can Make handle Jepto for you while you work on something else? The Jepto Make integration gives you 9 modules: 7 actions and 2 searches. This page shows what each one does, how to link your account and how to build a first scenario step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Jepto Make integration do for you?

The Jepto Make integration links your Jepto account to Make, a no-code tool where you chain apps together. You build a scenario, which is the automation itself, out of modules, which are its bricks: here, modules that create clients, create social posts and work through Jepto insights without you opening Jepto each time.

New clients set up on their own. When a deal is signed in another app, Create Client adds the account in Jepto. Put Search Clients in front of it if the same company might already be there.

Insights that reach the right person. Search for Insights pulls the ones you care about, Get an Insight reads one in full, and once someone takes it over, Acknowledge an Insight or Resolve an Insight records it in Jepto.

Posts that go out from where you write them. Create a Social Post turns text approved in another tool into a Jepto post, so the copy never has to be pasted by hand.

Jepto has no trigger in Make: a scenario starts on a schedule or on another app's event, never on something that happens in Jepto. Make also warns that its Jepto documentation is limited, so test each module with Run once before relying on it. If you are weighing tools, read n8n vs Make; for the basics of the editor, see Make training, and to budget your usage, Make pricing.

Connect

How do you connect Jepto to Make?

  1. 01

    Add a Jepto module

    In your scenario, pick any Jepto module, for example Search Clients. Its settings open with a Connection field: click Create a connection. A connection is your Jepto account linked to Make once, then reused by every Jepto module.

  2. 02

    Name it and authorize Make

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

  3. 03

    Save and check

    Click Save. The module now shows your connection, and Make can list what it reads from your account. From here, every other Jepto module you add picks the same connection from the list.

First scenario

Your first scenario with Jepto

GoalWhen a new client lands in the app you already use to sign deals, Make creates that client in Jepto.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your new clients show up first, such as your CRM or a form tool.

  2. 02

    Set up the starting module

    Search that app by name, pick the module that watches for new records, and connect your account. This brick decides when the whole scenario runs, since Jepto has no trigger of its own.

  3. 03

    Add Create Client

    Click the + on the right, search Jepto and choose Create Client. Pick your connection, then map the client details from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one client. Check that the client appears in Jepto.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From then on, new clients reach Jepto without anyone retyping them.

Modules

What the Jepto modules do

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

Jepto1

Acknowledge an Insight

ActionIn the docs only

You get a way to tell Jepto that an insight has been seen and is in someone's hands, without opening the app. As its name suggests, it marks one insight as acknowledged.

When to use it
right after the step that hands the insight to a teammate, so the team knows it is being looked at.
Watch out
acknowledging is not closing it; use Resolve an Insight once the issue is really dealt with.
Jepto2

Add External ID to Insight

ActionIn the docs only

This one keeps a Jepto insight tied to its copy elsewhere: it attaches an identifier from another tool, such as a ticket number, to the insight.

When to use it
after a module of another app creates a task from the insight, map that task's ID here so both records point to each other.
Watch out
run it after the other tool has returned its ID, never before, or there is nothing to store.
Jepto3

Create Client

ActionIn the docs only

With Create Client, a new account appears in Jepto from data another app already holds, so nobody types the same company twice.

When to use it
when a deal is signed or an onboarding form comes in, as the action right after that event.
Watch out
nothing shows that it checks for an existing client by itself; place Search Clients before it if duplicates are possible, and test with Run once.
Jepto4

Create a Social Post

ActionIn the docs only

Your text, written and approved somewhere else, becomes a social post in Jepto without copy and paste. The module sends one post per bundle it receives.

When to use it
when a row is marked as approved in the sheet or tool where your team drafts its posts.
Watch out
a search placed before it can return several items, and each one then produces its own post, so filter upstream.
Jepto5

Execute a GraphQL Query

ActionIn the docs only

For anything the other eight modules do not cover, this module lets you send a GraphQL query of your own to Jepto and use what comes back in the next modules.

When to use it
when a need goes beyond clients, insights and posts and you know the query to write.
Watch out
it asks for GraphQL knowledge, and Make gives no Jepto documentation to help write the query, so test it alone first.
Jepto6

Get an Insight

ActionIn the docs only

Get an Insight, as its name says, fetches one insight you already know, so the next modules can quote it in a message or a report.

When to use it
after Search for Insights has found the one that matters, or when another tool stored its identifier earlier.
Watch out
it reads a single insight; to go through many, start from Search for Insights instead.
Jepto7

Resolve an Insight

ActionIn the docs only

Closing the loop is what this module gives you: once a problem is fixed elsewhere, the matching insight is marked as resolved in Jepto.

When to use it
when the ticket or task linked to the insight is closed in the other app your team works in.
Watch out
resolve only after the real fix, not on acknowledgment, or the insight leaves your list too early.
Jepto8

Search Clients

SearchIn the docs only

Before acting on a client, you can find it: Search Clients looks through your Jepto clients and returns zero, one or several of them as bundles.

When to use it
ahead of Create Client, to avoid a duplicate, or before any step that needs a client that already exists.
Watch out
an empty result still lets the scenario go on, so decide what the next modules should do when nothing matches.
Jepto9

Search for Insights

SearchIn the docs only

Search for Insights gathers the insights you want to deal with in one pass, each returned as its own bundle for the modules that follow.

When to use it
as the first Jepto step of a scheduled scenario that sends new insights to your team.
Watch out
every insight found makes the next modules run once more, which adds operations, the unit Make counts on your plan.
Need help

Need help automating Jepto with Make?

A person reads every message.

FAQ

Questions about the Jepto Make integration

01Is the Jepto Make integration free?
Yes, Jepto is a standard app, so it works on the Free plan of Make. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, and stops a run after 5 minutes. Files are capped at 5 MB and data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring a 1 minute interval, unlimited active scenarios and 40 minutes per run, with usage counted in operations each month. Your Jepto subscription is a separate matter this page does not cover.
02What do you need to connect Jepto to Make?
A Jepto account and a Make account. The documentation from Make lists no other prerequisite and no specific steps for Jepto, so the usual path applies: add a Jepto module, click Create a connection, optionally name it, then approve Make on the Jepto page or paste the key Jepto provides, and click Save. The connection is then shared by all 9 Jepto modules. If the screen asks for a value you cannot find, check your Jepto account settings.
03Does the Jepto Make integration react in real time?
No. Jepto has no trigger in Make, neither scheduled nor instant, so nothing in Jepto can start a scenario. You have two ways to start one anyway. The first is a schedule set on the first module, every 15 minutes by default, useful with Search for Insights. The second is to open the scenario with a module from another app, whose event then drives the Jepto actions. On the Free plan, a scheduled run cannot be closer than 15 minutes apart.
04What if a Jepto module is missing in Make?
It depends on what you need. Jepto has no Make an API Call module, but Execute a GraphQL Query lets you send your own query to Jepto, which may cover a case the 7 actions and 2 searches miss. Make also says its Jepto documentation is limited, so expect to test by trial with Run once. If the query is out of reach, the team at the agency can build the scenario with you.
05Should you use Make or n8n for Jepto?
It depends on the tool you already use. On Make, Jepto comes with 9 modules and no trigger, and this page walks through all of them. Many apps also have an n8n node, but this page does not confirm whether Jepto does, so check the n8n node list before deciding. If you already run your scenarios in Make, staying there keeps every automation in one place. The comparison page linked above sets out how the two tools differ.