Short answer: Drop the "Pinterest → Get Pinterest Pin 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 |
|---|---|---|---|
Pin ID pin_id | string | Required | The Pin ID assigned by Pinterest. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Start Date (YYYY-MM-DD) start_date | string | Required | — |
End Date (YYYY-MM-DD) end_date | string | Required | — |
Metrics metric_types | string | Optional | — |
{"pin_id": "{{trigger.pin_id}}","start_date": "{{trigger.start_date}}","end_date": "{{trigger.end_date}}","metric_types": "{{trigger.metric_types}}"}
{"all": {"lifetime_metrics": {"SAVE": 50,"PIN_CLICK": 100,"IMPRESSION": 1000}}}
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.