Resources · Make integration

KissFlow Make integrationAutomate KissFlow with Make.

Need KissFlow to move work forward without someone copying data by hand? The KissFlow Make integration gives you 23 modules: 2 triggers, 17 actions and 4 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the KissFlow integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the KissFlow Make integration do for you?

The KissFlow Make integration links your KissFlow account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule. Each module is one brick of that chain, such as a trigger that spots a change, an action that creates or updates an item, or a search that brings back a list.

Tell the team when a request moves. Watch Process Items notices new, updated or completed process items, and Create a Channel Post publishes a short update in the channel your colleagues already read. Nobody has to chase the status of an approval.

Open project work from an outside event. A form, a CRM deal or a spreadsheet row in another app can start the scenario, then Create a Project Item or Create a Case Item opens the matching record in KissFlow with the data already filled in.

Keep other tools in step with your channels. Watch Channel Announcements picks up announcements that were created or edited since its last check, so you can copy them into a chat tool or an intranet page without retyping them.

What Make does not give you here: KissFlow has no instant trigger in Make, so both triggers check on the scenario's schedule. Make's own documentation for KissFlow is also marked as limited, so expect to test each module with your own data. When a module is missing, Make an API Call reaches the rest of the KissFlow API. To learn the editor from the ground up, the Make training is a good start, and if you are weighing tools, n8n vs Make lays out the criteria side by side. When a run fails, Make troubleshooting covers the usual error messages.

Connect

How do you connect KissFlow to Make?

  1. 01

    Add a KissFlow module

    In a new scenario, click the +, search for KissFlow and pick any of its modules. In the module panel, click Create a connection. A connection is your KissFlow account linked to Make once, then reused by every KissFlow module.

  2. 02

    Name the connection

    Give it a name you will recognize later, for instance the KissFlow account or the team it belongs to. This step is optional, but it helps a lot once several people share the same Make organization.

  3. 03

    Authorize and save

    Follow what KissFlow asks for: either approve Make on the KissFlow page that opens, or paste the key your KissFlow account gives you. Then click Save and Make lists the KissFlow data it can now read.

First scenario

Your first scenario: post an update when a process item changes

GoalWhen a process item is created, updated or completed in KissFlow, Make publishes a post in a KissFlow channel.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to add your first module.

  2. 02

    Set the trigger

    Search for KissFlow, choose Watch Process Items, then pick your connection or create it. Fill in the fields; once connected, Make lists what it can read in your account.

  3. 03

    Add the channel post

    Click the + to the right of the trigger and add Create a Channel Post. Map the item data from the trigger into the post text so readers see which request moved.

  4. 04

    Test with Run once

    Click Run once, then change a process item in KissFlow. Open the bubbles above each module to read the bundles, one bundle per item that went through.

  5. 05

    Schedule and switch on

    On the first module, open the clock and keep the default of every 15 minutes or change it. Switch the scenario on, and it checks KissFlow at that rhythm from now on.

Triggers

What can start a KissFlow scenario?

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

KissFlow1Watch Channel Announcements

Watch Channel Announcements

Scheduled trigger

In Make“Triggers when a channel announcement is created or updated.”

This trigger hands your scenario every announcement that appears or gets edited in a KissFlow channel, so its text can travel to other tools without anyone retyping it.

How it fires
it is a scheduled trigger, which means Make checks the app on the scenario's schedule and collects what changed since the last check.
When to use it
your HR team posts policy news in a KissFlow channel and you want the same message mirrored in the company chat.
Watch out
edits count too, so a corrected typo can send the same announcement out again; add a filter if repeats bother your readers.
KissFlow2Watch Process Items

Watch Process Items

Scheduled trigger

In Make“Triggers when a process item is created, updated or completed.”

Each time Make checks, you get the process items that are new, updated or completed since the last check, which is the natural starting point for anything that should follow an approval flow.

How it fires
scheduled; Make checks the app on the scenario's schedule, every 15 minutes by default, and each item it finds becomes one bundle.
When to use it
a purchase request gets approved and the finance tool, a spreadsheet or the requester should hear about it.
Watch out
since updates also fire it, one item can pass through several times during its life; add a filter after it when only completed items matter.
Modules

What can each KissFlow module do?

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

KissFlow1

Add an Attachment to a Channel Post

Action

In Make“Adds a new attachment to a channel post.”

A file lands on an existing channel post, so the document sits right where people are already discussing it instead of in a separate folder.

When to use it
a signed contract arrives in a storage app and belongs under the announcement about that deal.
Watch out
the post must exist first, so place this module after Create a Channel Post or a search that returns the post; on the Free plan, files stay under 5 MB.
KissFlow2

Create a Case Item

Action

In Make“Creates a new case item.”

Opens a fresh case in KissFlow from data that arrived somewhere else, which saves your support or service team from typing the ticket by hand.

When to use it
a customer fills in a web form or sends an email, and that request should become a case your team can pick up and track.
Watch out
each run creates one case, so a scenario that fires twice on the same form leaves you with duplicates.
KissFlow3

Create a Channel Post

Action

In Make“Creates a channel post.”

Publishing into a KissFlow channel from your scenario means updates reach colleagues where they already look, with the details pulled from earlier modules.

When to use it
a deal closes in your CRM, a process item is completed or a milestone passes, and the whole channel should know.
Watch out
map only the fields readers need, because a post stuffed with raw data gets ignored fast.
KissFlow4

Create a Process Item

Action

In Make“Creates a process item.”

Starting a KissFlow process from another app turns an outside request into an item that follows your approval steps right away.

When to use it
an expense line lands in a spreadsheet, or a leave request comes in through a form, and it has to enter the official process.
Watch out
Make lists your processes once the connection works, so check you picked the right one before the first Run once.
KissFlow5

Create a Project Item

Action

In Make“Creates a new project item.”

New work shows up on a KissFlow project board without anyone adding the card, fed by whatever event starts your scenario.

When to use it
a client signs a quote in another tool and the delivery team needs a project item ready to plan.
Watch out
if the source can send the same event again, search first with List Project Items so you do not open the same piece of work twice.
KissFlow6

Delete a Case Item

Action

In Make“Deletes a case item.”

Removing a case from KissFlow keeps your case list clean when a request turns out to be spam, a test or a duplicate.

When to use it
a form sends junk that already became a case, and your scenario spots it by a rule you trust.
Watch out
a delete cannot be undone from Make, so run it only after a filter or a Get a Case Item check proves you have the right one.
KissFlow7

Delete a Channel Post

Action

In Make“Deletes a channel post.”

Taking a post off a KissFlow channel lets a scenario clean up messages that are outdated or were published by mistake.

When to use it
an event gets cancelled in your calendar tool and its announcement should disappear from the channel.
Watch out
nothing brings the post back afterwards; keep a copy elsewhere if the content still matters.
KissFlow8

Delete a Process Item

Action

In Make“Deletes a process item.”

Pulling an item out of a KissFlow process is useful when a request was withdrawn at the source and should not wait in anyone's queue.

When to use it
a requester cancels an order in your e-commerce tool, so the matching purchase request no longer makes sense.
Watch out
the removal is final, so test on a dummy item with Run once before letting the scenario touch real requests.
KissFlow9

Delete a Project Item

Action

In Make“Deletes a project item.”

Clearing a project item from KissFlow keeps your boards honest when the work behind it is dropped in another tool.

When to use it
a deal is marked lost in your CRM and the project item created for it should go.
Watch out
there is no recycle step inside Make, so if you might need the history, update it with Update a Project Item instead of deleting it.
KissFlow10

Get a Case Item

Action

In Make“Returns the data of specified case item.”

You get the full data of one case you already know, which lets later modules work with its current values rather than a stale copy.

When to use it
an email mentions a case and your scenario needs its latest status before replying or escalating.
Watch out
it reads a single case you point to; when you do not know which one, start with List Case Items instead.
KissFlow11

Get a Channel Post

Action

In Make“Retrieves a channel post.”

With this module a scenario reads one specific channel post, so its content can be reused, checked or forwarded to another app.

When to use it
a post needs to be copied into a newsletter draft or an intranet page after someone flags it.
Watch out
you need to know which post to fetch; List Channel Announcements is the way to find it when you only know the channel.
KissFlow12

Get a Process Item

Action

In Make“Retrieves a process item.”

One process item comes back with its current data, handy when a scenario must decide what happens next based on where the request stands.

When to use it
a finance tool asks whether a purchase request is approved before it releases a payment.
Watch out
it returns the item as it is at the moment of the run, so a change made after that shows up only on the next run.
KissFlow13

Get a Project Item

Action

In Make“Retrieves a project item.”

Fetching a single project item gives your scenario its latest details so other tools can report on it accurately.

When to use it
a client portal or a reporting sheet needs the current state of one project item when a customer asks about progress.
Watch out
like the other Get modules, it expects you to name the item; pair it with List Project Items when you start from a board.
KissFlow14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules covers what you need, this one sends your own request to the KissFlow API with the connection you already set up.

When to use it
you need a KissFlow feature that has no dedicated module here, and you know which endpoint handles it.
Watch out
you write the request yourself, so keep the KissFlow API documentation open and test with Run once before switching the scenario on.
KissFlow15

Update a Case Item

Action

In Make“Updates an existing case item.”

Changing an existing case from another app keeps KissFlow accurate without a person switching screens to type the same update.

When to use it
a reply from the customer comes in by email and the case should reflect what the customer just said.
Watch out
map only the fields you want to change; an empty value mapped by mistake can wipe what was there.
KissFlow16

Update a Process Item

Action

In Make“Updates an existing process item.”

Editing a process item from your scenario lets outside data complete or correct a request while it moves through its steps.

When to use it
a supplier sends a quote and its amount should be written onto the purchase request waiting for approval.
Watch out
if Watch Process Items starts the same scenario, your own update can fire it again; filter on a field that tells the two apart.
KissFlow17

Update a Project Item

Action

In Make“Updates an existing project item.”

Progress recorded elsewhere lands on the right project item, so the board shows reality without a manual refresh.

When to use it
a task is closed in a developer tool or a time tracker and the linked project item should show that progress.
Watch out
you need the item's identity first, usually from Create a Project Item earlier or from List Project Items.
KissFlow18

List Case Items

Search

In Make“Retrieves a list of case items.”

Pulling a list of cases gives your scenario zero, one or many bundles to sort, count or send to a report.

When to use it
a manager wants open cases copied into a spreadsheet the moment a review meeting is booked.
Watch out
each case becomes its own bundle and the next modules run once per bundle, which adds operations to your plan; add an aggregator when one summary is enough.
KissFlow19

List Channel Announcements

Search

In Make“Retrieves a list of the announcements in a channel.”

Every announcement of a channel comes back as a separate bundle, ready to be archived, filtered or pushed somewhere else.

When to use it
you are setting up an intranet page and want the existing announcements copied there once, before Watch Channel Announcements takes over.
Watch out
a busy channel returns many bundles, so a filter right after this module keeps the operation count down.
KissFlow20

List Process Items

Search

In Make“Retrieves a list of the process items.”

Searching through process items hands you the requests of a process as a stack of bundles, which is the base for any overview or follow-up.

When to use it
someone opens a report in another tool and it should show every purchase request still pending.
Watch out
unlike Watch Process Items, it does not remember what it already sent, so running it twice returns the same items twice.
KissFlow21

List Project Items

Search

In Make“Retrieves a list of project items.”

This search returns the project items of a board so you can check them, match them against another tool or avoid creating a duplicate.

When to use it
before Create a Project Item runs, you want to confirm that no item already exists for that client.
Watch out
the search can come back empty; plan a router or a filter for that case so the rest of the scenario still behaves.
Need help

Need help automating KissFlow with Make?

A person reads every message.

FAQ

Common questions about KissFlow and Make

01Is the KissFlow Make integration free?
Yes, KissFlow is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module run on each bundle. KissFlow's own subscription is separate and is not covered here.
02What does it take to connect KissFlow to Make?
A KissFlow account and a Make account are enough to start, since Make's documentation lists no special prerequisite for this app. You add any KissFlow module, click Create a connection, optionally give it a name, then either approve Make on the KissFlow page or paste the key KissFlow gives you, and save. The documentation for KissFlow is marked as limited, so there is no official step-by-step guide. If the connection fails, check the account you signed in with and retry from the module panel.
03Does the KissFlow trigger in Make react in real time?
No. Both KissFlow triggers in Make, Watch Channel Announcements and Watch Process Items, are scheduled triggers: Make checks KissFlow on the scenario's schedule instead of being called the moment something changes. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two runs; paid plans can go down to 1 minute. If a process needs a faster reaction, a paid plan with a shorter interval is the lever Make offers for this app.
04What if a KissFlow module is missing in Make?
Use Make an API Call. It is a KissFlow module that sends any request to the KissFlow API with the connection you already created, so you can reach features the 23 listed modules do not cover. You write the request yourself, which means reading the KissFlow API documentation for the right endpoint. Make's own guide for this app is marked as limited, so test each call with Run once and read the bundles it returns before switching the scenario on.
05Make or n8n for KissFlow automation?
It depends on the tool your team already knows. On the Make side, KissFlow offers 23 modules covering cases, processes, projects and channel posts, two scheduled triggers, and Make an API Call for everything else. The same app often has an n8n node as well, so check its page before deciding. Compare the modules each side offers for your exact flow, how you prefer to build, and how usage is counted, rather than picking on reputation. Test your real flow on one of them first.
Same platform

Other docs you might need on this stack.

Browse all integrations