Lead Agent

Connect AI agents to Lead Agent, a Czech omnichannel CRM and marketing platform. Agents import leads in bulk, move them between groups with a destination status, create funnels and contacts, and send mobile verification codes before outreach.

20 actions API key available

Lead Agent website ↗ Platform Documentation ↗ Capability data verified 2026-08-04

A campaign export, a form batch, or a scheduled poll starts the run

Get Lead is called by telephone or email, which is a lookup rather than a search, to test whether the person is already known

Search Leads pages the near-matches on name so ambiguous rows are separated from clean ones

Add Leads writes the unmatched rows in one bulk call of up to 500 records

Add Group and Move Leads place the new records into the group and destination status the campaign expects

The campaign owner is told how many were created, how many were matched, and how many were held

A person approves the recipient set before Send Verification Code puts an SMS on a real handset

What This Integration Enables

Lead Agent is a Czech omnichannel CRM and marketing platform, and its V2 public API is unusually honest about what it is for. There is no deal object, no pipeline value, no forecast. There are leads, the contact details attached to them, funnels, groups, and a mobile verification service. That is the shape of a platform built around getting a real, reachable person into a campaign rather than around reporting on a sales process, and it means an agent working here is doing acquisition work, not pipeline hygiene. The most useful thing about the surface is that it is bulk-first where it counts: Add Leads creates up to 500 leads in a single call, Move Leads moves a set between groups with a destination status, and Remove Leads From Groups strips a set out. With a rate limit of 100 requests per minute per IP address, the difference between the bulk actions and a per-row loop is the difference between a list landing in one call and a list not landing at all.

Two details shape how flows are built. Get Lead is a direct fetch by ID, telephone, or email rather than a search, which makes it the right dedup primitive: an exact identifier either resolves to a record or it does not, with no relevance ranking to interpret. Search Leads is the paginated fuzzy path for name matching, and it belongs on the ambiguous rows rather than on every row. Every response is a JSON envelope carrying status_code, error, error_code, and data, so a flow reads the envelope rather than the HTTP status. Two things are worth stating plainly because the action names invite the wrong assumption. First, this connector ships no triggers. Add Leads accepts an optional callback URL, but that callback reports on the bulk job you submitted, to an endpoint you nominate. It does not register a FlowRunner listener, and nothing here makes Lead Agent push events into a flow, so change detection is a scheduled Search Leads poll. Second, the funnel actions are Create Funnel, Get Funnel, and Search Funnels. Funnels can be created and read, and lead movement in this connector happens between groups, not between funnel stages. The bulk movement verbs are Move Lead and Move Leads and their destination is a group with a status. There is also no delete anywhere on this surface: Remove Lead From Group and Remove Leads From Groups take a lead out of a group, and the lead record itself stays.

Without FlowRunner

Imports are one row at a time Each lead is posted individually, so a list arrives slowly and the rate limit is hit for no reason

Duplicates are found afterwards The same person is loaded twice and discovered when they get two messages

Group membership is manual People are dragged into groups by hand, so the group is only accurate the day it was built

With FlowRunner

Imports go in one call Up to 500 leads are created per request, so a list lands as a single unit with one result to read

Duplicates are found before the write Get Lead by telephone or email runs first, so a match becomes an update rather than a second record

Group membership follows the data Leads are moved between groups with a destination status as their state changes, on an approved set

Use Case Scenarios

A campaign list that lands as one call instead of five hundred

A list arrives from an event, a partner, or a spreadsheet in Google Sheets. Rather than posting each row, the agent first runs Get Lead on each telephone number and email, which is a direct lookup and returns a record or nothing. Matches become Update Lead calls that enrich the existing record instead of creating a second one, and Update Contact keeps the telephone and email details current. The remainder is batched and sent through Add Leads in a single call of up to 500. That one design decision is what keeps the run inside the 100 requests per minute limit, and it means the campaign owner gets one result envelope to read rather than five hundred outcomes to reconcile. Add Group creates the campaign's group if it does not exist, and Get Groups confirms what the account already has so the flow does not fragment the taxonomy with a near-duplicate group name.

Group membership that reflects behaviour instead of the day it was built

A group in Lead Agent is what the platform's own outreach acts on, so membership is the real control surface. On a schedule, the agent runs Search Leads across the segments a campaign cares about, joins each lead to the engagement signal held in an analytics or event system, and computes the set that should change treatment. Leads that engaged are gathered for Move Leads into the follow-up group with a destination status. Leads that went quiet are gathered for Remove Leads From Groups. The agent does not execute either immediately. It writes the two sets and their sizes into the campaign owner's channel first, because moving a set of people between groups is the same as changing who receives the next message, and it uses the bulk verbs rather than looping so the whole change either happens as one intent or does not happen.

Reachability checked before a number is trusted, not after

An inbound form supplies a mobile number that may or may not belong to the person who typed it. The agent adds the lead with Add Contact so the number is attached to the record, then holds. Send Verification Code, Resend Verification Code, and Check Verification Code exist as a three step handshake precisely because verification is a conversation with a human being rather than a data quality check. Where the flow is verifying a single number a person actively requested, it sends and then polls Check Verification Code before promoting the lead into an outreach group. Where the flow is verifying a batch, it stops at the gate below, because a verification code is an SMS that arrives on somebody's phone whether or not they asked for it.

Human-in-Loop Highlight

Send Verification Code is the action on this connector that leaves the system entirely. Everything else writes a record, moves a record, or reads one, and all of it stays inside Lead Agent where a person with a login can look at it and fix it. A verification code does not stay inside Lead Agent. It is an SMS that lands on a real handset, at whatever hour the flow happened to run, belonging to a person who may have mistyped their number, or given someone else's, or filled in a form months ago and forgotten. There is no unsend, there is no delete on this surface to remove the lead that triggered it, and Resend Verification Code makes the same mistake twice as cheap to repeat. That risk is small for one number that a person just asked to verify and large for a batch, because the batch is where an agent can put hundreds of messages on hundreds of phones from a single decision it made on its own. So the gate sits between Add Leads and Send Verification Code, and it is about the recipient set rather than the message. The agent posts to the campaign owner: "The import created 412 leads. 388 carry a mobile number in a plausible national format, 24 do not and are listed below. Of the 388, 61 already existed and were matched by telephone through Get Lead, which means those handsets have had a code from us before. Verification sends an SMS to a real phone and cannot be recalled. Send to all 388, send only to the 327 that are new to us, or hold?" The owner answers once, and only the approved set goes through Send Verification Code, with Check Verification Code polling the results and Move Leads promoting the confirmed numbers into the outreach group. This is the human-in-the-loop moment on an acquisition platform: the agent is fully capable of choosing the audience, and choosing an audience whose phones will ring is a decision that belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

20 actions

Leads

Get Lead Fetches one lead by ID, telephone, or email. This is a direct lookup rather than a search, which makes it the reliable dedup check before any create.
Search Leads Searches by name, telephone, or email with pagination. Used for the fuzzy matches that a direct lookup cannot resolve, so ambiguous rows can be separated out for review.
Update Lead Updates a lead's profile fields. Used to enrich an existing record instead of creating a second one for the same person.
Add Leads Bulk-creates up to 500 leads in a single call, with an optional callback URL that reports on the submitted job to an endpoint you nominate. This is the action that keeps a list import inside the rate limit.

Contacts

Add Contact Attaches a telephone number or email address to a lead. Used when a new channel for an existing person arrives from a form or another system.
Get Contact Retrieves a lead's contact details. Used to confirm which number a verification code would actually reach before one is sent.
Update Contact Updates a lead's telephone and email details. Used to correct a channel without disturbing the rest of the lead profile.

Funnels

Create Funnel Creates a funnel, which Lead Agent also calls a strategy. Used when a new campaign needs its own structure rather than reusing an existing one.
Get Funnel Retrieves a single funnel by ID. Used to confirm a funnel exists before a flow references it.
Search Funnels Returns the funnels in the account. Used to resolve a funnel by name so a flow does not create a near-duplicate of one that already exists.

Groups

Get Group Retrieves a single group. Used to confirm the destination of a move before the move happens.
Get Groups Returns the groups in the account. Used to resolve a campaign's group by name and to keep the group taxonomy from fragmenting.
Add Group Creates a group. Used to give a campaign its own audience container at the moment the campaign is set up.
Remove Lead From Group Removes one lead from a group. The lead record itself remains; only the membership that drives outreach is withdrawn.
Remove Leads From Groups Removes a set of leads from groups in one call. Used for the disengagement sweep, where looping would be both slow and rate limited.
Move Lead Moves one lead between groups with a destination status. Used when a single record's state changes and its treatment should change with it.
Move Leads Moves a set of leads between groups with a destination status in one call. Because group membership is what the platform's own outreach acts on, this runs on an approved set.

Mobile Verification

Send Verification Code Sends an SMS verification code to a mobile number. The message reaches a real handset and cannot be recalled, so batch sends run only after a person has approved the recipient set.
Resend Verification Code Sends the code again to the same number. Used when a code did not arrive, and held to the same approval as the original send.
Check Verification Code Validates a code the recipient supplied and returns the verification outcome. Used to promote a confirmed number into an outreach group.

Frequently Asked Questions

What can FlowRunner do with Lead Agent?

FlowRunner agents can run Get Lead, Search Leads, and Update Lead in Lead Agent, plus 17 more actions.

Does connecting Lead Agent to FlowRunner require OAuth?

No. Lead Agent connects to FlowRunner with an API key, no OAuth flow required.

Can Lead Agent trigger a FlowRunner workflow automatically?

Lead Agent doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Lead Agent

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us