Create Campaign
emelia.create_campaign
ActionEmailconnection required
Calls the Emelia API with the connection's credentials.
Create an empty multichannel campaign, ready for identities and steps.
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
2 fields, 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 |
|---|---|---|---|---|---|
name Name of the campaign; it must not already be used on the account. | string | Yes | — | — | Q4 outbound |
time_zone IANA timezone the sending window is read in; Emelia uses Europe/Brussels. | string | No | — | — | Europe/Paris |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"name": "Q4 outbound",
"time_zone": "Europe/Paris"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
campaign_id The new campaign's Emelia id. | string | — |
name The name the campaign was created with. | string | — |
result Emelia's own response object for the create. | object | — |
{
"campaign_id": "",
"name": "",
"result": {}
}See Create 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.