Lenz Zapier integrationAutomate Lenz with Zapier.
The Lenz Zapier integration offers 1 trigger, 4 actions and 0 searches. Lenz checks factual claims with AI and returns sourced verdicts. Through Zapier, any tool can send it a claim, and a finished check can start the next step on its own.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lenz Zapier integration does for your content
Lenz is a fact-checking service built on AI: you hand it a claim, it researches it, spots made-up statements and returns a verdict with its sources. Connected to Zapier, it stops being a tab you open by hand and becomes a step that runs whenever text arrives somewhere else.
Three results worth building. A quick screen on incoming text: a new row in a spreadsheet goes to Assess (Fast), which answers in about 10 seconds, so a doubtful line is flagged before anyone reuses it. A list of what needs checking: Extract Claims reads a block of text or a public web page and pulls out the factual statements, without judging them yet. A full report on the claims that matter: Verify a Claim runs the complete research, debate and panel review, then New Verification Completed carries the sourced verdict to the people who need it.
What Zapier does not do here. There is no search, so a Zap cannot look up an older verification by its content; Ask Follow-Up needs the verification ID handed over by an earlier step or picked from the recent list. Lenz also cuts long input without warning: past 10,000 characters for a claim, so long documents go through Extract Claims first. And pages behind a login stay unreadable.
To weigh other platforms on the same job, see our n8n vs Zapier comparison.
Zapier vocabulary in one minute
Seven words come back across this page. Here is each one in plain terms.
- Zap
- The automation you build on Zapier: 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 waits for that event and reacts to it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, here often a request to Lenz.
- Task
- The unit Zapier bills: one action your Zap completed successfully. The quota of your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer, Zapier asks the app for new items. An instant trigger is pushed by the app the moment it happens.
- Filter
- A step that lets the Zap carry on only when the data that arrived meets a condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
What a Lenz Zap really costs on Zapier
Lenz is not a premium app, so it runs on the free plan. Zapier bills the actions that succeed, never the trigger.
- Premium appNo, works on the free plan
- Tasks on the free plan100 per month
- Cost of the trigger0 tasks
- Steps allowed on the free plan2 (one trigger, one action)
Each Lenz action that completes counts as one task: an assessment, an extraction, a verification, a follow-up answer. An action that fails is not counted, and the New Verification Completed trigger costs nothing however often Zapier checks. The free plan gives 100 tasks a month and Zaps of two steps. Chain Extract Claims and Verify a Claim, or add a filter on the verdict as in the Zap below, and the Zap becomes multi-step, so it needs a paid plan.
Connect your Lenz account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Lenz account before you start, plus access to anything you do not own that the Zap should touch.
- 02
Find Lenz and add it
Type Lenz in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens on the Lenz side to finish the link there.
- 03
Sign in and grant access
Log in to Lenz in that tab and let Zapier reach the account. The connection is then saved, listed on the Apps page and reused by every Lenz step you add to any Zap.
Your first Zap: flag the Lenz verdicts that need a look
GoalEach time a full verification finishes in Lenz, post it to your team chat, but only when the result matches the rule you set.
- 01
Build: pick the trigger
Create a Zap, choose Lenz as the app and New Verification Completed as the event, then select your Lenz connection in the account box.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent finished verifications of the account, so you pick a real one and build the rest on actual data.
- 03
Add the filter
Click the plus icon, add Filter, then set the field to watch, the rule and the value. For a score, pick a number rule: a text rule on a number never passes.
- 04
Add the chat message
Add the action in your team chat and map the verdict and its sources into the message. Test the step and check that the message really landed in the channel.
- 05
Publish
Click Publish to switch the Zap on. Because of the filter this is a multi-step Zap, so it needs a paid plan; without it, the same Zap fits the free plan.
The Lenz trigger
1 event starts a Zap when something happens in Lenz. Zapier checks for them at the interval your plan allows.
New Verification Completed
Polling triggerIn Zapier“Triggers when a fact-check finishes.”
Starts the Zap once a full fact-check has finished in Lenz, and hands the finished verification to the next step, so the result reaches people without anyone refreshing the Lenz screen.
The 4 Lenz actions
Lenz gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Ask Follow-Up
ActionIn Zapier“Asks a follow-up question about a completed verification and returns the answer.”
Puts a further question to a verification that already finished and returns the answer, drawn from the research and evidence of that check.
Assess (Fast)
ActionIn Zapier“Checks a claim and returns a verdict for it, in about 10 seconds. Several claims in one input are each assessed separately. A claim that could not be checked comes back as an "Error" row with an Error Code saying why and a Hint saying what to send instead.”
Returns a quick verdict in about 10 seconds. Paste a paragraph that holds several claims and each one gets its own verdict.
Extract Claims
ActionIn Zapier“Pulls the verifiable factual claims out of a block of text, or out of a public web page given its URL, without checking them. Status is "ready" when claims were found, "not_a_claim" when none were, or "no_match" when a Focus excluded all of them.”
Pulls the factual statements out of a text, or out of a public web page given its address, and leaves them unchecked so you decide what to verify next.
Verify a Claim
ActionIn Zapier“Runs the full fact-checking pipeline on one claim — research, debate, and panel review — and returns a sourced verdict with score and citations. Takes about 90 seconds.”
Sends one claim through the complete process (research, debate, panel review) and returns a verdict with a score and citations, in about 90 seconds.
When a Lenz Zap breaks
Zapier links no help article to Lenz. Besides the input limits seen above, these general limits hit any Lenz Zap.
Most of these never throw an error while you build. They show up later as a missing verdict or a quota that drains too fast. When one of them bites, open our Zapier troubleshooting page.
Old verifications are never picked up
A Zap only reacts to what happens after you switch it on. Verifications finished before that stay in Lenz, and moving them elsewhere is a separate job.A verdict that starts its own check loops
If the step after New Verification Completed launches a new verification, the Zap sets itself off again and again and burns through your tasks.A sudden batch can be held back
When a trigger returns a huge batch at once, after a bulk import for example, Zapier's flood protection can hold it back instead of running every item.The same verification runs once
Zapier remembers what it already saw on a polling trigger. A verification it has handled will not start the Zap a second time.
Need help automating Lenz with Zapier?
A person reads every message.



