Short answer: Drop the "LinkedIn Ads → Get LinkedIn Ads Campaign Analytics" 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 |
|---|---|---|---|
Campaign ID campaign_id | string | Required | Numeric ID of the LinkedIn campaign |
Start Date date_start | date | Required | Reporting window start (YYYY-MM-DD) |
End Date date_end | date | Required | Reporting window end (YYYY-MM-DD) |
Granularity time_granularity | select | Optional | Time granularity of returned rows |
{"campaign_id": "{{trigger.campaign_id}}","date_start": "2025-01-01","date_end": "2025-01-31","time_granularity": "{{trigger.time_granularity}}"}
{"elements": [{"clicks": 320,"costInUsd": "450.25","impressions": 12500,"oneClickLeads": 8,"externalWebsiteConversions": 14}]}
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.