Short answer: Drop the "LinkedIn Ads → List LinkedIn Ads Lead Responses" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Lead Form ID form_id | string | Required | ID of the Lead Gen Form |
Ad Account ID ad_account_id | string | Required | Owning ad account ID |
{"form_id": "{{trigger.form_id}}","ad_account_id": "{{trigger.ad_account_id}}"}
{"elements": [{"id": "urn:li:leadFormResponse:556677","answers": [{"questionId": "email","answerDetails": {"textQuestionAnswer": {"answer": "lead@example.com"}}}],"submittedAt": 1736000000000}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.