Short answer: Drop the "Constant Contact → Send Email 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 Activity ID campaign_activity_id | string | Required | Campaign activity ID (each campaign has a primary_email activity) |
Scheduled Date scheduled_date | string | Optional | Use 0 to send immediately or an ISO-8601 timestamp |
{"campaign_activity_id": "c1c75a40-3122-11ee-a32f-fa163e56c9b0","scheduled_date": "0 for now, or 2026-05-01T15:00:00Z"}
{"scheduled_date": "2026-05-01T15:00:00Z"}
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.