Leady

Identify website visitors in Czechia and Slovakia with Leady, reading identified company and person sessions and reconstructing their path. Agents route a researching account to sales before the interest cools.

14 actions API key available

Leady website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

The nightly poll of identified sessions on the tracked domain runs

Agent reads each session's action list to reconstruct the page-by-page path and time spent

Agent keeps only sessions that crossed the engagement threshold the team set

Agent resolves the company record by registration number for each qualifying session

Agent separates company-level identifications from person-level ones

Agent posts the company-level hits to sales with the path each one read

Person-level sessions go to the account owner, who decides whether the approach names the individual

What This Integration Enables

Leady is a visitor identification connector with two properties that put it somewhere different from the rest of the category. The first is scope: coverage is Czechia and Slovakia only, and companies resolve to a registration number, which means an identified visitor joins cleanly to the official register rather than to a fuzzy name match. Get Company returns registration number, legal form, address, region and NUTS code, industry, turnover and headcount bands with numeric bounds, website, verified emails and phone numbers, and contact persons. For a team selling into those two markets, that is a materially better join key than a domain.

The second property is the one to be honest about. Leady identifies sessions at the person level as well as the company level. Get Person returns a named individual with their email, employer, profile image, gender, social profiles and organisations, and List Session Actions reconstructs exactly which pages that session touched, in order, with seconds spent on each and the full location including query string. That is a detailed picture of one person's behaviour on your website, and it is assembled from an observation rather than from anything they submitted. Leady ships a control for this: personal-data fields return null when personal info is disabled on the account, which is a switch the account holder sets deliberately. FlowRunner's contribution is at the other end. The agent can read every session every night without a person present. What it does with a person-level record is a decision, and decisions like that are where human-in-the-loop belongs.

Without FlowRunner

A visit is a number in analytics Session counts and sources, with no way to connect them to an account

Sales calls start cold The rep opens the call with no idea which pages the buyer had already read

Segments live in one person's head The filter that defines a good visitor exists in someone's saved view and nowhere else

With FlowRunner

A visit is a named organization Sessions resolve to companies with registration number, turnover band and headcount band

Calls start with the path The rep knows the pages read, the order, and the minutes spent on each

Segments are shared and reusable A saved filter the team already trusts drives the flow that pulls the list

Use Case Scenarios

A morning digest of companies that were researching yesterday

Each night an agent calls List Sessions for the tracked domain, applying a saved filter the sales team already uses in the Leady app. The definition of a qualifying visit is therefore the one they agreed on, not one invented inside a flow. For each hit it calls Get Company with the secure token issued alongside the session, pulling registration number, turnover and headcount bands, address and verified contacts. It maps the magnitude fields onto the team's own segmentation using List Company Size Bands and List Turnover Bands, then posts a digest to Slack split by territory. Sales arrives to a list of organizations that spent real time on the site, sized against the segmentation they actually use.

Pipeline stage tagging driven by engagement

An agent watches session activity against a threshold: a company that returns three times in a fortnight, or spends more than a set number of minutes across the pricing and integration pages. When an account crosses it, the agent calls Assign Labels To Companies with the registration numbers and the label the team uses for active research. When a deal closes or the account is disqualified, a second flow calls Unassign Labels From Companies to clear it. Because labels key off registration numbers and all numbers in a call must belong to the same country, the agent groups by market before it writes. The tagging that used to be a Monday admin task becomes a property of the traffic.

Call preparation from the visit path

A meeting is booked. Before it, an agent pulls the account's recent sessions and calls List Session Actions on each, reconstructing the journey in order with the time spent on every page, the referrer and the search query that brought them in. It writes a short brief into the CRM record in Pipedrive: they came from a comparison search, read the security page twice, spent nine minutes on pricing, then left from the integrations index. If the expected traffic is missing, the agent checks List Blacklist, since a company excluded as an existing customer, a competitor or your own office will simply not appear in the session results, and knowing that is better than concluding they lost interest.

Human-in-Loop Highlight

The gate here sits on Get Person, not on anything the agent reads. Get Person returns a named individual behind a session, with their email address, employer, social profiles and gender, and List Session Actions returns the eight pages that person read and the fourteen minutes they spent on pricing. The agent now knows something specific about a specific human in a jurisdiction that treats that as personal data, and the person did not fill in a form to give it. Reading it is a configuration the account holder chose. Acting on it is a separate decision with a different weight, and an email that opens by referencing what someone read on your website cannot be unsent.

So the agent splits the queue. Company-level identifications flow to sales unattended, because an organization researching a product is an ordinary commercial signal and the outreach is addressed to a company. Person-level identifications stop and raise an automation exception to the account owner. The message carries the company, the person's role, the page path from List Session Actions, and the two drafts the agent has prepared: one addressed to the organization that references nothing personal, and one addressed to the individual that does. The question is which to send, or neither. The agent has an opinion and states it. It does not get to act on it. Where a team decides person-level approaches are never appropriate for its market, that becomes a standing rule in the flow rather than a habit that depends on who is on shift.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

14 actions

Sessions and Journeys

List Sessions Lists identified visitor sessions for a tracked website, each with the recognised company or person, first and last timestamps, referrer, search query, action count and time spent. Defaults to the last thirty days when no period is given, and can be filtered by session type, engagement thresholds or a saved filter. Each session carries the secure token that Get Company and Get Person require.
List Session Actions Returns the individual actions inside a single session, in order, with timestamp, seconds spent, page location including query string, and the action category, which is a pageview, an identification or a generic event. This is the action that reconstructs a journey rather than reporting that one happened.

Identified Visitors

Get Company Returns the full company record behind an identified session: registration number, legal form, address, region and NUTS code, industry, turnover and headcount bands with numeric bounds, website, verified emails and phone numbers, and contact persons. Requires the secure token issued with the company in List Sessions. Fields containing personal data return null when personal info is disabled on the account.
Get Person Returns the full person record behind an identified session, including email, associated company, profile image, gender, social profiles and organisations. Requires the secure token issued with the person in List Sessions. The company field is null when the employer could not be recognised.

Website Configuration

List Websites Lists the websites tracked by the account, each with tracking status, partner code, configured territories, form-tracker flag and the follow-up timeout settings for contacted, won and lost states. This is how a flow discovers the domain value every other action needs.
Get Website Returns the configuration of a single tracked website, including status, territories, CSV secret, form-tracker setting and the URLs for its session list and saved filters. Domains are stored lowercased without a leading www, and a leading dot means all subdomains are tracked.

Labels

List Labels Lists the labels defined for a tracked website, each with its numeric primary key, text and colour code. The primary keys are what the assignment actions consume.
Assign Labels To Companies Assigns up to ten labels to a set of companies identified by registration number, returning the companies affected. Registration numbers in a single call must all belong to the same country, so a flow spanning both markets groups before it writes.
Unassign Labels From Companies Removes up to ten labels from a set of companies identified by registration number. Used to clear a pipeline stage when a deal closes or an account is disqualified.

Filters and Reference Data

List Saved Filters Lists the saved session filters defined for a tracked website, with names, colours, creators and whether they are shared across the team. Passing a filter ID to List Sessions applies the same criteria the team already uses in the Leady app.
Get Saved Filter Returns a single saved filter including its raw definition, so a flow can inspect exactly which criteria it applies before relying on it. Worth doing when a shared team filter drives an automated route.
List Blacklist Lists the blacklist entries for a tracked website, each with the reason it was excluded, the matched company, the homepage and who created it. Reasons cover own visits, competitors, existing customers, other reasons and bug reports. Read-only here; entries are managed in the Leady app. This is the action that explains why expected traffic is absent from session results.
List Company Size Bands Returns the headcount bands Leady uses for a country, each with identifier, raw value, display label and numeric lower bound. Used to map the magnitude fields on a company record onto your own segmentation.
List Turnover Bands Returns the turnover bands Leady uses for a country, each with identifier, raw value, display label, currency and numeric lower bound. Used to interpret turnover fields or to build a revenue-based qualification rule.

Frequently Asked Questions

What can FlowRunner do with Leady?

FlowRunner agents can run List Websites, Get Website, and List Sessions in Leady, plus 11 more actions.

Does connecting Leady to FlowRunner require OAuth?

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

Can Leady trigger a FlowRunner workflow automatically?

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

Start building with Leady

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

Start Building Free Talk to us