Instapage
AdvertisingSync Instapage landing-page leads into the rest of your stack. Agents list subaccounts and pages, pull captured form submissions filtered by page or date window, and read publish status and URL details for campaign audits.
What This Integration Enables
A landing page is a promise that someone will follow up, and the follow-up is where campaigns actually win or lose. The media budget buys the click, the page earns the submission, and then the whole investment sits in a lead table waiting on an export habit. Instapage captures the submission; this connector makes sure it goes somewhere while it is still worth something. FlowRunner agents read workspaces, pages, and captured leads, all workspace-scoped, so agencies running dozens of subaccounts can drive every client's lead flow from the same set of flows. - Sync captured leads into a CRM or email list on a tight cycle, filtered by page or date window - Audit landing pages across every workspace an agency or enterprise account manages - Export campaign form submissions into spreadsheets and reporting flows, scoped by page or date window - Read a page's publish status and URL details before paid traffic gets pointed at it The workspace scoping is the structural advantage for agencies. One personal API token reaches every workspace the issuing user can access, at that user's permission level, so a single set of FlowRunner flows serves every client: same sync logic, same audit sweep, same validation rules, parameterized by workspaceId instead of rebuilt per account. The connector reads; what the reads feed, sales queues, nurture enrollments, client reports, is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) judgment applies.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Speed-to-lead as a standing property
During a paid campaign, the agent polls List Page Leads with a submittedAfter window, validates each submission, and creates the contact in [HubSpot](/integrations/hubspot) with the source page attached. A task lands on the assigned rep's queue in the same cycle. The lead that used to wait for Friday's export gets a call while the landing page is still open in their browser. Page-level attribution rides along on every record, so when the campaign retro asks which page produced the leads that closed, the CRM already knows.
The agency's cross-client page audit
An agency manages many client workspaces. Weekly, the agent chains List Subaccounts and List Pages, pulls Get Page for publish status and URL details, and writes the full inventory to [Google Sheets](/integrations/google-sheets): workspace, page, group, published URL, last updated, one row per page across every client. Pages that changed since last week get flagged in the [Slack](/integrations/slack) summary. When a client asks what is live, the answer is current, not archaeological, and the monthly reporting deck starts from an inventory nobody had to rebuild. The audit also catches the quiet liabilities: the expired-offer page still published, the campaign page still collecting leads nobody syncs.
Campaign leads flow into the nurture audience
A webinar campaign's pages capture registrations. The agent pulls the leads per page, enrolls each in the nurture audience via [Mailchimp](/integrations/mailchimp), and logs the enrollment. Backfills are the exception path: when someone widens the date window to re-sync history, the batch stages for review first, because re-enrolling three months of old leads into a fresh sequence is a decision, not a sync. The nurture audience grows in near real time, and every enrollment traces back to the page and the day it came from.
Human-in-Loop Highlight
List Page Leads is where a date-window mistake becomes a customer-facing incident: widen submittedAfter by a quarter, and the sync does not fail, it faithfully delivers three months of stale leads into a live nurture sequence, and every one of those people gets an email that makes no sense to receive in July about a January webinar. The sends are downstream, but the blast radius is set right here, at the read. So FlowRunner agents hold two rules on this connector. The incremental window advances mechanically and its leads flow without ceremony, because same-hour follow-up is the whole point. Any manual widening of the window, and any cycle whose lead volume spikes far past the page's baseline, form spam does this, stages its batch for the campaign manager with counts by page and date before a single downstream enrollment fires. The sync is relentless. The re-sync asks first.
Agent Capabilities
4 actionsSubaccounts
1- List Subaccounts Lists the Instapage workspaces the API key can access, owned or as a team member, each exposing the workspaceId every page and lead operation requires. Paginated for large agency accounts. The resolution step that starts every flow on this connector.
Pages
2- List Pages Lists a workspace's landing pages with optional last-updated window and page-group filters, paginated. Supplies the pageId for detail reads and per-page lead filtering.
- Get Page Retrieves one landing page's full details by workspaceId and pageId: name, group, publish and URL details, timestamps. The pre-flight read before traffic is pointed at a page, and the audit read behind inventory sheets.
Leads
1- List Page Leads Lists form submissions captured in a workspace, optionally narrowed to a single page or a submitted date window, paginated. The lead-sync read at the center of this connector, and the one whose date window this page's gate watches.
Frequently Asked Questions
What can FlowRunner do with Instapage?
FlowRunner agents can run List Subaccounts, List Pages, and Get Page in Instapage, plus 1 more action.
Does connecting Instapage to FlowRunner require OAuth?
No. Instapage connects to FlowRunner with an API key, no OAuth flow required.
Can Instapage trigger a FlowRunner workflow automatically?
Instapage doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Instapage
$100 in credits. No card required. Connect in minutes.