Start free
CActionConstant ContactUpdated June 2026

How do I list Constant Contact contacts?

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

List Contacts in Constant Contact — start free All 8 Constant Contact actions
List Contacts 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
Limit
limit
stringOptionalNumber of contacts to return (max 500)
Status
status
optionsOptionalFilter by subscription status
Sample request
{
  "limit": "50",
  "status": "{{trigger.status}}"
}
Returns
{
  "contacts": [
    {
      "last_name": "Doe",
      "contact_id": "06d4ca6a-3122-11ee-a32f-fa163e56c9b0",
      "first_name": "John",
      "email_address": {
        "address": "user@example.com"
      }
    }
  ],
  "contacts_count": 1
}

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

Triggered by

Apps that pair well as the trigger for List Contacts.

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 List Contacts.

What does the List Contacts action do in Constant Contact?
Paginated contacts with filters by list, status, recently modified. For warehouse-sync workflows, use the modified-since filter to incrementally pull only touched contacts.
What inputs does List Contacts require?
List Contacts has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Contacts support batch operations?
Yes. Run List Contacts 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
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.
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 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.
List Contacts in Constant Contact — start free