Constant Contact
Read and write Constant Contact contacts with consent status, lists, tags and custom fields, with an explicit-consent sign-up upsert, and read email campaigns and reports.
Keep contacts, consent and list membership in Constant Contact aligned with CRM, event and commerce systems, and bring campaign results back for reporting.
Source actions
10
Destination actions
9
Data types
7
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
campaign activity stats
- Get campaign activity statisticsSource
Send, open, click, bounce and opt-out statistics for up to 10 campaign activities.
campaign summaries
- List campaign summary reportsSource
Unique sends, opens, clicks, bounces and opt-outs per sent campaign.
contact lists
- Create contact listDestinationNot retried automatically
Creates a list.
- Get contact listSource
One list with its membership count.
- List contact listsSource
Contact lists with membership counts.
- Update contact listDestinationDuplicate protected
Changes a list's name, description or favourite flag.
contacts
- Create contactDestinationNot retried automatically
Creates a contact. Permission to send is set only when given explicitly.
- Get contactSource
One contact with consent status, custom fields, lists and tags.
- List contactsSourceIncremental
Contacts with consent status, custom fields, lists and tags, filtered by status, list, tag or update time.
- Update contactDestinationDuplicate protected
Replaces a contact's core properties (full PUT). Unmapped core fields are cleared; lists, tags and custom fields not given are kept.
- Create or update contact from sign-upDestinationDuplicate protected
Creates or updates a contact by email and adds it to lists (sign-up form endpoint). Only for contacts who gave consent.
custom fields
- Create custom fieldDestinationNot retried automatically
Creates a contact custom field.
- List custom fieldsSource
Contact custom field definitions with types and choices.
- Update custom fieldDestinationDuplicate protected
Changes a custom field's label or choices.
email campaigns
- Get email campaignSource
One campaign with its activities.
- List email campaignsSourceIncremental
Email campaigns with status, optionally changed after or before a date.
tags
- Create tagDestinationNot retried automatically
Creates a contact tag.
- List tagsSource
Contact tags with contact counts.
- Rename tagDestinationDuplicate protected
Changes a tag's name.
Authentication
OAuth 2.0 (customer application, rotating refresh token)
Plans and access
All paid Constant Contact plans and trials. Needs a customer-owned application in the Constant Contact developer portal with the contact_data, campaign_data and offline_access scopes.
Test environment
Use a Constant Contact trial account with a developer application.
Rate limits
10,000 requests per day and 4 requests per second per application; HTTP 429.
Provider events
Partner webhooks for billing events only; no contact webhooks for customer apps. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Contact update uses Constant Contact's full replace (PUT): core properties that are not mapped (names, job title, company, birthday, anniversary) are cleared. Map every field you want to keep, or use contacts.upsert.
- permission_to_send is sent only when explicitly given. Whether a PUT without it keeps the stored value is not stated in the reference; it is documented as unverified.
- contacts.upsert uses the sign-up form endpoint, which Constant Contact says may set explicit permission even for unsubscribed contacts, so Nexra requires an explicit consent confirmation input.
- Unsubscribing, campaign sends, bulk activities and all deletes are not implemented.
- Constant Contact documents no idempotency key; creates are not repeated automatically when uncertain.