CActionConstant ContactUpdated September 2026
How do I send a Constant Contact campaign?
Short answer: You can send email campaign in Constant Contact by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Constant Contact Send Email Campaign action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Sample request
{"campaign_activity_id": "c1c75a40-3122-11ee-a32f-fa163e56c9b0","scheduled_date": "0 for now, or 2026-05-01T15:00:00Z"}
Returns
{"scheduled_date": "2026-05-01T15:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Email Campaign.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Email Campaign.
What does the Send Email Campaign action do in Constant Contact?
Triggers send for a previously-created campaign (created in Constant Contact UI). For "trigger weekly newsletter on schedule" or "approval clicked in Slack → fire the campaign" workflows.
What inputs does Send Email Campaign require?
Required: Campaign Activity ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Constant Contact returns an error?
The run history shows the failed step with its input and the error message Constant Contact returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Send Email Campaign support batch operations?
Run Send Email Campaign inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Constant Contact's rate limits.
More actions
Other Constant Contact actions.
Action
Add Contact to List
Adds an existing contact to a specific list — list membership drives campaign targeting. Useful for "lead matched ICP criteria → add to high-intent list for the next campaign" workflows.
ActionCreate Contact
Inserts a new contact with email (dedupe key), name, phone, and custom fields. The standard hook for "form submission → push to CC list" sync workflows.
ActionList Contacts
Paginated contacts with filters by list, status, recently modified. For warehouse-sync workflows, use the modified-since filter to incrementally pull only touched contacts.
ActionList Email Campaigns
Returns paginated campaigns with state (DRAFT, SCHEDULED, SENT, DONE). Useful for "weekly performance report" workflows that aggregate sent-campaign metrics.
ActionRemove Contact from List
Removes the contact from a specific list while preserving the contact record. For "campaign over → remove from the campaign list" hygiene or for "user changed preferences → unsubscribe from this segment only" granular preference automation.
ActionSearch Contact by Email
Lookup by exact email match. The standard "find before update" pattern for upsert workflows.