Resources · Zapier integration

OKrunit Zapier integrationAutomate OKrunit with Zapier.

The OKrunit Zapier integration offers 2 triggers, 3 actions and 2 searches. Its main trick: a Zap can stop and wait until a person approves or rejects, then carry on. The two triggers are polled, so decisions reach your other tools on Zapier's timer, not instantly.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OKrunit Zapier integration is for

OKrunit puts a human checkpoint in front of automated work, so an AI agent or a script does not publish, deploy or spend before someone says yes. On Zapier, that checkpoint becomes a step: a Zap (an automation made of one trigger and the actions that follow) can pause on OKrunit, wait for a decision, then continue.

Three results people build first. A gate before anything risky: Request Approval holds a Zap that would send a mass email or push a price change, and the next step only runs after a reviewer decides. A decision that travels: Approval Decided tells your chat, your ticket tool or your CRM which way it went. An audit trail: Create Activity Log writes a line for each automated event worth keeping, and Add Comment attaches context to a pending request.

What it does not do. The two triggers are polling ones: Zapier checks OKrunit on a timer, so a decision can take up to 15 minutes to show up on the free plan. Create Activity Log does not open an approval request, despite its key, and the Zap moves on at once. There is no action to approve or reject from Zapier; the decision belongs to a human in OKrunit. The Zapier review gives the wider picture, and n8n vs Zapier comparison is there if you are weighing another tool.

Vocabulary

Zapier vocabulary in one minute

Seven words return on every line below. Plain English, one line each.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap, such as a new approval request in OKrunit. Once the Zap is on, Zapier watches for it.
Action
What the Zap does after it starts: the step that writes, sends or, with OKrunit, pauses for a human decision.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer; an instant one is pushed by the app. Both OKrunit triggers are polling ones.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in an app, like an approval request, so later steps can reuse what it found.
Cost

What an OKrunit Zap really costs

The OKrunit triggers cost nothing, and neither do Zapier's checks for new requests, however often they run. Only completed actions are billed.

  • Trigger and polling checks0 task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • OKrunit triggersPolling, interval set by plan

Each action that succeeds counts as one task; an action that fails is not counted. A gate in the middle of a Zap means at least two actions plus the trigger, so the Zap is multi-step and needs a paid plan, as does any search or filter. The free plan gives 100 tasks a month and unlimited two-step Zaps, enough for Approval Decided followed by one alert. OKrunit is not a premium app. The grid below matters here: it sets how quickly the two polling triggers notice a new request or a decision, and on paid plans a check can also be run by hand.

Connect

Connect your OKrunit account to Zapier

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. You need an OKrunit account first, with access to the approval requests of the organization your Zaps will work in.

  2. 02

    Pick OKrunit

    Search for OKrunit in the dialog, select it and click Add connection. A new tab opens on the OKrunit side, where you sign in with the account that will own the requests.

  3. 03

    Sign in and grant access

    Log in to OKrunit in that tab and allow Zapier to reach the account. The connection then appears in your Apps list, and every OKrunit step in your Zaps reuses it.

First Zap

Your first OKrunit Zap, step by step

GoalEvery rejected request in OKrunit warns the person who asked, so nobody waits for a yes that will never come.

  1. 01

    Set the trigger

    Create a Zap, pick OKrunit and Approval Decided as the event, then select the OKrunit connection you made in the previous section.

  2. 02

    Test it

    Run the test: Zapier brings back the three most recent decisions, so you map fields on a real verdict rather than on an empty sample.

  3. 03

    Add the filter

    Add a Filter step, pick the decision field, choose a text rule and type the rejected value. Only rejections go further; this makes the Zap multi-step, so a paid plan is needed.

  4. 04

    Add the alert

    Add the chat action and send a direct message to the requester with the details of the rejected request, so they know where things stand.

  5. 05

    Test and publish

    Test each step once, read what came back, then publish. Decisions taken from now on are checked on your plan's interval; older ones are not replayed.

Triggers

The 2 OKrunit triggers

2 events start a Zap when something happens in OKrunit. Zapier checks for them at the interval your plan allows.

1

Approval Decided

Polling trigger

In Zapier“Triggers when an approval request is approved or rejected.”

Starts a Zap once someone approves or rejects a request in OKrunit, so the outcome reaches the people and tools waiting on it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
post each verdict in the channel of the team that asked, or close the matching ticket.
Watch out
it covers both outcomes, so add a filter on the decision if approvals and rejections need different follow-ups; that filter makes the Zap multi-step.
2

New Approval Request

Polling trigger

In Zapier“Triggers when a new approval request is created in your organization.”

Picks up every approval request created in your OKrunit organization, whatever created it: an agent, a script or another Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
ping the on-call reviewer so no request sits unseen in the queue.
Watch out
do not use it to start a Zap that itself runs Request Approval in the same organization, or each new request will create another one.
Actions

The 3 OKrunit actions

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

1

Add Comment

Action

In Zapier“Add a comment to an existing approval request.”

Attaches a note to an approval request that already exists, giving the reviewer the context they need to decide.

When to use it
add the customer history or the AI's reasoning to a pending request.
Watch out
it needs the request's Approval ID and a comment of 5000 characters at most.
2

Create Activity Log

Action

In Zapier“Log an activity for audit and tracking purposes. This does not create an approval request. The Zap continues immediately.”

Writes an entry in OKrunit's activity log for audit and tracking, then lets the Zap continue at once.

When to use it
keep a record each time an automation sends a refund or changes a setting, even without a review.
Watch out
despite its key, it never opens an approval request; the title is mandatory and capped at 500 characters.
3

Request Approval

Action

In Zapier“Pause this Zap until a human approves or rejects. The next step runs only after a decision is made.”

Pauses the Zap right there until a person approves or rejects in OKrunit; the next step only runs once a decision exists.

When to use it
before any step you would not want an agent to run alone, like a payment or a public post.
Watch out
everything after it waits on a human, so plan who reviews and how fast.
Searches

The 2 OKrunit searches

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

A search step finds an approval request that already exists so the following steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.

1

Find Approval Request

Search

In Zapier“Find a specific approval request by its ID.”

Fetches one specific approval request from its ID, so a later step can read its status or details.

When to use it
a ticket stores the Approval ID and you want its current state before replying to the customer.
Watch out
the Approval ID is mandatory; without a step that carries it, this search has nothing to look for.
2

Find Approvals

Search

In Zapier“Search for approval requests with filters.”

Looks through your approval requests using filters, handy when you do not hold an exact ID.

When to use it
check whether a similar request is already pending before opening a new one.
Watch out
when several requests match, Zapier keeps the first by default; change that setting if the order matters.

The three settings every search exposes

  1. Successful if no search results are found?
    Left at its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap continues empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. OKrunit exposes no such variant, so neither search can create a missing request.
  3. If multiple search results are found?
    Three ways out when several requests match: keep the first one (the default), stop the Zap, or pass all of them on together.
When it breaks

When an OKrunit Zap breaks

Zapier lists no OKrunit-specific error. The traps below come from polling, from the searches and from Zapier's general limits.

Most surprises are about timing and loops rather than OKrunit itself. The Zapier troubleshooting guide covers each fix in more depth.

  • The decision shows up late

    Both triggers are polled. On the free plan, Zapier checks every 15 minutes, so a verdict given now can wait that long before the Zap starts.

  • Requests multiply on their own

    A Zap started by New Approval Request that runs Request Approval in the same organization creates a request, which starts the Zap again, and burns tasks fast.

  • The Zap stops at a search

    Find Approval Request or Find Approvals found nothing, and by default an empty search halts the Zap. Turn on the no-results setting if that case is normal.

  • Old requests never come through

    A Zap only reacts to what happens after it is switched on. Requests created or decided before stay out, and moving that history is a separate job.

  • A big batch gets held back

    After a bulk import, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection, so the runs you expected do not all start.

  • Same request, one run only

    Zapier remembers what a polling trigger has already seen, so the same request does not start the Zap twice.
Need help

Need help automating OKrunit with Zapier?

A person reads every message.

FAQ

OKrunit Zapier integration: your questions

01Is the OKrunit Zapier integration free?
Yes, OKrunit is not a premium app, so it runs on the free Zapier plan, which gives 100 tasks a month and unlimited Zaps of two steps. Approval Decided followed by one alert fits that limit. A real approval gate does not: a trigger, Request Approval and the step it protects make three steps, so the Zap is multi-step and needs a paid plan. The same goes for any search or filter. Plan prices change often, so check the official grid before committing.
02How many tasks does an OKrunit Zap use?
One per action that succeeds, and nothing for the trigger or for Zapier's checks. A Zap that posts each decision to chat costs one task per decision. A gated Zap with Request Approval and an email costs two per run once both succeed, and a failed action is not billed. Estimate how many requests your agents or scripts create each month, multiply by the actions in the Zap, and size the plan from that figure.
03Does OKrunit trigger Zaps in real time?
No, both OKrunit triggers are polling ones. Zapier checks OKrunit at a fixed interval set by your plan: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. On paid plans the interval can be changed and a check can be run by hand from the editor. The type comes from OKrunit itself and cannot be switched to instant from Zapier, so plan your reviews around that delay.
04What does it take to connect OKrunit to Zapier?
An OKrunit account and a Zapier account. In Zapier, open Apps, click + Add connection, pick OKrunit, sign in in the tab that opens and grant access. The account needs access to the approval requests of your organization. Keep in mind that Add Comment and Find Approval Request ask for an Approval ID, so map it from an earlier OKrunit step. The connection is then reused by every OKrunit step. You do not repeat these steps for the next Zap.
05Does Create Activity Log open an approval request?
No. Despite its internal key, Create Activity Log only writes an entry in OKrunit for audit and tracking, and the Zap carries on immediately without waiting for anyone. To actually stop a Zap until a human decides, use Request Approval. The log needs a title of 500 characters at most, and the + button lets you insert data from earlier steps. Pick it when you want a record, and Request Approval when you want a gate.
06What if the OKrunit operation you need is not there?
Then Zapier cannot do it today, and no editor setting adds it: the list comes from OKrunit. The integration has 2 triggers, 3 actions and 2 searches, and none of them approves or rejects on a reviewer's behalf. Check first whether a combination fits, such as Find Approvals followed by Add Comment. If not, the request goes to OKrunit, or to a tool that reaches it another way. Keep the human decision inside OKrunit either way.
07Zapier, Make or n8n for OKrunit?
Judge on criteria, not on a ranking. Availability first: this page documents the Zapier side, with a ready Request Approval gate; check whether the other tool offers an OKrunit connector before comparing anything else. Timing next: on Zapier both triggers are polled, so the plan sets how fast decisions travel. Budget last: Zapier bills each successful action while the others use different models, so estimate your monthly volume of requests first.
Same platform

Other docs you might need on this stack.

Browse all integrations