Resources · Zapier integration

Krozu Zapier integrationAutomate Krozu with Zapier.

The Krozu Zapier integration exposes 15 triggers, 46 actions and 1 search, enough to run boards, lists, cards and checklists from the other tools your team already uses. Here is what each one does, what it costs and what tends to break.

See the 62 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Krozu Zapier integration is for

Krozu organises work as a hierarchy of groups, boards, lists and cards, with checklists, dates and team messaging on top. Zapier connects it to your other apps without code: an event in one tool, a follow-up done for you in another. With Krozu, almost every object on a board can be watched, created, moved, dated or archived from outside.

Three results come up first. Intake that lands on the right board: an item arrives in another app, and Create New Card files it in the intake list of the right board. Stages that trigger the next job: New Card Created or Moved Into List notices a card reaching a given list, and the next step runs in another tool. Projects that stay dated: Board Due Date, Card Due Date and the estimated-hours actions keep Krozu in step with deadlines and budgets agreed elsewhere.

Know the limits before building. All fifteen triggers are polling, so nothing reacts the instant it happens: Zapier checks on a timer set by your plan. Several triggers follow one board, one list, one card or one checklist, so a large workspace can need many Zaps. There is a single search, and no find-or-create, so a Zap cannot create a missing board on the fly. Dates are expected in UTC, which catches out anyone outside that time zone.

See also our n8n vs Zapier and Make vs Zapier pages.

Vocabulary

Zapier words, explained once

The same seven terms run through the whole page. Here they are in everyday language.

Zap
An automation on Zapier: a trigger, then one or more actions that run each time the trigger event takes place.
Trigger
The event that starts the Zap, such as a card reaching a list. Once the Zap is on, Zapier waits for exactly that.
Action
The work the Zap does after starting: creating, moving, dating or archiving something in an app for you.
Task
What Zapier bills: one action your Zap completes successfully. The monthly allowance of your plan counts these.
Polling vs instant
Polling means Zapier checks the app on a timer. Instant means the app tells Zapier the moment the event happens.
Filter
A step that lets the Zap go on only when the data meets your condition, and quietly stops it the rest of the time.
Search step
A step that finds something already in an app, such as a board, so later steps can use it without you picking it by hand.
Cost

What a Krozu Zap costs

Krozu is not a premium app, so the free Zapier plan is enough to start. What you pay for is completed actions.

  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo
  • Krozu triggers15, all polling
  • BilledEach successful action

Triggers are free, and so are the checks Zapier makes to spot new Krozu items, however often they run. Every action that succeeds counts as one task, and a failed action is not counted. A Zap that creates a card, sets a due date and assigns someone uses three tasks per run. The free plan includes 100 tasks a month and unlimited Zaps, but only two steps per Zap. A filter, the search or a second action makes it a multi-step Zap that needs a paid plan.

Connect

Connect Krozu to Zapier

  1. 01

    Go to Apps

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Krozu account linked once, then reused by every Krozu step in every Zap you build.

  2. 02

    Find Krozu

    Type Krozu in the dialog, select it, then click Add connection. Zapier opens a new tab on the Krozu side. You need a Krozu account already in place before you start.

  3. 03

    Sign in and allow access

    Log in to Krozu in that tab and grant Zapier access. Boards you do not own must be shared with this account with the rights your Zaps need, read for triggers and write for actions.

First Zap

Build your first Krozu Zap

GoalComment on every card that reaches a chosen list and passes your filter.

  1. 01

    Start with the trigger

    Create a Zap, pick Krozu and the event New Card Created or Moved Into List, then choose the Krozu connection you created earlier.

  2. 02

    Choose the list

    Select the list to watch; it is required. Test the trigger: Zapier brings back the three most recent cards from that list so you map fields from a real one.

  3. 03

    Add a filter

    Click the plus icon and add Filter. Set the field to look at, the rule and the value to compare with. A text rule only works on text values.

  4. 04

    Add the comment

    Add a Krozu step with Add Comment, map the card from the trigger and write the comment text. Both the card and the comment are required.

  5. 05

    Test and publish

    Run the test, check the comment in Krozu, then click Publish. With its filter this is a multi-step Zap, so it needs a paid plan to run.

Triggers

Krozu triggers on Zapier

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

1

Board Changed

Polling trigger

In Zapier“Triggers when any change on a Board happens.”

Watches one Krozu board as a whole and starts the Zap whenever something on it changes. It is the broadest net in the list, useful when you care that a project moved at all, not about which card moved.

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
keeping a line in another tool each time an important board is touched, whatever changed on it.
Watch out
you must pick the board to watch, and on a busy board this trigger fires often, so pair it with a filter.
2

Card Changed

Polling trigger

In Zapier“Triggers when a Card changes.”

Keeps an eye on a single card and reacts when it is edited. Think of it as a tripwire on one deliverable that matters more than the rest.

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
copying the state of one key card into another tool that people outside Krozu read.
Watch out
it follows one chosen card only; a new card elsewhere on the board will not start it.
3

List Changed

Polling trigger

In Zapier“Triggers when a List has changed.”

Reacts when a list you select has changed, which in Krozu usually means cards arriving, leaving or being reordered in that column of work.

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
a list where any movement should alert someone who works in another tool.
Watch out
the list is required and the trigger does not say which card caused the change; add a search or a filter if you need that detail.
4

New Accessible Board

Polling trigger

In Zapier“Triggers when a new Board is now accessible by you within your account.”

Fires when a board becomes reachable from your own Krozu account, whether someone created it or just shared it with you. No board needs to be picked.

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
keeping a record, in another tool, of every board you are given access to.
Watch out
it follows what the connected user can see, so connect the account whose view actually matters.
5

New List Created in a Board

Polling trigger

In Zapier“Triggers when a new List is created within the specified Board.”

Starts the Zap as soon as a new list appears inside the board you choose. Lists are the columns of a Krozu board, so this catches a new stage or phase being added.

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
creating a matching entry in another tool each time a board gains a new phase.
Watch out
you have to select the board to monitor before the test returns anything.
6

New Board Member

Polling trigger

In Zapier“Triggers when a new Board Member is Added.”

Picks up each person added to a chosen board. It turns "someone joined the project" into a signal your other tools can act on.

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
giving each new board member what they need in your other tools at the same moment.
Watch out
one board per Zap: the board field is required, so a team with many boards needs several Zaps.
7

New Board Message Added

Polling trigger

In Zapier“Triggers when a New Board Message is Added.”

Catches every new message posted in the messaging area of a selected board, with its text, so conversations do not stay trapped inside Krozu.

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
copying a board's messages into another tool where they must also be kept.
Watch out
if the same Zap writes back with Add Message on that board, it sets itself off in a loop.
8

New Card Comment Added

Polling trigger

In Zapier“Triggers when a new Card Comment is created.”

Runs each time a comment is written on the card you picked. Handy when one card carries the discussion that other people outside Krozu must follow.

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
forwarding the comments of one card to someone who follows it from another app.
Watch out
it watches one card, not the whole board; pairing it with Add Comment on that same card creates a loop.
9

New Card Created in Board

Polling trigger

In Zapier“Triggers when a new card is created within a specified board.”

Kicks in when a card is created anywhere inside a given board. It is the closest thing to a "new task" trigger for a whole Krozu project.

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
pushing each new card of a board into another tool your team already works in.
Watch out
the board is asked for by its UUID, so select it from the dropdown rather than typing a name.
10

New Card Tag Created

Polling trigger

In Zapier“Triggers when a new Tag has been added to a Card.”

Notices when a tag is added to the card you chose. A tag is a cheap way for people to flag something without leaving Krozu.

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
a tag on a sensitive card that should alert someone in another app.
Watch out
you pick one card to monitor, so this suits a handful of sensitive cards, not a full board.
11

New Checklist Added to a Card

Polling trigger

In Zapier“Triggers when a new Checklist is Created within a Card.”

Starts when a checklist is created inside a selected card. It tells other tools that a piece of work has just been broken into steps.

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
logging in another tool each checklist opened on a card you follow closely.
Watch out
the card is mandatory; checklists on other cards stay invisible to this Zap.
12

New Checklist Item Added to a Checklist

Polling trigger

In Zapier“Triggers when a new Checklist Item is Added to an existing Checklist.”

Goes one level deeper than the previous trigger: it reacts to each new line added to a checklist you choose.

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
a shared checklist whose new items should also land in a personal task tool.
Watch out
you select the checklist itself, so the card holding it must already exist and contain that checklist.
13

New Invites

Polling trigger

In Zapier“Triggers when you receive a new Invite.”

Fires when your connected Krozu account receives a new invite. Nothing to configure: it simply watches your own invitations.

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
being alerted in the tool you check most when you are invited to a new project.
Watch out
it only covers invites sent to the connected account, not invites you send to others.
14

New Card Created or Moved Into List

Polling trigger

In Zapier“Triggers when a new Card is created within or moved into the specified List.”

Springs into action when a card shows up in a chosen list, whether someone created it there or dragged it in from another column. That makes it the go-to trigger for "card reached stage X".

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
starting the next job in another tool when a card reaches a given list.
Watch out
the list is required, so one Zap watches one list; a pipeline with several stages needs one Zap per list you care about.
15

New Notifications

Polling trigger

In Zapier“Triggers when you receive a new Notification.”

Collects every notification that Krozu sends to the connected account, so you can route those alerts wherever you actually read them.

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
gathering your Krozu notifications in the same place as the alerts of your other tools.
Watch out
it is tied to the connected user; colleagues need their own connection to route their notifications.
Actions

Krozu actions on Zapier

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

1

Add Checklist

Action

In Zapier“Create a Checklist”

Creates a named checklist inside an existing card, so a recurring set of checks gets attached without manual work.

When to use it
giving every new card of a given kind the same checklist.
Watch out
needs both the card and the checklist name.
2

Create a Checklist Item

Action

In Zapier“Creates a Checklist Item”

Appends one line to a checklist that already exists on a card. The checklist grows step by step as events happen elsewhere.

When to use it
adding a step to an existing checklist each time a related event happens elsewhere.
Watch out
pick the checklist and give the item a name; both fields are mandatory.
3

Add Comment

Action

In Zapier“Add a Comment to Card”

Writes a comment on a chosen card, which keeps outside updates visible where the team works.

When to use it
writing on the right card an update that happened in another app.
Watch out
combined with New Card Comment Added on the same card, it loops.
4

Create a List

Action

In Zapier“Creates a new List”

Opens a new list, in other words a new column, on a chosen board.

When to use it
adding a phase column to a board when an event elsewhere calls for a new stage.
Watch out
the board and the list name are both required.
5

Add Message

Action

In Zapier“Add a new Message”

Posts a message into the messaging area of a board, the place where the whole project team reads updates.

When to use it
telling everyone on a board about an event that happened in another tool.
Watch out
the board and the message text are required.
6

Adjust List Weighting

Action

In Zapier“Manually adjusts a Lists weighting. Manual List Weighting must be enabled.”

Sets the low and high share any card in a list may add to the board progress.

When to use it
giving one list more weight in the board progress than another.
Watch out
manual list weighting must already be enabled on that list.
7

Archive Board

Action

In Zapier“Archives a Board”

Sends a whole board to the archive, out of daily view. It is the gentle way to close a project: the board is not deleted, and Unarchive Board can bring it back later.

When to use it
archiving a board when the matching project closes in another tool.
Watch out
the board field is required.
8

Archive Card

Action

In Zapier“Archives a Card”

Archives a single card. The card leaves the board but keeps all its history. Restoring it later is one action away.

When to use it
clearing finished cards from the board once the follow-up is done elsewhere.
Watch out
archived is not deleted; use Unarchive Card to bring it back.
9

Archive List

Action

In Zapier“Archives a List”

Archives a full list with its column. The cards inside go with it, still intact, and the board looks cleaner for everyone who opens it.

When to use it
hiding a finished phase of a board.
Watch out
only the list is required.
10

Add Board Member

Action

In Zapier“Assigns someone to a Board”

Gives someone a role on a board using their email address.

When to use it
adding a person to the right board when they are added somewhere else.
Watch out
board, email address and role are all required, so decide the role in advance.
11

Add Card Assignee

Action

In Zapier“Assign someone to a Card”

Makes a person responsible for a card, identified by email. The card then shows up in that person's own Krozu view.

When to use it
handing a new card to the person picked by a rule in another tool.
Watch out
the email must belong to a member, and the card field is required.
12

Board Due Date

Action

In Zapier“Sets the Due Date for a Board”

Fixes the due date of a board, the deadline the project is measured against. It is the date that the notify-hours action counts back from, so set it before any reminder.

When to use it
syncing a deadline agreed in another tool with the board.
Watch out
the date is expected in UTC, not your local clock.
13

Board End Date

Action

In Zapier“Sets the End Date for a Board”

Records the date a board actually finishes, distinct from the due date. Keeping it separate lets you compare planned and real finish dates later.

When to use it
recording when a board really ended, from an event in another app.
Watch out
use UTC for the date, like the other date actions.
14

Board Estimated Hours

Action

In Zapier“Sets the estimated hours for completion of a Board”

Writes the number of hours a board is expected to take. It gives the project a budget in time that progress can be read against.

When to use it
copying the hours planned in another tool into the board.
Watch out
decimals are allowed; the board and the hours are required.
15

Board Due Date Notify Hours

Action

In Zapier“Set hours previous to the due date of this Board to the project manager of this board. Decimals are allowed.”

Tells Krozu how many hours before the board due date to warn its project manager.

When to use it
setting the same early warning on every new board.
Watch out
it only helps if the board has a due date.
16

Board Start Date

Action

In Zapier“Sets the Start Date for a Board”

Sets when a board begins. It anchors the project timeline that the other date actions build on, so it is usually the first date a Zap writes.

When to use it
stamping the start date of a board from a date held in another app.
Watch out
the date must be in UTC of your local time, in the format shown in the field help.
17

Card Due Date

Action

In Zapier“Sets the Due Date for a Card”

Sets the deadline of a card. It is the deadline the assignee sees, and the date reminders count back from.

When to use it
giving each new card a due date taken from another tool.
Watch out
enter it in UTC, and set it before any notify hours.
18

Card Due Date Notify Hours

Action

In Zapier“Sets the number of hours before a Due Date for this card to send a notification to the assignee”

Decides how many hours before its due date the assignee of a card is notified. It is a reminder setting, not a message: Krozu sends the alert itself.

When to use it
reminding assignees ahead of deadlines without setting it by hand on each card.
Watch out
the card needs a due date first, or the notification never fires.
19

Card End Date

Action

In Zapier“Sets the End Date for a Card”

Stores the date a card was actually finished. It keeps the real finish apart from the planned one, which is what makes delivery reports honest.

When to use it
recording finish dates for later reporting.
Watch out
UTC format again, as in the field example.
20

Card Progress

Action

In Zapier“Sets Card Progress”

Updates how far along a card is. It is the figure people glance at on the board to see where a card stands, so keeping it fed from the real source saves questions.

When to use it
reflecting progress recorded in another tool.
Watch out
the card and the new progress value are both mandatory.
21

Card Start Date

Action

In Zapier“Sets the Start Date for a Card”

Marks when work on a card starts. It places the card on the timeline, which helps when cards are created long before the work begins.

When to use it
placing cards created from another app on the right start date.
Watch out
dates go in as UTC of local time.
22

Check a Checklist Item

Action

In Zapier“Puts a checkmark in this Checklist Item”

Ticks an item on a checklist for you. The step then shows as done for everyone on the card, with no one having to open Krozu to tick it.

When to use it
ticking a step as soon as the matching event happens in another app.
Watch out
pick the exact checklist item; it is required.
23

Create New Card

Action

In Zapier“Create a new card in the board and list provided”

Adds a card to the board and list you point it at, using a name mapped from the trigger. It is the workhorse action of most Krozu Zaps.

When to use it
turning each new item in another app into a card in the right list.
Watch out
board, list and card name are required, and board and list are picked by their internal IDs.
24

Delete a Card

Action

In Zapier“Delete a card (confirmation required)”

Removes a card for good, not to the archive. Unlike archiving, there is no way back from it.

When to use it
removing duplicate cards created by mistake.
Watch out
Krozu asks for confirmation: you must type 1 in the dedicated field.
25

Delete Checklist

Action

In Zapier“Deletes a Checklist”

Erases a checklist and its items. Every item inside goes with it, ticked or not, and the card simply no longer shows that checklist.

When to use it
removing a checklist that no longer applies.
Watch out
enter 1 in the confirmation field or nothing happens.
26

Delete Checklist Item

Action

In Zapier“Deletes a Checklist Item”

Removes one line from a checklist. The rest of the checklist stays as it was, so it suits precise clean-ups.

When to use it
dropping a step that was cancelled elsewhere.
Watch out
it also requires 1 in its confirmation field.
27

Delete List

Action

In Zapier“Deletes an existing List”

Deletes an existing list. It is final, unlike Archive List. Choose it only when you are sure.

When to use it
removing an empty column after a board is restructured.
Watch out
deletion needs 1 in the confirmation field; archive instead if in doubt.
28

Card Estimated Hours

Action

In Zapier“Set the estimated hours for a Card”

Puts an estimate, in hours, on a single card. Card estimates roll up into the picture you get of the whole board.

When to use it
copying estimates held in another tool onto each card.
Watch out
decimals are allowed; both fields are required.
29

Limit Cards in List

Action

In Zapier“Limits the number of Cards that can be contained in this List”

Caps how many cards a list may hold, a classic way to stop a column from overflowing. Once the cap is reached, the list stops taking new cards.

When to use it
capping how much work can sit in one list at a time.
Watch out
a value of 0 means unlimited.
30

Move Card

Action

In Zapier“Moves a Card from its original position”

Shifts a card from one list to another, at the position you set, which is how a Zap advances work through your stages.

When to use it
moving a card to the next list when the matching step is done elsewhere.
Watch out
board, source list, card, target list and position are all required.
31

Recurse a Card/Board

Action

In Zapier“Recurse a Card into a Board or Board into a Card”

Turns a card into a board of its own, or folds a board back into a card. This is the hierarchical side of Krozu.

When to use it
promoting a card that grew into a full project.
Watch out
leave the recurse value empty and it simply toggles, which can surprise you on a second run.
32

Rename Board

Action

In Zapier“Renames a Board”

Gives a board a new name. Members, lists and cards stay exactly where they were, only the label at the top changes, which is what you want for references.

When to use it
adding a reference from another tool to a board name.
Watch out
the new name replaces the old one completely.
33

Rename Card

Action

In Zapier“Renames an existing Card”

Changes the title of a card. The card keeps its comments, dates and assignee, so this is a safe way to surface a state in the title.

When to use it
putting a state set in another tool into a card's title.
Watch out
both the card and the new name are required.
34

Rename Checklist

Action

In Zapier“Renames a Checklist”

Changes the name of an existing checklist. The items inside stay untouched, so ticks and order survive the rename.

When to use it
marking in its title that a checklist is finished.
Watch out
checklist and new name are both required.
35

Rename Checklist Item

Action

In Zapier“Renames a Checklist Item”

Rewrites the label of one checklist item. Whether the item is ticked or not does not change.

When to use it
adding to a step a reference that only becomes known later.
Watch out
both the item and its new name are required.
36

Rename Group

Action

In Zapier“Renames a Group”

Gives a Krozu group a new name. Groups sit above boards in the Krozu hierarchy, so a rename here shows across everything filed under that group.

When to use it
keeping group names in step with names used in another tool.
Watch out
you must choose the group and type the new name.
37

Rename List

Action

In Zapier“Renames an existing List”

Renames one list on a board. Cards stay in place, only the column header changes, so nobody loses track of their work.

When to use it
keeping list names in step with stages renamed in another tool.
Watch out
list and new name are mandatory.
38

Toggle List Testers

Action

In Zapier“Toggles the ability for Testers to add Cards to this List”

Turns on or off the ability for testers to add cards to a list. Testers are a role in Krozu with narrower rights.

When to use it
letting testers add cards to a list only for a set period.
Watch out
a toggle again, so check the current state first.
39

Toggle List Time Tracking

Action

In Zapier“Toggles the ability for Cards placed in this List to track time.”

Flips time tracking on or off for cards placed in a list. Time tracking lets cards in that list log the time spent on them, card by card.

When to use it
turning time tracking on only for the lists where time must be logged.
Watch out
running it twice cancels itself out.
40

Toggle List Weighting

Action

In Zapier“Toggles Smart Progress or Manual List Weighting”

Switches a list between Smart Progress and manual weighting. Weighting decides how much each list counts in the board progress.

When to use it
turning manual weighting on before adjusting it in the next step.
Watch out
it is a toggle: running it twice puts you back where you started.
41

Unarchive Board

Action

In Zapier“Unarchives a Board”

Brings an archived board back into view. It is the reverse of Archive Board, so a project closed a little too early is never lost for good.

When to use it
reopening an archived board when its project starts again.
Watch out
the board must be chosen.
42

Unarchive Card

Action

In Zapier“Unarchives a Card”

Brings back a card that was archived, the reverse of Archive Card. The card returns to view so the work on it can pick up again.

When to use it
bringing back an archived card when its topic comes back to life.
Watch out
pick the card; it is required.
43

Unarchive List

Action

In Zapier“Unarchives a List”

Puts an archived list back on its board, the reverse of Archive List, so a phase hidden too early becomes visible again.

When to use it
restoring a phase that was archived too early.
Watch out
the list field is required.
44

Remove Board Member

Action

In Zapier“Removes a Member from a Board”

Takes a member off a board for a given role, the mirror of Add Board Member.

When to use it
removing a member from a board when they leave the project in another tool.
Watch out
you must give the board, the email and the role to remove.
45

Remove Card Assignee

Action

In Zapier“Removes the Assignee from the Card”

Clears a named assignee from a card. Nothing else on the card changes, only the name of the person in charge, so comments and dates stay as they were.

When to use it
freeing a card when its owner changes in another tool.
Watch out
the card and the assignee email are required.
46

Uncheck Checklist Item

Action

In Zapier“Removes the checkmark from a Checklist Item”

Removes the tick from a checklist item, reopening that step. It is the undo of the previous action, useful when an outside event cancels a step that was marked as done.

When to use it
reopening a step when an event elsewhere cancels it.
Watch out
the item field is required.
Searches

The Krozu search on Zapier

1 search step looks for data that already exists in Krozu, so a later step can use it.

A search step finds something that already exists in Krozu and passes it on. It sits at the bottom of the Action event list, under SEARCH, and makes the Zap multi-step. Krozu offers no find-or-create, so the search never creates what it misses.

1

Find User Accessible Boards

Search

In Zapier“Provides a list of all User Accessible Boards”

Looks up the boards the connected user can reach and hands one to the following steps.

When to use it
finding the right board before creating a card on it.
Watch out
the board field is required, and the result depends on what the connected account can see.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on default, an empty search stops the Zap and skips the steps that relied on it. Turned on, the Zap carries on with nothing.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Krozu does not offer it, so it will not appear here.
  3. If multiple search results are found?
    Three choices when several boards match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When a Krozu Zap breaks

Zapier lists no help article for Krozu, so these are the general limits that bite Krozu Zaps hardest.

Broken Krozu Zaps mostly come from the way Zapier works rather than from Krozu: the wait between checks, the missing history, loops between a trigger and an action on the same card or board. See also our Zapier troubleshooting page.

  • Existing cards are ignored

    A Zap only reacts to what happens after it is switched on. Cards, lists and messages already in Krozu are not picked up; moving that backlog is a separate job.

  • A Zap that keeps firing itself

    Adding a comment to the card a comment trigger watches, or a message to the board a message trigger watches, restarts the Zap in a loop and burns tasks.

  • Big imports get held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection may hold it back instead of running everything.

  • Changes show up late

    Every Krozu trigger is polling. On the free plan Zapier checks every 15 minutes, so a moved card can wait that long before anything happens.
Need help

Need help automating Krozu with Zapier?

A person reads every message.

FAQ

Krozu Zapier integration: FAQ

01Is the Krozu Zapier integration free?
Yes, on the Zapier side. Krozu is not a premium app, so the free Zapier plan can run it. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. Add a filter, the search or a second action and the Zap becomes multi-step, which requires a paid plan. Your Krozu subscription is separate, and this page says nothing about its pricing.
02How many tasks does a Krozu Zap use?
One task for each action that succeeds, and none for the trigger. Zapier does not charge for the checks it runs to spot new Krozu cards or changes, however frequent. A Zap that creates a card uses one task per run; one that creates a card, sets its due date and assigns it uses three. A failed action is not counted. A few apps take more than one task per action, so check the step if the count surprises you.
03Does Krozu trigger Zaps in real time?
No. All fifteen Krozu triggers are polling triggers: Zapier asks Krozu for new items at a fixed interval and keeps only what it has not seen yet. That interval is 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise. Krozu itself sets this type, and it cannot be switched in the editor. On paid plans you can also run a check by hand while testing a Zap.
04What does it take to connect Krozu to Zapier?
A Krozu account, plus access to the boards your Zaps will read or write if you do not own them. You add the connection once from the Apps page with + Add connection, search Krozu, sign in in the tab that opens and grant access. Since nearly every step asks for a board, list, card or checklist, the connected account must be able to see those objects, or the dropdowns stay empty.
05Why do Krozu dates land at the wrong hour?
Because the date fields of Krozu actions expect UTC, not your local clock. Board Start Date, Board Due Date, Card Due Date and the other date actions all say so in their field help, with an example in year-month-day and hour format. If your source gives local times, convert them before the Krozu step, or every deadline shifts by your offset from UTC. Check one test card before publishing, and keep the conversion in a single place.
06What if the Krozu operation you want is missing on Zapier?
Then this integration cannot do it directly, and it is worth knowing before you build. First see whether two existing operations get you there, such as Find User Accessible Boards followed by Create New Card. Otherwise, check whether Make or n8n expose other Krozu modules, and compare. Before you build, list the steps your idea needs, because a search step or a second action makes the Zap multi-step, which needs a paid plan.
07Zapier, Make or n8n for Krozu?
It comes down to your criteria, not to a winner. Zapier is the fastest to start and Krozu runs on its free plan, but billing is per successful action and the free plan stops at two steps. Make suits visual scenarios with branches. n8n suits teams that want to self-host and keep volume costs under control. Compare the Krozu operations each tool exposes, your expected monthly volume and who will maintain the automations.
Same platform

Other docs you might need on this stack.

Browse all integrations