Short answer: Drop the "Klaviyo → List Campaigns" 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 |
|---|---|---|---|
Channel channel | options | Optional | Channel to filter by. Klaviyo requires a channel filter on this endpoint — pick one of email, sms, or mobile_push. |
Page Cursor page_cursor | string | Optional | Cursor for the next page of results. Copy from the previous response's links.next field. Leave empty for the first page. |
Sort sort | options | Optional | Sort order for the results. |
{"channel": "{{trigger.channel}}","page_cursor": "WyIyMDI2...","sort": "{{trigger.sort}}"}
{"data": [{"id": "01JCAMP123456789","type": "campaign","attributes": {"name": "Spring Sale 2026","status": "draft","audiences": {"excluded": [],"included": ["UxYzAb"]},"created_at": "2026-04-20T09:00:00+00:00","updated_at": "2026-04-22T14:30:00+00:00","send_options": {"use_smart_sending": true}}}],"links": {"next": null,"self": "https://a.klaviyo.com/api/campaigns"}}
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.