Resources · Zapier integration

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

Overview

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.

Vocabulary

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.
Cost

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

Connect your Lenz account to Zapier

  1. 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.

  2. 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.

  3. 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.

First 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Triggers

The Lenz trigger

1 event starts a Zap when something happens in Lenz. Zapier checks for them at the interval your plan allows.

1

New Verification Completed

Polling trigger

In 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.

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
verifications are launched from several places and you want every verdict collected in one shared sheet or channel.
Watch out
only checks that finish after the Zap is switched on come through, so earlier verifications stay in Lenz.
Actions

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.

1

Ask Follow-Up

Action

In 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.

When to use it
a verdict came back and you want Lenz to explain one point of it in plain words.
Watch out
the question is capped at 500 characters, and the Test button returns a sample answer, not a real one.
2

Assess (Fast)

Action

In 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.

When to use it
you want a quick first pass on many lines before spending a full verification on the doubtful ones.
Watch out
past 10,000 characters the input is cut off with no warning.
3

Extract Claims

Action

In 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.

When to use it
a long draft would be cut off if sent whole to a check, so you split it into claims first.
Watch out
a Zap step has 30 seconds and reading a page can take longer; for a long page, send its text instead.
4

Verify a Claim

Action

In 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 to use it
a statement will be published or relied on, and you want the sources behind the verdict.
Watch out
clicking Test shows an example verdict only; the real check runs once the Zap is on.
When it breaks

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

Need help automating Lenz with Zapier?

A person reads every message.

FAQ

Lenz Zapier integration: frequent questions

01Is the Lenz Zapier integration free?
Yes, for Zaps of two steps. Lenz is not a premium app, so the free plan accepts it, with 100 tasks a month and Zaps made of one trigger and one action. A new spreadsheet row sent to Assess (Fast) fits that limit. As soon as you add a filter on the verdict or a second Lenz action, the Zap turns multi-step and needs a paid plan. Lenz's own pricing is a separate matter that this page does not cover.
02How many tasks does a Lenz Zap use?
One task for each action that completes, and nothing for the trigger. A Zap that sends each new row to Assess (Fast) uses one task per row. A Zap that extracts claims, then verifies one, then posts the verdict uses three tasks per run. An action that fails is not counted. A few apps and actions take more than one task when they complete, so watch the count during your first runs.
03Does Lenz send results to Zapier in real time?
No. New Verification Completed is a polling trigger: Zapier asks Lenz for finished checks on a timer. On the free plan that happens every 15 minutes, on Professional every 2 minutes, and on Team and Enterprise every minute. The type comes from how Lenz built its side and cannot be changed in the editor. The actions are another story: Assess (Fast) answers in about 10 seconds within the step itself.
04What does it take to connect Lenz to Zapier?
A Lenz account, nothing more on the Zapier side. Open Apps, click + Add connection, search for Lenz, click Add connection, then sign in and grant access in the tab that opens. The connection is reused by every Lenz step afterwards. For Ask Follow-Up you will also need a verification ID, picked from the recent list or mapped from an earlier Verify a Claim step. If a step later fails to find that ID, check that it really comes from the verification and not from a task.
05Why does Lenz ignore the end of a long text?
Because input over 10,000 characters is cut off without warning on Assess (Fast) and Verify a Claim. Nothing fails, the end is simply never checked. Send long documents to Extract Claims first: it reads up to the first 50,000 characters of a text or a public page, then you check claims one by one. For a long web page, send the text rather than the address, since a Zap step only has 30 seconds.
06What if the Lenz operation you need is missing?
Then the integration cannot do it today. Lenz offers one trigger and four actions: extract, assess, verify and ask a follow-up. There is no search, so finding an old verification by its content is not possible from a Zap. What you can do is store each verification ID in another tool when New Verification Completed fires, then map it into Ask Follow-Up later. For anything else, check whether the other app of your Zap covers it.
07Zapier, Make or n8n for Lenz?
It depends on your criteria, not on a ranking. On Zapier, Lenz gives four actions and one polling trigger that work from the free plan. The 30-second limit of a Zap step matters for long page reads, so check how each platform handles long-running steps. Hosting, the price of each run and how much control you want over the flow are the other points to compare. Try your own case on each before you decide.