List Email Campaigns: Constant Contact action

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
Limit limit	string	Optional	Number of campaigns to return (max 500)
Status status	options	Optional	Filter by campaign status

Sample request

{
  "limit": "50",
  "status": "{{trigger.status}}"
}

Returns

{
  "campaigns": [
    {
      "name": "April Newsletter",
      "type": "CUSTOM_CODE_EMAIL",
      "created_at": "2026-04-01T10:00:00Z",
      "campaign_id": "b1c75a40-3122-11ee-a32f-fa163e56c9b0",
      "current_status": "DRAFT"
    }
  ]
}

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

FAQ

Questions about List Email Campaigns.

What does the List Email Campaigns action do in Constant Contact?

Returns paginated campaigns with state (DRAFT, SCHEDULED, SENT, DONE). Useful for "weekly performance report" workflows that aggregate sent-campaign metrics.

What inputs does List Email Campaigns require?

List Email Campaigns 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 Email Campaigns support batch operations?

Yes. Run List Email Campaigns inside a Loop node to process arrays. Tiny Command handles Constant Contact's rate limits automatically so you don't have to throttle manually.

More actions