Short answer: Drop the "Klaviyo → Create Campaign" 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 Name name | string | Required | Name of the campaign |
List ID list_id | string | Required | The ID of the list to send the campaign to |
Subject Line subject | string | Required | Email subject line |
From Email from_email | string | Required | Sender email address |
{"name": "Spring Sale 2026","list_id": "e.g. UxYzAb","subject": "Don't miss our Spring Sale!","from_email": "newsletter@yourcompany.com"}
{"data": {"id": "01JCAMP987654321","type": "campaign","attributes": {"name": "Spring Sale 2026","status": "draft","audiences": {"excluded": [],"included": ["UxYzAb"]},"created_at": "2026-04-23T10:00:00+00:00","updated_at": "2026-04-23T10:00:00+00:00"}}}
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.