LinkedIn Lead Gen Forms
AdvertisingPull LinkedIn Lead Gen Form submissions into your workflows. Agents list the forms a sponsored ad account owns, inspect form definitions, and retrieve lead responses with each member's name, email, and company answers for CRM sync and follow-up.
What This Integration Enables
LinkedIn Lead Gen Forms exist to remove friction for the prospect, and they succeed: a member taps twice and their name, email, and company answers are yours. The friction just moves to your side, because those answers sit inside Campaign Manager until someone goes and gets them. This connector makes retrieval an agent's job. FlowRunner agents list the forms a sponsored account owns, inspect each form's definition before mapping answers downstream, and pull responses on a schedule with a time-window filter so nothing is fetched twice. The connector is read-only by design, which makes it the intake side of an orchestration: the writes happen in your CRM, your outreach tool, and your prospect's inbox, and that is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate belongs. - Poll a sponsored ad account for new submissions on a schedule, filtered by submission time - Inspect form definitions with field lists before wiring answers into CRM properties - Retrieve a single submission by URN to hydrate a record with the member's full answers - Route every lead through a named human decision before outreach begins
Without FlowRunner
With FlowRunner
Use Case Scenarios
Speed-to-lead without the export
A demand gen team runs three lead gen campaigns for a webinar series. A FlowRunner agent calls List Lead Form Responses every 15 minutes with a submitted-at window covering the gap since the last run. Each new submission is matched against [HubSpot](/integrations/hubspot) by email; net-new members become contacts with the form and creative recorded, and known contacts get an activity note instead of a duplicate. A summary posts to [Slack](/integrations/slack) so the SDR on duty sees every lead while the webinar is still on the prospect's mind.
Field mapping that survives form edits
Marketing ops changes a lead form mid-campaign, adding a company size question. Because the agent calls Get Lead Form before mapping any batch, it detects the new field, appends the answers to the tracking sheet in [Google Sheets](/integrations/google-sheets), and flags the ops owner that the CRM property map needs a decision: create a new property or fold the answers into an existing one. No submissions are dropped while the humans decide, because the raw responses keep landing in the sheet with every field intact.
One pipeline for a multi-account agency
An agency manages sponsored accounts for six clients. A nightly agent calls List Lead Forms per account to enumerate active forms, then List Lead Form Responses per account for the day's window. Each client's leads are written to that client's CRM, and a per-client digest goes to the account manager. When a submission looks malformed, the agent calls Get Lead Form Response with the compound URN to pull the full answer set before deciding whether it is a real lead or a test entry, and ambiguous cases go to the account manager rather than into a client's pipeline.
Human-in-Loop Highlight
List Lead Form Responses returns something unusual for an advertising API: the exact words a real person typed while asking to be contacted. The action itself is a read, but everything downstream of it reaches that person, and the first touch cannot be recalled once a cadence tool sends it. So the agent stops before enrollment. It posts the batch with each member's answers, the form they came from, and the CRM match result, and the campaign owner decides who enters the sequence, who goes to nurture, and who was a competitor filling out forms. The agent also refuses to guess on field mapping: if Get Lead Form shows a field the property map does not cover, a person resolves it before any answer is written to a record a rep will quote back to the prospect. Machine speed on retrieval, human judgment on the send.
Agent Capabilities
4 actionsLead Forms
2- List Lead Forms Lists the lead gen forms owned by a sponsored ad account, with each form's id, name, status, and locale. The enumeration step for multi-form and multi-account pipelines.
- Get Lead Form Retrieves a single form's definition: headline, privacy policy, locale, and the fields it collects. Used before mapping so answers land in the right CRM properties even after a form is edited.
Lead Form Responses
2- List Lead Form Responses Lists the submissions collected for a sponsored ad account, each carrying the member's answers, the originating form and creative, and the submission time. Supports a submitted-at time window and pagination, which makes scheduled incremental pulls reliable.
- Get Lead Form Response Retrieves a single submission by its full LinkedIn URN, returning the member's complete answers, lead type, and source. Used to hydrate one record with full context before a routing decision.
Frequently Asked Questions
What can FlowRunner do with LinkedIn Lead Gen Forms?
FlowRunner agents can run List Lead Forms, Get Lead Form, and List Lead Form Responses in LinkedIn Lead Gen Forms, plus 1 more action.
Does connecting LinkedIn Lead Gen Forms to FlowRunner require OAuth?
Yes. LinkedIn Lead Gen Forms connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can LinkedIn Lead Gen Forms trigger a FlowRunner workflow automatically?
LinkedIn Lead Gen Forms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LinkedIn Lead Gen Forms
$100 in credits. No card required. Connect in minutes.