CActionConstant ContactUpdated September 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.

Add Contact to List in Constant Contact — start free All 8 Constant Contact actions

Add Contact to List in Constant Contact — start free

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
List IDs list_ids	string	Required	Comma-separated list IDs
Contact IDs contact_ids	string	Required	Comma-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.

Gmail → Constant Contact

1 Gmail triggers

Slack → Constant Contact

13 Slack triggers

Google Sheets → Constant Contact

2 Google Sheets triggers

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 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 Add Contact to List support batch operations?

Run Add Contact to List 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