Lancey Zapier integrationAutomate Lancey with Zapier.
The Lancey Zapier integration has 0 triggers, 1 action and 0 searches. It does one job: it drops feedback into Lancey from any other app you already use, so your AI product manager reads what customers say without anyone copying it over.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lancey Zapier integration actually does
Lancey is an AI product manager: it reads product feedback, pulls insights out of it and suggests experiments. The Zapier side is narrow on purpose. It writes feedback into Lancey, and that is all. Something else has to start the Zap, because Lancey offers no event of its own that Zapier can listen to.
Three setups people build with it, each one resting on the single action, Create Feedback:
A feedback inbox that fills itself. A new message in your support mailbox becomes a Lancey entry with a title, the message text and a type such as "bug" or "request". Nobody pastes anything.
A form that feeds the backlog. Whatever form tool collects your NPS comments or feature requests starts the Zap, and each answer lands in Lancey as feedback, tagged by type.
A sales-call digest. Notes your team writes after a demo, in a doc or a CRM, travel to Lancey so product objections sit next to support tickets.
What Zapier does not do here: it cannot read anything back out of Lancey. No trigger fires when Lancey produces an insight, and there is no search step to look up an existing piece of feedback. So you cannot build "when Lancey suggests an experiment, post it in Slack" with this integration. Updating or deleting feedback is not on the menu either.
If you are still choosing a tool, see our Make vs Zapier comparison and our Zapier review.
Zapier words in one minute
You will meet these terms in the editor. Each one in plain words, once.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap. Lancey has none, so the trigger always comes from another app, like your inbox or a form.
- Action
- What the Zap does once started. Here, Create Feedback is the action: it writes a new entry into your Lancey workspace.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan gives you a monthly count of them.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and quietly stops it otherwise.
- Multi-step Zap
- Anything beyond one trigger plus one action. Add a filter or a second action and the Zap becomes one, which needs a paid plan.
What a Lancey Zap costs you
Short version: each feedback written into Lancey costs one task. Everything around it is free.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- One feedback created1 task
- Trigger checksFree, however often they run
The trigger never costs a task, and neither do the checks Zapier runs to spot new items. Only a Create Feedback that goes through is counted; a failed one is not. Lancey is not a premium app, so it works on the free plan, which gives 100 tasks a month and checks polling triggers every 15 minutes. The catch: the free plan only builds two-step Zaps. The moment you add a filter to keep spam out of Lancey, the Zap is multi-step and needs a paid plan.
Connect your Lancey account
- 01
Open the Apps page
In your Zapier account, go to the Apps page and click + Add connection. You need an existing Lancey account before you start, plus the right to add feedback to any workspace you do not own yourself.
- 02
Find Lancey and start the link
Type Lancey in the search box of the dialog that opens, pick it from the results, then click Add connection. A new browser tab opens on the Lancey side to finish the link.
- 03
Sign in and grant access
Log in to Lancey in that tab and allow Zapier to reach the account. The connection is saved once, under your Apps page, and every Zap that uses Lancey reuses it from then on.
Your first Lancey Zap, step by step
GoalTurn each support email into a piece of Lancey feedback, skipping auto-replies.
- 01
Build: choose the starting app
Create a Zap and pick the app that starts it, here your support mailbox. Lancey cannot be the first step, since it has no trigger.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from the connected account, so you map fields on a real email, not a blank sample.
- 03
Add the filter
From the plus icon, add Filter, then set the field, the rule and the value. Use a text rule on the subject. This step makes the Zap multi-step, so a paid plan.
- 04
Add Create Feedback
Pick Lancey, then Create Feedback. Map the subject to Title, the body to Content, and type a fixed word such as "support" in Type.
- 05
Test, then publish
Test the action and check the new entry inside Lancey. When it looks right, Publish the Zap to switch it on. Only emails that arrive after that point are handled.
The Lancey action
Lancey gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Feedback
ActionIn Zapier“Creates a Feedback in Lancey”
Writes a new piece of feedback into Lancey, with a title, the full text and a type, so the AI product manager can sort it alongside everything else it reads.
When a Lancey Zap breaks
Zapier publishes no help article and no specific limit for Lancey. What goes wrong comes from how Zaps behave in general.
Most failures here are not Lancey's fault: they come from the starting app, an empty required field, or a Zap that expected to pick up old data. If you get stuck, see our Zapier troubleshooting page.
Old feedback is never imported
A Zap only reacts to what happens after you publish it. Last month's emails or survey answers stay where they are; moving that backlog is a separate job.An empty field stops the run
Title, Content and Type are all required. When the source sends nothing for one of them, Create Feedback fails on that run and no task is counted.A bulk import gets held back
If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can pause it before anything reaches Lancey.Duplicates are rare, not impossible
If the starting trigger is a polling one, Zapier remembers what it has already seen, so one item does not create two entries. A second Zap on the same source would, though.
Need help automating Lancey with Zapier?
A person reads every message.



