CActionConstant ContactUpdated September 2026

How do I remove a contact from a Constant Contact list?

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

Remove Contact from 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.

FieldTypeRequiredDescription
List IDs
list_ids
stringRequiredComma-separated list IDs
Contact IDs
contact_ids
stringRequiredComma-separated contact IDs to remove
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 Remove Contact from List.

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

FAQ

Questions about Remove Contact from List.

What does the Remove Contact from List action do in Constant Contact?
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.
What inputs does Remove Contact from 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 Remove Contact from List support batch operations?
Run Remove Contact from 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

Other Constant Contact actions.

Remove Contact from List in Constant Contact — start free