Craft.io Zapier integrationAutomate Craft.io with Zapier.
The Craft.io Zapier integration gives you 6 operations: 3 triggers and 3 actions. Enough to turn customer feedback into backlog work, react to new OKRs and items, and create all three without leaving the tool your request came from, from the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Craft.io Zapier integration does for you
Craft.io is one shared place where product managers work together, feedback portals included. Through Zapier, it reports new feedback, new work items and new OKRs, and it can create each of those three things for you, so the product backlog stays fed without anyone copying requests across.
Feedback that turns into backlog work. New Feedback Created starts the Zap, a filter keeps the categories your team handles, and Create New Work Item drops them into a workspace the team already plans from.
Objectives broken down into work. New OKR Created fires on every new objective, and Create New Work Item opens the matching piece of work so the goal never sits alone.
Requests logged where they belong. Create New Feedback writes a request into the right feedback portal, and Create New OKR records an objective, from data an earlier step carried.
What Zapier does not do here: every trigger watches for something new, never for a change, there is no search to look up an existing item, and no action updates or deletes anything. If the job depends on an edit or a status change, these six operations will not see it.
Still weighing platforms? See our Make vs Zapier comparison, or our Zapier agency if you would rather hand the build over.
Zapier vocabulary in one minute
Seven or eight words carry the whole page. Read them once and the rest of the page reads like plain English.
- Zap
- The automation you build on Zapier: one trigger that starts it, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that sets the Zap off. Once the Zap is published, Zapier sits and waits for that event to come up.
- Action
- The step that does the work after the start: it creates, sends or writes something in an app on your behalf.
- Task
- Zapier's billing unit. One task is one action that completed successfully, and your plan is sized as a count of those.
- Polling vs instant
- Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier itself the moment something happens.
- Filter
- A step that lets the Zap carry on only when the incoming item meets a condition you set, and stops it otherwise.
- Connection
- Your Craft.io account linked to Zapier once, then reused by every step of every Zap that works with Craft.io.
What a Craft.io Zap really costs
Short version: the trigger is free, every successful action is billed, and the free plan stops at two steps.
- Triggernever billed
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps
- Premium appno
Zapier counts in tasks. Looking for new data never costs anything, and an action that fails is not billed. Each action that succeeds counts on its own, so a Zap with three actions uses three tasks per run. The free plan gives you 100 tasks a month and Zaps of exactly two steps. Add a second action, a filter or a search step and the Zap turns multi-step, which needs a paid plan. Craft.io is not a premium app: it works from the free plan. The plan also sets how often a polling trigger checks for new items, and that check is free.
Connect Craft.io to Zapier in three steps
- 01
Open Apps and start a connection
In your Zapier account, go to the Apps page and click + Add connection. Type Craft.io in the search box of the dialog and pick it from the list of results.
- 02
Sign in to Craft.io
Click Add connection. A new tab opens on the Craft.io side: log in with the account the Zap should work with. You need an account there, plus read or write access to anything you do not own yourself.
- 03
Grant access, once
Approve the access Zapier asks for. That connection is now reusable: every Craft.io step in every Zap picks it up, so you link the account once rather than once per Zap.
Your first Craft.io Zap: from feedback to backlog
GoalEach new piece of feedback in the category your team owns becomes a work item in the workspace it plans from.
- 01
Build: pick the trigger
In the Build phase, choose Craft.io as the trigger app and New Feedback Created as the event. Select your connection, then the feedback portal to watch.
- 02
Test it on real feedback
Run the trigger test. Zapier pulls the three most recent feedback items from that portal, so you map the next steps on a real request rather than an empty template.
- 03
Add the filter
Add a Filter step and, in Configure & test, compare the feedback category with the one your team owns. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Create the work item
Add Create New Work Item, pick the workspace and map a Title from the feedback. Both are required, and an empty title makes this step fail.
- 05
Test, then Publish
Use Test on each step and open the new item in Craft.io. Then click Publish: Zapier will look for new feedback on your plan's schedule.
Craft.io triggers: what starts a Zap
3 events start a Zap when something happens in Craft.io. Zapier checks for them at the interval your plan allows.
New Feedback Created
Polling triggerIn Zapier“Triggered when a new feedback item is added”
Whenever a request lands in one of your Craft.io feedback portals, this trigger passes it to Zapier so the next steps can act on it.
New Item Created
Polling triggerIn Zapier“Triggers when a new item is added”
Fires each time a regular work item appears in a Craft.io workspace, giving the rest of the Zap something to work with.
New OKR Created
Polling triggerIn Zapier“Triggers when a new OKR item is added”
Reacts to a new objective added in a Craft.io workspace, so the goals your leadership sets do not stay on a page nobody reads.
Craft.io actions: what the Zap can do
Craft.io gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create New Feedback
ActionIn Zapier“Creates a new feedback in the feedback portal”
Writes a request into a Craft.io feedback portal, so ideas from sales or support calls stop living in someone's notes.
Create New Work Item
ActionIn Zapier“Creates a new regular item”
Adds a regular item to a Craft.io workspace, the everyday unit your team plans and ships from.
Create New OKR
ActionIn Zapier“Creates a new OKR item”
Records a new objective in a Craft.io workspace from values an earlier step carried, so goals agreed in a meeting reach the tool.
When a Craft.io Zap breaks
Zapier attaches no help article to Craft.io, so the traps are the general ones, applied to a product backlog.
Good news first: a polling trigger remembers what it has already returned, so the same feedback never starts the Zap twice. The four cases below are where things really go wrong. If a run fails anyway, start with our Zapier troubleshooting guide.
Existing feedback is never picked up
The Zap only reacts to feedback, items and OKRs created after you publish it. Your current backlog stays where it is, and moving it is a separate job.A workspace that feeds itself
New Item Created and Create New Work Item on the same workspace make a loop: each item created starts the Zap again and eats through your tasks.A bulk import gets held back
Import a large batch of feedback or items at once and the trigger may return a huge set in one go. Zapier's flood protection can hold it back.A required field arrives empty
Create New Feedback needs six filled fields, the two other actions need a Workspace and a Title. One blank value and the action fails, with nothing created.
Need help automating Craft.io with Zapier?
A person reads every message.
