Start Campaign
emelia.start_campaign
ActionEmailconnection required
Calls the Emelia API with the connection's credentials.
Start a campaign and let Emelia schedule its first actions.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Emelia
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- list_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
campaign_id The campaign's Emelia id, as returned by emelia.create_campaign or list_campaigns. | string | Yes | — | — | 65f0a1b2c3d4e5f6a7b8c9d0 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"campaign_id": "65f0a1b2c3d4e5f6a7b8c9d0"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
campaign_id The campaign the action was applied to. | string | — |
success True when Emelia accepted the action. | boolean | — |
result Emelia's own response object for the action. | object | — |
{
"campaign_id": "",
"result": {},
"success": false
}Notes
- Emelia answers 400 with the reason unless the campaign has at least one identity, at least one recipient (15,000 maximum), a valid sequence, and connected accounts for its identities.
See Start Campaign run in a workflow.
In a technical demo we add the Emelia connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.