Jestor Make integrationAutomate Jestor with Make.
Can Make react the moment a Jestor record changes? Yes: the Jestor Make integration offers 3 instant triggers and 2 actions. This guide is for ops teams who run their work in Jestor: you will link your account, build a first scenario and test it.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Jestor Make integration do?
The Jestor Make integration links your Jestor account to Make so records can start automations and be created by them. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, such as a trigger that listens or an action that writes.
A team that hears about new work. Watch Created Record starts a scenario as soon as someone adds a record in Jestor, so the next module can post it where your team already reads messages.
A clean audit trail. Watch Deleted Record and Watch Updated Record tell Make when a record disappears or changes. Sending those events to a log sheet gives a manager a history without asking anyone to fill it in by hand.
Jestor filled by other tools. Create a Record goes the other way: a form, a signed quote or a support ticket in another app becomes a Jestor record. For anything the listed modules skip, Make an API Call reaches the rest of the Jestor API with the same connection.
Know the limit before you start: Make flags its own Jestor documentation as limited, so it gives no field list, no connection prerequisites and no troubleshooting notes for this app. Expect to discover the fields inside the module once your account is linked. If you are still choosing a tool, the n8n vs Make comparison and the Make pricing breakdown help you decide, and the Make training covers the editor from zero.
How do you connect Jestor to Make?
- 01
Add a Jestor module
In a scenario, search for Jestor, pick any of its modules and click Create a connection. A connection is your Jestor account linked to Make once, then reused by every Jestor module you add later.
- 02
Name the connection
This step is optional, but a clear name such as the workspace it belongs to saves confusion later, especially if several people or several Jestor accounts end up sharing the same Make organization.
- 03
Authorize and save
Either approve Make on the Jestor page that opens or paste the key Jestor gives you, depending on what the window asks for. Then click Save and the module is ready to fill in.
Your first scenario with Jestor and Make
GoalWhen a request comes in through another app, such as your form tool, Make turns it into a new record in Jestor.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes the first module, the one that starts everything.
- 02
Start with the source app
Pick the app where requests arrive, such as your form or shop tool, and its module that watches new entries. Each entry will arrive as a bundle, one item passed from module to module.
- 03
Add Create a Record
Click the + on the right of that module, search for Jestor and choose Create a Record. Select your connection, or click Create a connection, then map the incoming data into the Jestor fields.
- 04
Test with Run once
Click Run once and send one test entry from the source app. Open the bubble above each module to read the bundle it received, then check the new record in Jestor.
- 05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. Each module run counts as one operation, which is what Make measures on your plan.
Jestor triggers in Make
3 modules start a scenario when something happens in Jestor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Jestor as soon as it happens.
Watch Created Record
Instant triggerIn Make“Triggers when a new record is created in Jestor”
Watch Created Record gives you a scenario that starts the second a new Jestor record exists, carrying that record into the next module as a bundle. It is the natural entry point for anything that must happen once per new item.
Watch Deleted Record
Instant triggerIn Make“Triggers when a record is deleted in Jestor”
Removal is the one event people forget to track, and this trigger catches it: whenever a record is deleted in Jestor, your scenario receives it and can keep a trace somewhere else.
Watch Updated Record
Instant triggerIn Make“Triggers when a record is upated in Jestor”
Changes to an existing record become a starting signal with this trigger, so the rest of your stack follows along when someone edits Jestor instead of drifting out of date.
Jestor actions in Make
Jestor gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Record
ActionIn Make“Create new record in Jestor”
This action writes a brand new record into Jestor from data that comes from earlier modules, so information captured elsewhere lands in your workspace without anyone copying it.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When none of the four other Jestor modules covers your need, this one lets you call any endpoint of the Jestor API while reusing the same connection, so you skip handling credentials yourself.
Need help automating Jestor with Make?
A person reads every message.
