Resources · Zapier integration

Jepto Zapier integrationAutomate Jepto with Zapier.

Jepto Zapier integration: 3 triggers, 5 actions and 3 searches to push Jepto Insights into the project and chat tools your team already works in, close them from there, and create clients or social posts without opening Jepto at all.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Jepto Zapier integration actually does

It links your Jepto account to the other apps you use, with Zapier in the middle. When Jepto raises an Insight, from an anomaly in a client's data or from one of your automation jobs, Zapier can carry it to a task board, a chat or a sheet. It also runs the other way: other apps can create clients and posts in Jepto, or acknowledge and resolve Insights.

A task for every anomaly. Insight Created From Anomaly starts the Zap, your project tool gets a card, and Add External ID to Insight stamps the card's reference back on the Insight so both records stay linked.

Insights closed where the work happens. When that card is done, Find Insight by External ID locates the matching Insight and Resolve Insight closes it. Nobody has to go back into Jepto to tidy up.

Clients and posts fed from elsewhere. A deal won in your CRM can become a Jepto client through Create Client, and an approved row in a content calendar can become a scheduled social post through Create Post.

What Zapier does not do here: no trigger fires on a new client or a new post, and no action edits or deletes a post or a client. Insights only move three ways (acknowledge, resolve, tag with an External ID). If you want to weigh the alternative, the Jepto Make integration covers the same app on Make, and Make vs Zapier puts the two tools side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts a Zap, here a Jepto Insight being created or resolved. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like resolving an Insight.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan's allowance counts those.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier the moment the event happens. All Jepto triggers are instant.
Filter
A step that lets the Zap go on only when what arrived matches the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app, such as an Insight by its External ID, so later steps can use it.
Connection
Your Jepto account, linked to Zapier once and then reused by every step of every Zap that touches Jepto.
Cost

What a Jepto Zap really costs

On Zapier you pay in tasks, not in triggers. The trigger never costs anything, and looking for new data is free too.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, Jepto works on every plan

Every action that succeeds counts as one task, so a Zap with three actions uses three times as many as a one-action Zap. A failed action is not billed. Jepto is not a premium app, so it runs on the Free plan: 100 tasks a month, but only two-step Zaps. Add a filter or a search and the Zap turns multi-step, which needs a paid plan. The interval grid below only concerns polling triggers, and all three Jepto triggers are instant.

Connect

Connect Jepto to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. You only do this once: every later Zap that touches Jepto reuses the same link.

  2. 02

    Find Jepto and confirm

    Type Jepto in the search box of the dialog, pick it from the results, then click Add connection. Zapier then hands you over to Jepto in a new browser tab.

  3. 03

    Sign in and grant access

    Log in to Jepto in that tab and allow Zapier to reach the account. You need a Jepto account of your own, plus read or write access to any client you don't own but want a Zap to touch.

First Zap

Your first Zap: from anomaly to tracked card

GoalTurn every Jepto anomaly into a Trello card, then write the card's reference back onto the Insight.

  1. 01

    Create the Zap and pick the trigger

    In Zapier, create a new Zap. Choose Jepto as the app that starts it and Insight Created From Anomaly as the event, then select the Jepto connection you just added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent Insights of your account, so you map fields from a real one rather than a blank example.

  3. 03

    Add the card

    Add an action in your project tool, here Trello's Create Card, and map the Insight's details into the card title and description. Test it once and read what comes back.

  4. 04

    Write the reference back to Jepto

    Add Jepto's Add External ID to Insight. Map Client ID, Insight ID and Insight Type from the trigger, and the new card's ID into External ID. This third step makes it a multi-step Zap, so a paid plan.

  5. 05

    Publish

    Test the last step, then click Publish to switch the Zap on. From then on, each new anomaly gets its card straight away; Insights raised before that stay where they are.

Triggers

Jepto triggers on Zapier

3 events start a Zap when something happens in Jepto, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Insight Created From Anomaly

Instant trigger

In Zapier“Triggers when a new Insight is created from an Anomaly being detected.”

Starts your Zap each time Jepto spots an anomaly and turns it into a fresh Insight. Short version: the problem leaves Jepto. Its details flow to the next steps, so someone on your side can look at the unexpected change before a client notices it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when an odd shift in a client's numbers should land as a card on the board your account managers already work from.
Watch out
only anomalies flagged after you publish reach the Zap, so Insights already open in Jepto still need handling by hand.
2

Insight Created From Automation

Instant trigger

In Zapier“Triggers when a new Insight is created from an Automation Job.”

Runs whenever one of your Jepto automation jobs produces a new Insight. The finding of a rule you built in Jepto then travels on to another app instead of waiting in the dashboard for someone to log in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when what an automation job finds should reach a shared channel or a support queue, with the client named in the message.
Watch out
anomalies and automations are two separate triggers, so getting both into one place means two Zaps feeding the same destination.
3

Insight Resolved

Instant trigger

In Zapier“Triggers when an Insight is resolved.”

Kicks off when an Insight gets marked as resolved, and passes along which one it was so the other tools tracking it can catch up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to move the matching card to Done, or to drop a short note in the client's channel once the issue is behind you.
Watch out
the trigger asks for an Insight Type, Anomaly or Automation, so one Zap follows one kind of Insight; covering both takes a second Zap.
Actions

Jepto actions on Zapier

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

1

Acknowledge Insight

Action

In Zapier“Acknowledge an active Insight.”

Marks an active Insight as seen: Jepto learns that someone has picked it up, while the issue stays open.

When to use it
when a card gets assigned in your project tool and Jepto should show that the anomaly is being handled.
Watch out
it needs the Client ID, the Insight ID (both 16-character codes Jepto generates) and the Insight Type; map them from a trigger or a search rather than typing them.
2

Add External ID to Insight

Action

In Zapier“Adds an External ID to your Insight, to enable tracking and resolution in third party tools and management platforms.”

Attaches your own reference, such as a card or ticket number, to a Jepto Insight. That External ID is what lets a later Zap find the Insight again starting from the other tool.

When to use it
right after a task is created for an anomaly, to tie the two records together both ways.
Watch out
four values are required here (Client ID, Insight ID, Insight Type, External ID); take the external one from the step that created the card.
3

Create Client

Action

In Zapier“Creates a new Client in your Account.”

Adds a new client to your Jepto account. Two values, both required: a name and a website domain.

When to use it
when a deal marked won in your CRM should hand the account team a client that is ready to be worked on in Jepto, with nobody retyping it.
Watch out
duplicates. Put Find Client by Name first, or tick its find-or-create option.
4

Create Post

Action

In Zapier“Creates a new Social Post in your Account.”

Queues a social post in Jepto for a given client and profile, with a status and the date and time it should go out.

When to use it
when an approved line in a content calendar sheet should turn into a scheduled post without anyone retyping it.
Watch out
Client, Post Status, Schedule Date/Time and Profile are all mandatory, so the source row has to carry a usable date.
5

Resolve Insight

Action

In Zapier“Resolve an active Insight.”

Closes an active Insight for good, the last state an issue can reach in Jepto.

When to use it
at the end of a Zap that starts when a ticket or card is completed elsewhere, after a search has found the matching Insight.
Watch out
it takes the same three codes as acknowledging, mapped from a trigger or a search; a step that fails is not billed, but nothing gets closed either.
Searches

Jepto searches on Zapier

3 search steps look for data that already exists in Jepto, so a later step can use it.

Searches sit at the bottom of the action event list, under the SEARCH heading. Each one either hands over what it found or comes back empty, and three settings decide what happens next.

1

Find Client by Name

SearchFind or create

In Zapier“Finds an existing Client by name.”

Looks up a Jepto client from its name and hands its details to the next steps. That's how a Zap gets the client a post or an Insight action asks for.

When to use it
before Create Post, when the source sheet only knows the client by name.
Watch out
the editor also lists Find or Create a Client. It is this same search with creation ticked, so a missing client gets created on the spot instead of stopping the Zap.
2

Find Insight by External ID

Search

In Zapier“Finds an Insight via its External ID. You can set External IDs in the app, or by using the Add External ID to Insight action.”

Tracks down the Insight that carries a given External ID, whether that reference was set in Jepto or through Add External ID to Insight.

When to use it
when a card closes in your project tool and the Zap must work out which Insight it belonged to before resolving it.
Watch out
it only finds Insights that already carry an External ID; anything never linked comes back empty.
3

Find Insight by Insight ID

Search

In Zapier“Finds an Insight using its alphanumeric ID.”

Fetches one Insight from its Jepto code and gives later steps its current details.

When to use it
when another tool stored the Insight ID earlier and a Zap needs up-to-date information on it.
Watch out
like the Insight actions, it asks for Client ID, Insight ID and Insight Type, so store all three together wherever you keep them.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switched on, the Zap carries on with empty values.
  2. Create Client if it doesn't exist yet?
    Only offered on Find Client by Name. Ticking it turns the search into a find-or-create: the setting above disappears and Zapier asks for what a new client needs.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass every match on at once.
When it breaks

When a Jepto Zap breaks

Zapier ties no help article to Jepto, so the cases below come from how every Zap behaves, applied to this app.

None of them shows up as a clear error the first time. If a Zap keeps misbehaving after these checks, the Zapier troubleshooting page goes through the usual fixes.

  • Older Insights never come in

    A Zap only reacts to what happens after you publish it. Insights already open in Jepto stay there, and moving that backlog is a separate job.

  • A Zap that keeps setting itself off

    If a Zap writes into the very place its own trigger watches, it fires again and again and burns through your task count fast.

  • A sudden burst held back

    A huge batch of Insights at once, after a bulk import or a migration, can be held back by Zapier's flood protection instead of running straight through.

  • Codes typed by hand

    Insight steps need the Client ID, the Insight ID and the Insight Type together. Map all three from the trigger or a search rather than typing them by hand.
Need help

Need help automating Jepto with Zapier?

A person reads every message.

FAQ

Jepto and Zapier: common questions

01Is the Jepto Zapier integration free?
Yes. Jepto is not a premium app on Zapier, so it works on the Free plan. That plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stays at two steps: one trigger and one action. The anomaly-to-card Zap that writes an External ID back has three steps, so it needs a paid plan. The same goes for any Zap with a filter or a search, such as finding an Insight by its External ID before resolving it. Plan prices move often, so check the current grid on Zapier before choosing.
02How many tasks does a Jepto Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that turns an anomaly into a card uses one task per anomaly. Add the step that writes the card reference back to Jepto and it becomes two tasks per anomaly. Adding a search before an action makes the Zap multi-step, so it then needs a paid plan. An action that fails is not counted against your plan. Checking for new data never costs a task either, however often it happens.
03Do Jepto triggers work in real time?
Yes. All three Jepto triggers, Insight Created From Anomaly, Insight Created From Automation and Insight Resolved, are instant: Jepto calls Zapier as soon as the event happens. The 15-minute check of the Free plan does not apply to them, and neither do the shorter intervals of paid plans. In the editor, a Zap built on one of them shows a lightning bolt. The one thing an instant trigger won't do is look backward: anything that happened before the Zap was switched on is ignored.
04What does connecting Jepto to Zapier require?
A Jepto account of your own, plus read or write access to any client you don't own but want a Zap to touch. In Zapier, open the Apps page, click + Add connection, search for Jepto and confirm with Add connection. A tab opens where you sign in to Jepto and grant Zapier access. That single connection is then reused by every Zap you build with Jepto, so you won't repeat the sign-in for each new automation.
05Where do the Client ID and Insight ID come from?
From Jepto itself. Both are 16-character codes the system generates, and the Insight actions and the Find Insight by Insight ID search ask for them along with the Insight Type, Anomaly or Automation. Nobody is expected to type them. Map them from an Insight trigger earlier in the Zap, or from a search step that found the Insight. If you store them in another tool for later, keep all three side by side, otherwise the next Zap can't point at the right Insight.
06What if the Jepto operation you need isn't on Zapier?
Then it can't be added from the editor: the list of triggers, actions and searches comes from Jepto's own Zapier app. Today there is no trigger on a new client or a new post, and no action to edit or delete them. Two workarounds exist. Chain a search and an action, for instance finding an Insight by External ID and resolving it. Or check whether the Make version of the Jepto app covers the missing step. For anything beyond that, the Hack'celeration team can look at the case with you.
07Zapier, Make or n8n for Jepto?
It depends on what matters most to you. Zapier suits a short Zap built fast, and here all three Jepto triggers are instant, even on the Free plan. Make suits flows with many branches where you want to see every path on one canvas, and Jepto has its own app there. n8n suits teams who host their tools themselves and are comfortable assembling steps; check whether a ready-made Jepto node exists before choosing it. None of the three is better for every case.
Same platform

Other docs you might need on this stack.

Browse all integrations