Resources · Zapier integration

Kitemaker Zapier integrationAutomate Kitemaker with Zapier.

The Kitemaker Zapier integration gives you 4 triggers and 6 actions, with no search step. All four triggers are instant, so a new work item, comment or initiative reaches your other tools without waiting for a check, even on the free plan.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Kitemaker Zapier integration actually does for your product team

Zapier links Kitemaker to the rest of your tools without code. Something happens in Kitemaker (a work item is created, a comment lands, an initiative appears) and Zapier passes it on. Or the reverse: something happens elsewhere and Zapier writes a work item, a comment, a label or a piece of feedback into Kitemaker for you.

Three results you can expect once it runs. Customer requests that land in the backlog by themselves: a support form or a CRM note becomes an entry through Create Feedback, so nobody retypes what a customer asked for. A team that hears about work as it moves: Updated Work Item can post a line in your chat tool each time a ticket changes, and New Comment can copy a discussion to the person who owns the customer account. Planning that starts from a decision, not from a meeting note: Create Initiative opens an initiative when a deal is signed or a roadmap row is approved somewhere else.

Now the limits. There is no search step for Kitemaker on Zapier, so a Zap cannot look up an existing work item by its title. Every action that touches an existing item (Create Comment, Update Work Item) needs its Work Item ID handed over by an earlier step, usually the trigger itself. Create Work Item also wants a Space ID and a Status ID, which you look up once in Kitemaker and paste in. And a Zap never reaches back into history: items created before you switch it on stay where they are.

If you prefer to self-host your automations, the Kitemaker n8n integration covers the same app from the other side. For a wider view of the two tools, read n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Seven words and you can read any Zapier screen. Each one is used with this meaning for the rest of the page.

Zap
The automation you build: 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 simply waits for it to happen.
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 task is one action that your Zap finished successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is pushed by the app the second the event happens. Kitemaker only has instant ones.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your Kitemaker account linked to Zapier once, then reused by every step of every Zap that talks to Kitemaker.
Cost

What a Kitemaker Zap costs in tasks

The trigger never costs a task. Zapier bills only actions that went through, and an action that fails is not counted.

  • Trigger0 task
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A Zap with one Kitemaker trigger and one action costs one task per run. Add a second action and each run costs two, because every successful action counts on its own. The free plan gives you 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. A filter, a second action or a search turns the Zap into a multi-step Zap, which needs a paid plan. Kitemaker is not a premium app, so it works on the free plan. The polling grid below does not apply here: all Kitemaker triggers are instant.

Connect

Connect Kitemaker to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You only need a Kitemaker account, plus access to the spaces you want the Zap to write into.

  2. 02

    Pick Kitemaker

    Type Kitemaker in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Kitemaker side, where the actual sign-in happens.

  3. 03

    Sign in and allow access

    Log in to Kitemaker in that tab and grant Zapier access to the account. The connection now shows in your list, and every Kitemaker step of every Zap can reuse it.

First Zap

Your first Zap: tell the owner when a ticket moves

GoalEach time a Kitemaker work item is updated, check that it concerns a customer, then email the account owner.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Kitemaker as the app and Updated Work Item as the event. Select the connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so pick a real work item to map fields from.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, the rule and the value. A text rule only works on text. This step makes it a multi-step Zap, so a paid plan.

  4. 04

    Add the email action

    Add Gmail with Send Email, and drop the work item title into the message body, picking it from the data the trigger brought back during the test.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the email lands as expected, click Publish to switch the Zap on for every future update.

Triggers

Kitemaker triggers

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

1

New Comment

Instant trigger

In Zapier“Triggers when a new comment is added to a work item.”

Starts the Zap when a comment is added to a work item in Kitemaker. Use it to carry a discussion out of Kitemaker to people who never open it.

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 customer success manager wants to see every discussion on the tickets their accounts raised, without opening Kitemaker all day.
Watch out
if the same Zap writes comments back into Kitemaker with Create Comment, it sets itself off again and again, so add a filter or send the comment elsewhere.
2

New Initiative

Instant trigger

In Zapier“Triggers when an Initiative is created.”

Fires whenever someone creates an initiative in Kitemaker. Pick it when the people who need to know follow plans and goals, not individual tickets.

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 product lead adds a row to a planning spreadsheet or a slide in the roadmap review each time the team opens a new initiative.
Watch out
only initiatives created after the Zap is published come through; the ones already in Kitemaker are never sent.
3

New Work Item

Instant trigger

In Zapier“Triggers when a new Work Item is created.”

Reacts to every work item created in Kitemaker. Choose it when people outside the product team need to hear about new work without logging in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post each new item in a Slack channel so support and sales see what engineering just picked up.
Watch out
a bulk import into Kitemaker sends a large batch at once, and Zapier's flood protection can hold it back.
4

Updated Work Item

Instant trigger

In Zapier“Triggers when a Work Item is updated.”

Runs each time an existing work item is updated. On a busy board that means many runs, so keep the action behind it light.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a status column in your CRM in line with the ticket a customer is waiting on.
Watch out
pair it with Update Work Item on the same item and you build a loop that burns tasks; put a filter between the two, which means a paid plan.
Actions

Kitemaker actions

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

1

Create Comment

Action

In Zapier“Creates a comment on a work item”

Adds a comment to an existing work item. The body accepts Markdown, so links and bold text survive the trip.

When to use it
paste a customer's reply from your helpdesk under the ticket it concerns.
Watch out
it needs the Work Item ID, and without a search step that ID has to come from an earlier step.
2

Create Feedback

Action

In Zapier“Creates Feedback”

Files a new piece of feedback in Kitemaker with just a title required. It is the lightest way to get customer voice into the tool.

When to use it
every answer to a "what is missing?" survey question becomes a feedback entry the product team can sort later.
3

Create Initiative

Action

In Zapier“Creates a new Initiative”

Opens a new initiative from a title. Good for turning a decision taken in another tool into a planning object.

When to use it
a deal marked won in your CRM with a custom build attached starts an initiative named after the client.
4

Create Work Item

Action

In Zapier“Creates a work item”

Creates a work item in a given space. It asks the most of the six actions: a title, a Space ID (the space key, such as ABC), a Status ID and a placement inside the status column.

When to use it
a bug form on your site files a ticket straight into the triage column.
Watch out
look up the space key and status ID in Kitemaker before you build.
5

Create Label

Action

In Zapier“Creates a label for the specified Space”

Adds a label to a space, given a label name and the Space ID. Labels created this way are then available to tag items in that space.

When to use it
each new client signed in your CRM gets its own label so tickets can be tagged by account.
6

Update Work Item

Action

In Zapier“Updates an existing Work item”

Changes an existing work item. Only the Work Item ID is required; the rest depends on what you want to change.

When to use it
a payment confirmed in your billing tool moves the matching ticket forward.
Watch out
paired with Updated Work Item on the same item, it loops.
When it breaks

When a Kitemaker Zap breaks

Zapier links no help article to Kitemaker and lists no app-specific limit, so the failures below are the general ones, applied to this app.

Most broken Kitemaker Zaps come from one of four causes. If yours is not here, the Zapier troubleshooting guide goes further.

  • Old items never show up

    A Zap only reacts to what happens after you publish it. Work items, comments and initiatives created before that are never sent; moving that backlog is a separate job.

  • The Zap keeps restarting itself

    Updated Work Item plus Update Work Item on the same item, or New Comment plus Create Comment, makes a loop that sets the Zap off again and again and eats your task count.

  • A bulk import goes quiet

    Importing many work items at once sends a large batch in one go. Zapier's flood protection can hold that batch back instead of running the Zap for each item.

  • Create Work Item fails on IDs

    Space ID, Status ID and placement are all required. A wrong space key or Status ID makes the action fail, and a failed action costs no task.
Need help

Need help automating Kitemaker with Zapier?

A person reads every message.

FAQ

Kitemaker Zapier integration: common questions

01Is the Kitemaker Zapier integration free?
Yes, as long as your Zap stays at two steps. Kitemaker is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the shape: the free plan only builds Zaps with one trigger and one action. As soon as you add a filter or a second action, for example to only forward customer tickets, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Kitemaker Zap use?
One per successful action, per run. The trigger costs nothing, whichever of the four you pick, and Zapier does not bill the time spent waiting for events. A Zap that creates a work item and then posts a comment uses two tasks each time it runs. An action that fails is not counted. Keep an eye on Updated Work Item, which fires on every edit and can multiply runs quickly on a busy board.
03Does Kitemaker send events to Zapier in real time?
Yes. All four Kitemaker triggers are instant: Kitemaker tells Zapier as soon as a comment, initiative or work item is created or updated, and the Zap starts right away. That holds whatever your plan, so the 15-minute polling interval of the free plan does not apply to this app. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is the quickest way to confirm what you picked. The trigger itself never costs a task.
04What is required to connect a Kitemaker account?
A Kitemaker account and write access to the spaces the Zap will touch. The connection itself is done once from the Apps page of Zapier: click + Add connection, pick Kitemaker, sign in in the tab that opens and grant access. Every Kitemaker step then reuses that connection. If the account cannot write in a given space, actions like Create Work Item or Create Label will fail there, so check space access in Kitemaker before building the Zap.
05Why can't Zapier find an existing Kitemaker work item?
Because the Kitemaker integration has no search step. Zapier cannot look up a work item by its title or any other value. Create Comment and Update Work Item both need the Work Item ID, so it must come from an earlier step, typically New Work Item, Updated Work Item or New Comment in the same Zap. If the item started its life outside that Zap, there is no built-in way to fetch its ID.
06What if the Kitemaker operation you need is not in Zapier?
Then the integration simply does not offer it. On Zapier, Kitemaker has four triggers and six actions, nothing to delete items and no search. Check first whether a combination does the job, for instance Update Work Item fed by a trigger in the same Zap. Otherwise the option is another automation tool that talks to Kitemaker differently, or a request to the Kitemaker team. A short note about the missing step and the result expected makes that request easier to act on.
07Zapier, Make or n8n for Kitemaker?
It depends on your criteria rather than on a winner. Zapier is the quickest to set up and runs Kitemaker on its free plan, with instant triggers, but every successful action counts against a monthly task quota and anything beyond two steps needs a paid plan. If you prefer hosting the automation yourself or need logic Zapier does not offer here, compare what each tool exposes for Kitemaker before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations