Unbounce

Pull landing page and lead data out of Unbounce: agents list pages, pop-ups, and sticky bars, retrieve the leads each one captured, and inventory sub-accounts and custom domains for routing, reporting, and CRM sync.

7 actions API key available

Unbounce website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A scheduled sweep opens, timed to catch form submissions since the last run

List Pages inventories the landing pages, pop-ups, and sticky bars currently live

List Page Leads pulls submissions per page with a date-range filter, so only new leads move

Get Lead retrieves each submission's normalized form data, capturing variant, and integration extras

The agent validates the lead: work email or free domain, required fields present, which campaign the page belongs to

Leads that fail validation or match an existing account go to the marketing ops owner with the submitted data attached, instead of silently entering a nurture sequence

Clean leads sync to the CRM and the nurture audience, tagged with page and variant so attribution survives the handoff

What This Integration Enables

Unbounce is where conversion happens; everything after the form fill is somebody else's problem, and that somebody is usually a marketer with a CSV export. This connector makes the after-the-form work an agent's job. FlowRunner agents inventory every page, pop-up, and sticky bar in an account, pull the leads each one captured with date-range precision, retrieve individual submissions with their variant and integration data, and map the sub-account and custom-domain structure that agencies use to keep clients apart. The connector is read-only against Unbounce, which does not make the workflows around it low-stakes. A lead record is a person's data plus an implied promise about what happens next, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits between the read and the downstream sends it can trigger. - Sync new form leads from pages, pop-ups, and sticky bars into CRMs, email tools, or spreadsheets - Audit every page in an account or in a specific client sub-account, with publish state and live URL - Retrieve single leads with normalized form data for routing, follow-up, and notification workflows - Inventory sub-accounts and the custom domains published under each one - Feed page and lead data to an AI agent for qualification and routing decisions

Without FlowRunner

Leads exported by hand Someone downloads CSVs per page, and leads from Tuesday reach sales on Friday

Attribution dies at the form The CRM gets a name and email but not which page, pop-up, or variant actually converted them

Client data blurs together An agency's sub-accounts each capture leads, and keeping them separated is a manual discipline

With FlowRunner

Leads move on a schedule Date-filtered sweeps pull new submissions into the CRM within the hour

Variant-level attribution Every synced lead carries the page and variant that captured it, so reporting reflects what worked

Sub-account boundaries enforced Workflows scope reads per client, and cross-client mixing becomes structurally impossible

Use Case Scenarios

The lead sweep that replaces the CSV ritual

Hourly, the agent runs List Page Leads across the active campaign pages with a date filter set to the last sweep. Each new lead lands in [HubSpot](/integrations/hubspot) as a contact carrying the page name and capturing variant as properties. Leads with free-mail domains or gibberish fields queue for review instead of entering the sales rotation. The Friday CSV export stops existing, and the first-touch clock starts an hour after the form fill instead of three days.

The agency's per-client reporting pack

An agency runs a sub-account per client. Weekly, the agent walks List Sub Accounts, pulls each client's pages with List Sub Account Pages, counts leads per page with List Page Leads, and confirms live domains with List Domains. The result: one report per client in [Google Sheets](/integrations/google-sheets), posted to that client's channel in [Slack](/integrations/slack). No client ever sees another client's numbers, because the workflow reads within one sub-account at a time by construction.

Qualification before the sequence, not after the complaint

New leads from a high-traffic pop-up flow through an AI agent that reads each submission via Get Lead, checks the company against the existing customer list, and scores fit from the form data. Qualified net-new leads sync to [Mailchimp](/integrations/mailchimp) for nurture. Existing customers route to their account owner instead of a cold sequence. Ambiguous cases go to a human with the full submission attached. The nurture list stays clean because the sorting happens before enrollment, not after an unsubscribe.

Human-in-Loop Highlight

List Page Leads hands an agent people, not rows: names, emails, submitter IPs, and whatever else the form asked for. The read is reversible; what it feeds is not. The moment those leads enter a nurture audience or a sales cadence, emails go out that cannot be unsent, and in an agency account the nightmare version is specific: leads pulled from one client's sub-account landing in another client's campaign. So FlowRunner workflows built on this connector put the gate between read and send. Sweeps and scoring run at machine speed, but a new page's leads do not start flowing into any sequence until the marketing ops owner has confirmed which sub-account they belong to, which audience they feed, and that the form's promise matches what the sequence will send. The agent moves the data; a person decides where it is allowed to go.

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

7 actions

Leads

List Page Leads Retrieves all form leads collected by a given page, pop-up, or sticky bar, each including the submitted form data plus extras from third-party integrations. Date-range filtering makes incremental sweeps precise. The action every lead-sync workflow is built on.
Get Lead Retrieves a single lead by id: normalized form data, submitter IP, the variant that captured it, and integration extras. The full-context read behind qualification and routing decisions.

Sub Accounts

List Sub Accounts Retrieves all sub-accounts (Unbounce Clients) under the account. Sub-accounts group pages and domains per project or client, and their ids scope the actions below.
List Sub Account Pages Retrieves all pages belonging to a specific sub-account, with sorting, date filtering, and pagination. The per-client inventory read.

Domains

List Domains Retrieves all custom domains registered under a specific sub-account. Unbounce scopes domains to sub-accounts, so a sub-account must be selected first.

Frequently Asked Questions

What can FlowRunner do with Unbounce?

FlowRunner agents can run List Pages, Get Page, and List Page Leads in Unbounce, plus 4 more actions.

Does connecting Unbounce to FlowRunner require OAuth?

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

Can Unbounce trigger a FlowRunner workflow automatically?

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

Start building with Unbounce

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

Start Building Free Talk to us