KiSSFLOW Zapier integrationAutomate KiSSFLOW with Zapier.
The KiSSFLOW Zapier integration gives you 1 trigger and 3 actions, with 0 searches. Enough to react when a request changes step, open new requests, park drafts and approve from another tool. It runs on the free plan, within the limits below.
Verified Trustpilot reviews · AI, automation & growth agency
What the KiSSFLOW Zapier integration actually does
The KiSSFLOW Zapier integration links your KiSSFLOW workflow processes to the other apps you use, through Zapier. When a request moves from one step to the next, Zapier can react right away. In the other direction, an outside event can open, draft or approve a KiSSFLOW request without anyone retyping it.
Three results show what it is good for. First, a chained process: a purchase request gets approved in one workflow, and Change of Workflow Step sets off Submit a New Request in the next one, say the payment run your finance team owns. Second, a prepared draft: an event in another tool calls Create a Draft Request, so the request sits in the Draft folder of KiSSFLOW and a person checks it before sending it on. Third, an approval from outside: Approve a Request pushes a request to its next step on behalf of a named approver, handy when the decision is taken somewhere else.
Now the limits, because they matter as much. There is no search step for KiSSFLOW on Zapier, so a Zap cannot look up an existing request by itself: the request ID has to come from an earlier step. There is no reject action either, and no way to edit a request already submitted. Only one trigger exists, so anything that is not a step change (a new comment, say) stays invisible to Zapier.
If you are weighing tools, the same app has a KiSSFLOW Make integration page, and there is also our Make vs Zapier comparison.
Zapier words, in one minute
Seven terms come back on 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 in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for that event to show up.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills you for: one action your Zap completes successfully. Your plan counts these and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
- Connection
- Your KiSSFLOW account linked to Zapier once, then reused by every step that talks to KiSSFLOW.
What a KiSSFLOW Zap really costs
Zapier bills tasks, and only actions make tasks. The KiSSFLOW trigger never costs one.
- Free plan100 tasks a month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Trigger cost0 tasks
- KiSSFLOW triggerInstant, no waiting for a check
Each action that succeeds counts as one task, and each action in a Zap counts on its own: a Zap that submits a request and then approves another eats two tasks per run. An action that fails is not counted. Watching for step changes costs nothing at all. KiSSFLOW is not a paid-only app, so it works on the free plan, but that plan builds two-step Zaps only. Add a second action, or a filter, and you have a multi-step Zap that needs a paid plan.
Connect KiSSFLOW to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A dialog opens. You need a KiSSFLOW account first, plus access to every process the Zap will read from or write into.
- 02
Pick KiSSFLOW
Type KiSSFLOW in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the KiSSFLOW side, ready for the sign-in.
- 03
Sign in and allow access
Log in to KiSSFLOW in that tab and grant Zapier access to the account. The connection now shows on your Apps page and every KiSSFLOW step in every Zap reuses it.
Your first Zap: hand an approved request to the next process
GoalWhen a request moves forward in one process, submit a matching request in the next process, but only when the move was an approval.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose KiSSFLOW as the app and
Change of Workflow Stepas the event. Select the connection you made earlier. - 02
Set the process
Fill in Process Name with the workflow to watch. The trigger also passes on the action that caused the move, such as Approve or Reject.
- 03
Test the trigger
Run the test: Zapier brings back the three most recent items from your account. Pick a real one, so the next steps are mapped on true data.
- 04
Add the filter
Add a Filter step from the plus icon, then keep only runs where the action equals Approve. This makes the Zap multi-step, so a paid plan is needed.
- 05
Add the action and map it
Add KiSSFLOW with
Submit a New Request, pick the target process and set Initiator Email Id. Map the fields from the trigger, then test this step once. - 06
Publish
Click Publish to switch the Zap on. From now on, only approvals made after this moment will start it, never an older one.
The KiSSFLOW trigger
1 event starts a Zap when something happens in KiSSFLOW, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Change of Workflow Step
Instant triggerIn Zapier“Triggers when a request in a particular workflow process moves from one step to another step. The action performed to initiate this move like Approve or Reject will be provided as an additional input to the trigger.”
This starts your Zap every time a request in the process you chose moves from one step to another. Along with the request, Zapier receives the action that caused the move, so a later step can tell an approval from a rejection.
The 3 KiSSFLOW actions
KiSSFLOW gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Approve a Request
ActionIn Zapier“Approve a request to move it to its next step in the workflow process.”
Pushes an existing request to its next step, as if the named approver had clicked approve inside KiSSFLOW.
Submit a New Request
ActionIn Zapier“Initiates a new request for a chosen process , populates requisite fields and then submits the request for processing.”
Opens a request in the process you pick, fills its fields from earlier steps and sends it straight into the workflow.
Create a Draft Request
ActionIn Zapier“Creates a new request for a chosen process , populates requisite fields and saves it in the 'Draft' folder of KiSSFLOW.”
Builds a request with its fields filled in, then leaves it in the Draft folder of KiSSFLOW instead of submitting it.
When a KiSSFLOW Zap breaks
Zapier attaches no help article to KiSSFLOW, and no app-specific rate limit is documented. What breaks is what breaks on any Zap.
Four cases come up most. Each one is quiet: the Zap does not crash loudly, it just does something other than you expected. If a Zap misbehaves anyway, see our Zapier troubleshooting page.
Old requests are never picked up
A Zap only reacts to step changes made after it is switched on. Requests that moved last week stay where they are; moving that backlog is a separate job.The Zap that sets itself off
Submit a request into the same process your trigger watches, and each new step change can start the Zap again. It loops and burns through your task count fast.A bulk import that gets held back
After a migration or a mass update in KiSSFLOW, a sudden flood of step changes can be held back by Zapier's flood protection instead of running one by one.Rejections that start the Zap too
The trigger fires on any move, approval or rejection. Without a filter on the action, a rejected request can open a follow-up request it should not.
Need help automating KiSSFLOW with Zapier?
A person reads every message.
