Resources · Make integration

Inistate Make integrationAutomate Inistate with Make.

Make keeps an eye on Inistate for you, and writes back to it. The Inistate Make integration gives you 13 modules: 5 triggers that watch your entries, states and activities, plus 8 actions. This guide walks you from the API key to a first working scenario.

Try the Inistate integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Inistate Make integration do for you?

The Inistate Make integration links your Inistate account to Make, a visual tool where you chain apps together without writing code. Make watches Inistate for new entries, updates, state changes and activities, then acts on them: it can create, update, duplicate or delete entries, assign tasks and move states, in Inistate or in any other app you use.

Hand off new work the moment it lands. Watch Created Entries picks up each new entry, and Assign a Task to a User gives it an owner, so nobody has to sort the pile by hand.

Keep other tools in step with your workflow. Watch State Changes notices when an entry moves to another state; the next module can copy that change into a spreadsheet, a chat channel or your CRM.

Feed Inistate from the outside. A form, an email or a row from another app can become an entry through Create a Entry, and Update a Entry keeps it current when the source changes.

Keep the limits in mind. The official Make documentation for Inistate describes its own content as AI-generated and asks you to verify important details, so test each module with a real entry before you rely on it. When no listed module fits, Make an API Call reaches the rest of the Inistate API with the same connection. If you are still choosing a platform, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Inistate to Make?

  1. 01

    Generate your Inistate API key

    In Inistate, open Account, then Integration, and generate a new API key. Copy the key shown on screen: Make needs it to reach your account, and you need an active Inistate account for this.

  2. 02

    Add an Inistate module in Make

    In your Make scenario, add any Inistate module and click Create a connection. A connection is your Inistate account linked to Make once, then reused by every Inistate module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like (it is optional), paste the API key you copied, and confirm. Make then lists what it can read in your Inistate account.

First scenario

Your first scenario with Inistate

GoalWhen a new entry is created in Inistate, Make assigns a task on it to the right teammate.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. A scenario is the automation you build: a chain of modules. Click the + to add the first one.

  2. 02

    Add Watch Created Entries

    Search for Inistate, pick Watch Created Entries and choose your connection. This trigger starts the scenario with each new entry it finds, one bundle (one item passed along) per entry.

  3. 03

    Chain Assign a Task to a User

    Click the + on the right of the trigger, add Assign a Task to a User, then map the entry coming from the trigger into its fields. Make shows what it can read once the connection exists.

  4. 04

    Test with Run once

    Create a test entry in Inistate, then click Run once. Open the bubbles above each module to read the bundles they received and check that the task went to the right person.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Keep the default or adjust it, then switch the scenario on.

Triggers

What can start an Inistate scenario?

5 modules start a scenario when something happens in Inistate. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Inistate as soon as it happens.

Inistate1Watch Changes Information

Watch Changes Information

triggerIn the docs only

Watch Changes Information hands your scenario the change details Inistate records, so the next modules can react to what was modified rather than just to the fact that something moved.

How it fires
scheduled, judging by its name (the doc gives no type). Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
pick it when a manager wants a readable trail of edits sent to a shared channel or appended to an audit sheet.
Watch out
the Make documentation gives no description for this module, so run it once on a real change and read the bundle before you map anything.
Inistate2Watch Created Entries

Watch Created Entries

triggerIn the docs only

Watch Created Entries brings each freshly created Inistate entry into your scenario as its own bundle, which makes it the natural starting point for intake flows.

How it fires
scheduled. Make checks the app on the scenario's schedule, so new entries arrive in batches rather than the second they appear.
When to use it
choose it when every new request, order or case recorded in Inistate needs an owner, a copy elsewhere or a welcome message.
Watch out
it reacts to creation only; edits made later to the same entry need Watch Entry Updates instead.
Inistate3Watch Entry Updates

Watch Entry Updates

triggerIn the docs only

Watch Entry Updates starts your scenario whenever an existing entry has been edited, so downstream tools always get the latest version of the record.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the entries it finds updated since the last check.
When to use it
use it to mirror Inistate records into a spreadsheet or a CRM that must stay current after every edit.
Watch out
if the same scenario also runs Update a Entry on those entries, each write can count as a fresh update, so filter carefully to avoid feeding your own changes back in.
Inistate4Watch New Activities

Watch New Activities

triggerIn the docs only

Watch New Activities picks up the activities recorded in Inistate and turns each one into a bundle, giving you a feed of what people actually did on your entries.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at least that on the Free plan.
When to use it
reach for it when a team lead wants each logged activity posted to a chat channel or copied into a reporting sheet.
Watch out
every activity found is a bundle, and every module after the trigger spends one operation per bundle, so busy accounts use your plan faster.
Inistate5Watch State Changes

Watch State Changes

triggerIn the docs only

Watch State Changes lets your scenario follow an entry through your Inistate workflow, starting whenever an entry moves from one state to another.

How it fires
scheduled. Make checks the app on the scenario's schedule and reports the state changes found since its previous check.
When to use it
it fits approval chains, where a move to an approved or closed state should notify the requester or trigger the next step in another app.
Watch out
a filter after the trigger keeps only the states you care about; without one, every transition costs operations downstream.
Modules

What can Make do in Inistate?

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

Inistate1

Assign a Task to a User

ActionIn the docs only

Assign a Task to a User puts a named person in charge of the next piece of work, so an entry never sits unowned after it arrives.

When to use it
right after Watch Created Entries, when each new case should land with a specific teammate based on data from the trigger.
Watch out
map the user from the incoming bundle instead of typing one fixed name, or every task goes to the same person.
Inistate2

Change a State to a User

ActionIn the docs only

Change a State to a User moves work forward in your Inistate workflow from outside the app, tying the new state to a person.

When to use it
when an event elsewhere, such as a signed document or a paid invoice, should advance the matching entry without anyone clicking in Inistate.
Watch out
paired with Watch State Changes in one scenario, this module can trigger itself again; test the loop with Run once first.
Inistate3

Create a Entry

ActionIn the docs only

Create a Entry turns data from another app into a new Inistate record, so requests stop arriving by copy and paste.

When to use it
after a form submission, an incoming email or a new CRM deal, when that information must start its life in Inistate.
Watch out
a scenario that retries or runs twice on the same source item creates two entries; check your source trigger only passes each item once.
Inistate4

Delete a Entry

ActionIn the docs only

Delete a Entry removes a record from Inistate, which keeps test data and cancelled requests out of your working views.

When to use it
when an order or request is cancelled in the source system and the matching Inistate entry has no reason to stay.
Watch out
a deletion does not come back with a click; add a filter before this module and try it on a test entry with Run once.
Inistate5

Duplicate a Entry

ActionIn the docs only

Duplicate a Entry copies an existing record, giving you a ready-made starting point instead of rebuilding the same entry by hand.

When to use it
for recurring jobs built from a model entry, like a standard onboarding file copied for each new hire announced in your HR tool.
Watch out
the copy is a new entry, so a scenario running Watch Created Entries will pick it up too.
Inistate6

Make an API Call

ActionIn the docs only

Make an API Call sends your own request to the Inistate API through the connection you already set up, covering whatever the other modules leave out.

When to use it
when you need an Inistate feature that none of the 13 listed modules reaches, and you can read the vendor's API reference.
Watch out
you build the request yourself, so check each endpoint against Inistate's documentation before running it on live records.
Inistate7

Perform an Activity

ActionIn the docs only

Perform an Activity records an action on an Inistate entry from your scenario, so steps done in other tools still show up in Inistate.

When to use it
when a call logged in your phone system or a reply sent from your helpdesk should appear as activity on the matching entry.
Watch out
a scenario started by Watch New Activities that also runs this module can loop on its own output.
Inistate8

Update a Entry

ActionIn the docs only

Update a Entry rewrites an existing Inistate record with fresh values, so the entry matches what changed in your other apps.

When to use it
when a customer edits their details in a form or a deal moves in your CRM, and the related entry must follow.
Watch out
the module needs to know which entry to change; map its identifier from an earlier module rather than guessing it.
Need help

Need help automating Inistate with Make?

A person reads every message.

FAQ

Inistate and Make: common questions

01Is the Inistate Make integration free?
Yes, on the Make side. Inistate is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between 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) lower the interval to 1 minute and count usage in credits per month. You still need an active Inistate account and its API key; Inistate's own subscription is set by Inistate, on its pricing page.
02What do you need to connect Inistate to Make?
Two things: an active Inistate account and an API key. In Inistate, open Account, then Integration, generate a new key and copy it. In Make, add any Inistate module, click Create a connection, optionally name it, and paste the key. The connection is then reused by every Inistate module in your scenarios, so you only do this once per account. If the key stops working, generate a new one in Inistate and paste it into the existing connection.
03Does the Inistate trigger in Make fire in real time?
No. Going by their names, all 5 Inistate triggers are scheduled: the Make doc lists them without a type, and none is marked instant. Make checks Inistate on the scenario's schedule and picks up what changed since the previous check. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans can go down to 1 minute. If you need a faster reaction, a shorter schedule on a paid plan is the lever listed for this app.
04What if the Inistate module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Inistate API with the connection you already created, so you can reach features the other 12 modules do not cover. You write the request yourself, based on Inistate's API documentation. Also note that the Make help page for Inistate says its content is AI-generated and may contain mistakes, so for anything unclear, contact Inistate directly. Test every custom request with Run once before switching the scenario on.
05Make or n8n for Inistate?
It depends on what you check first. On Make, Inistate comes with 13 ready modules, including 5 scheduled triggers and a generic API call, and runs from the Free plan. The same app often has an n8n node too, so look at what n8n offers for Inistate before you commit, and compare the modules you actually need rather than the brand. On Make, anything the listed modules miss can still go through Make an API Call with the same connection.
Same platform

Other docs you might need on this stack.

Browse all integrations