Resources · Zapier integration

Inistate Zapier integrationAutomate Inistate with Zapier.

The Inistate Zapier integration gives you 6 triggers and 7 actions, all of them about entries, states and activities. Every trigger is instant, so a free plan reacts as fast as a paid one. There are 0 searches, which shapes how you point an action at the right entry.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Inistate Zapier integration actually does

Inistate runs your business processes as entries that move from state to state inside modules, without code. The Inistate Zapier integration lets Zapier watch those entries and act on them: when something happens to an entry, a Zap (the automation you build in Zapier) creates, edits, moves or assigns another one for you.

Three results people build first. An owner on every new record: New Entry starts the Zap and Assign hands the entry to a colleague as a task, so nothing sits unclaimed. A process that pushes itself forward: Activity Performed spots an approval, and Change State moves a related entry to its next stage. A follow-up when a date falls due: Information Due fires when a date field of an entry is reached, and Perform Activity runs the step your process expects at that point.

What Zapier does not do here: it offers no search for Inistate. No step can look up an entry by its content, so any action that targets an existing entry needs its document ID (something like BRN00005) handed over by the trigger. In practice, the entry that started the Zap is the one you can act on. Zapier also cannot reach back in time: entries created before the Zap was switched on are never picked up.

If you are weighing tools, the same breakdown exists for the Inistate Make integration, and our Make vs Zapier comparison puts the two tools next to each other.

Vocabulary

Zapier in one minute

Seven words you will meet in the editor. Each one is explained once, here, then used as is on the rest of the page.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan allowance counts these.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling one is checked on a timer. Inistate only has instant ones.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Connection
Your Inistate account, linked to Zapier once and then reused by every step that talks to Inistate.
Cost

What it really costs

Zapier bills tasks, and only completed actions count. The trigger is free, and so is all the waiting in between.

  • TriggerNever costs a task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, Inistate works on the free plan

Inistate is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap. The free plan stops at two steps, one trigger and one action. Add a second action or a filter and it becomes a multi-step Zap, which needs a paid plan. An action that fails is not counted. The polling grid below does not apply here: every Inistate trigger is instant.

Connect

Connect your Inistate account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A search box opens: type Inistate and pick it from the results. You only do this once per account.

  2. 02

    Sign in to Inistate

    Click Add connection. A new tab asks you to log in to Inistate with the account the Zaps will act as. Use an account that can see the workspaces and modules you plan to automate.

  3. 03

    Grant access

    Accept the access request so Zapier can read and write on your behalf. From then on, the connection is offered in every Inistate step, triggers and actions alike, without logging in again.

First Zap

Your first Inistate Zap, step by step

GoalEach new purchase request entry gets an owner, but only the ones that need a review.

  1. 01

    Build the trigger

    Create a Zap and choose Inistate with New Entry. Pick the Workspace, then the Module holding your purchase requests. Only entries created there will start this Zap.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries of that module, so you map the next steps on a real one instead of guessing what it contains.

  3. 03

    Add the filter

    Add a Filter step, then set the field to look at, the rule, and the value. Pick a number rule for amounts and a text rule for words: the wrong type never passes.

  4. 04

    Add the assignment

    Add Inistate with Assign. Map the entry's document ID from the trigger into Entry, then choose the user in Assign To. Test this step on the sample entry.

  5. 05

    Publish

    Click Publish to switch the Zap on. Remember that the filter makes it a three-step Zap, which needs a paid plan. On the free plan, drop the filter and assign every entry.

Triggers

Inistate triggers

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

1

Activity Performed

Instant trigger

In Zapier“Triggers when an activity performed for an entry.”

Starts a Zap when an activity is performed on an entry of the module you pick. You get the entry the activity touched, ready to pass on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a manager approves a leave request and HR needs a matching record opened in another module straight away.
Watch out
you pick Workspace, Module and Activity up front, so one Zap listens to one activity only. Two activities mean two Zaps.
2

New Entry

Instant trigger

In Zapier“Triggers when a new entry is created.”

Fires once for each entry created in the module you choose. This is the cleanest starting point when you want one reaction per new record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new support ticket entry should land on someone's desk before anyone has to chase it.
Watch out
if a Zap of yours also creates entries in that same module, it will set itself off. Keep the target module different.
3

Updated Entry

Instant trigger

In Zapier“Triggers when an entry is modified.”

Reacts whenever an entry in the chosen module is modified, whatever was changed. It is broad on purpose: any edit counts, so a single entry can start the Zap many times over its life.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a module where edits are rare and each one deserves a reaction, such as reviewing who is in charge of the record.
Watch out
pairing it with Create Entry produces a duplicate on every edit, and Edit Entry on the same entry sets it off again. If only one field matters, Changed Information is the narrower choice.
4

Changed Information

Instant trigger

In Zapier“Triggers when information of an entry's field has changed.”

Narrower than Updated Entry: it starts the Zap only when one named field of an entry changes, and ignores edits made anywhere else in the record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the priority field of a maintenance request is raised, and the request needs a new owner.
Watch out
Field is a required setting next to Workspace and Module. Watching two fields takes two Zaps, one per field.
5

Information Due

Instant trigger

In Zapier“Triggers when a information type of date or date time of an entry is up.”

Turns a date into an event. When a date or date-time field of an entry is reached, the Zap starts, which lets a deadline stored in Inistate drive work without anyone watching a calendar.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a contract entry reaches its renewal date and the account owner should be put in charge of it.
Watch out
the field you pick must be an information of type Date or Date Time in Inistate. Choose it in the setting of the same name.
6

Changed State

Instant trigger

In Zapier“Triggers when state of an entry has changed.”

Follows your process map: the Zap starts when an entry moves into the state you name. Because states are how Inistate models progress, this is often the most precise signal you have.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an order entry reaches Shipped and the invoicing module needs a fresh entry of its own.
Watch out
it asks for a Trigger and a State setting on top of Workspace and Module. Pick the state your process actually reaches.
Actions

Inistate actions

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

1

Assign

Action

In Zapier“Assign an inistate user to an entry as task”

Puts an Inistate user in charge of an entry, as a task on their list.

When to use it
new requests should never wait in a shared queue without a name next to them.
Watch out
Assign To must be a user of your Inistate account, and the Entry field needs the document ID.
2

Change State

Action

In Zapier“Changes the state of an entry through activity performed”

Moves an entry to another state by running the activity that leads there, just as a person would.

When to use it
an approval somewhere else should push the related entry to its next stage.
Watch out
paired with Changed State on the same module, it can start a loop. Keep a filter between them.
3

Create Entry

Action

In Zapier“Creates an entry”

Adds a brand new entry to the module you choose and fills its information from earlier steps.

When to use it
a state change in one process should open a record in another, like a shipped order opening an invoice entry.
Watch out
only Workspace and Module are required, so an empty mapping still creates a near-empty entry.
4

Delete Entry

Action

In Zapier“Deletes an entry”

Removes an entry from its module, identified by its document ID.

When to use it
a cancellation in your process should clear out a draft entry that no longer has a reason to exist.
Watch out
test it on a dummy entry first. A wrong ID mapping removes the wrong record.
5

Duplicate Entry

Action

In Zapier“Duplicate an entry”

Copies an existing entry so you start from its content instead of retyping it.

When to use it
a recurring job is closed and its next occurrence should be prepared from the same details.
Watch out
it needs the source entry, so the trigger must hand you that entry's reference.
6

Edit Entry

Action

In Zapier“Edits an entry's data”

Rewrites the data of an entry that already exists, found by its document ID.

When to use it
a date falls due and a status note on the same record should be filled in.
Watch out
Entry takes the document ID, for example TSX00150. With no search available, it has to come from the trigger.
7

Perform Activity

Action

In Zapier“Performs an activity to an entry”

Runs one of your process activities on a given entry, the same activity a user would pick in Inistate.

When to use it
a due date is reached and the reminder activity of your process should run on that entry.
Watch out
Activity is a required setting, so one step runs one named activity. Map the document ID into Entry from the trigger.
When it breaks

When an Inistate Zap breaks

Zapier publishes no help article dedicated to Inistate, so the failures below are the general Zapier limits, applied to how Inistate works.

None of them raises an alarm on its own. A Zap can look healthy for days while it creates duplicates or burns tasks in a loop. When something feels off, our Zapier troubleshooting page walks you through the checks.

  • No catch-up on old entries

    A Zap only reacts to what happens after you publish it. Entries that already existed are never picked up; moving that backlog is a separate job.

  • A state that triggers itself

    Changed State plus Change State on the same module, or New Entry plus Create Entry, can set the Zap off again and again and eat your tasks fast.

  • Duplicates from Updated Entry

    Updated Entry fires on every edit. Any Zap that creates an entry from it makes one new record per change, not one per source entry.

  • Bulk imports held back

    Importing many entries at once can send Zapier a sudden flood of events. Its flood protection may hold that batch back instead of running it.
Need help

Need help automating Inistate with Zapier?

A person reads every message.

FAQ

Inistate Zapier integration: questions

01Is the Inistate Zapier integration free?
Yes, as far as Zapier is concerned. Inistate is not a premium app, so it works on the free Zapier plan, which gives you 100 tasks a month and unlimited Zaps. The limit is the shape: a free Zap has two steps, one trigger and one action. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. Plan the filter before you build, not after.
02How many tasks does an Inistate Zap use?
One per action that completes. The trigger never counts, so an entry that starts a Zap costs nothing by itself. A Zap that only assigns the new entry uses one task each time it runs. A Zap that assigns it and then changes its state uses two. An action that fails is not counted against your plan. A filter that stops the Zap means the actions after it never run, so they cost nothing either. Keep an eye on loops, which multiply this count without you noticing.
03Does it work in real time?
Yes. All six Inistate triggers are instant: Inistate tells Zapier the moment an entry is created, updated, moved to a new state, hit by an activity, changed in one field or reaches a due date. The Zap then starts right away, whatever your plan. The polling interval grid, 15 minutes on the free plan, does not apply to any of them. In the editor, you will see a lightning bolt on a Zap built on one of these triggers.
04What does it take to connect Inistate to Zapier?
An Inistate account and access to what you want to automate. Every Inistate trigger and action asks for a Workspace and a Module, so the account you connect must be able to see them, and to edit entries there if your actions write. You connect it once from the Apps page of Zapier, with + Add connection, then you sign in to Inistate and accept the access request. Every Inistate step then reuses that same connection.
05How do you target the right entry without a search step?
By passing along the document ID the trigger gives you. Inistate offers no search in Zapier, so no step can look up an entry by its content. Actions such as Edit Entry, Assign, Change State or Delete Entry ask for the entry's document ID, written like BRN00005. In practice, the entry that started the Zap is the one you can act on, or the one your Create Entry step just made. Plan your Zap around that single entry.
06What if the Inistate action you need is not in Zapier?
Then the Zapier integration cannot do it directly, and it is worth knowing before you build. The seven actions cover creating, duplicating, editing, assigning, moving, running an activity on and deleting entries, plus no searches. If what you need is outside that list, compare what the Inistate Make integration offers, or ask the Hack'celeration team to look at a workaround. Do not count on an operation Zapier no longer shows in its editor.
07Zapier, Make or n8n for Inistate?
It depends on your criteria rather than on a winner. Look at three things: which Inistate operations each tool exposes, how each one bills a run, and who on your team will maintain the automation. On Zapier, the facts are on this page: six instant triggers, seven actions, tasks billed per successful action, two-step Zaps on the free plan. Put the same questions to the other tools before you choose, and pick the one that matches your process, not a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations