Start free
CActionConstant ContactUpdated June 2026

How do I add a contact to a Constant Contact list?

Short answer: You can add contact to list in Constant Contact by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Constant Contact Add Contact to List 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.

Use this actionAll 8 Constant Contact actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
List IDs
list_ids
stringRequiredComma-separated list IDs
Contact IDs
contact_ids
stringRequiredComma-separated contact IDs to add
Sample request
{
  "list_ids": "e.g. 12345678-1234-1234-1234-123456789012",
  "contact_ids": "e.g. 06d4ca6a-3122-11ee-a32f-fa163e56c9b0"
}
Returns
{
  "state": "initialized",
  "activity_id": "a8c75a40-3122-11ee-a32f-fa163e56c9b0",
  "percent_done": 0
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Add Contact to List.

Any of these apps can fire this action as part of a workflow.

C
Gmail → Constant Contact
1 Gmail triggers
C
Slack → Constant Contact
13 Slack triggers
C
Google Sheets → Constant Contact
2 Google Sheets triggers
C
HubSpot → Constant Contact
18 HubSpot triggers
FAQ

Questions about Add Contact to List.

What does the Add Contact to List action do in Constant Contact?
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.
What inputs does Add Contact to List require?
Required: List IDs, Contact IDs. 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Add Contact to List support batch operations?
Yes. Run Add Contact to List inside a Loop node to process arrays. TinyCommand handles Constant Contact's rate limits automatically so you don't have to throttle manually.
More actions

Other Constant Contact actions.

Action
Create 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.
Action
List 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.
Action
List Email Campaigns
Returns paginated campaigns with state (DRAFT, SCHEDULED, SENT, DONE). Useful for "weekly performance report" workflows that aggregate sent-campaign metrics.
Action
Remove 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.
Action
Search Contact by Email
Lookup by exact email match. The standard "find before update" pattern for upsert workflows.
Action
Send Email Campaign
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.