Constant Contact
Turn orders and customer changes into the right Constant Contact audiences and campaigns, with a person approving what goes out.
22 ways to read, 11 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Constant Contact, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create contact listApproval by rule
- Create contactApproval by rule
- List contact campaign summaryRead
Example flow
- Constant Contact · List contact campaign summaryDone
- Constant Contact · Create contact listNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Constant Contact.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Constant Contact
- Constant Contact's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Constant Contact contacts with consent, lists, tags and custom fields, read segments, create draft campaigns, and read campaign and contact activity reports.
Constant Contact API docs- Source actions
- 22
- Destination actions
- 11
- Data types
- 15
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account emails1
- List account email addressesSource
Account email addresses with confirmation status and roles; confirmed addresses can be campaign senders.
Account1
- Get account summarySource
Organisation name, contact details, time zone and physical address.
Campaign activities1
- Get campaign activitySource
One email campaign activity with its headers, content, recipients lists or segments and status.
Campaign activity stats1
- Get campaign activity statisticsSource
Send, open, click, bounce and opt-out statistics for up to 10 campaign activities.
Campaign send history1
- List campaign activity send historySource
Each send of a campaign activity with its lists, segments, count and status.
Campaign summaries1
- List campaign summary reportsSource
Unique sends, opens, clicks, bounces and opt-outs per sent campaign.
Campaign tracking1
- List campaign tracking activitySource
Per-contact sends, opens, clicks, bounces, opt-outs, forwards or non-opens for one campaign activity.
Contact activity summary1
- List contact campaign summarySource
Recent campaigns sent to one contact, with send, open, click, bounce, forward and unsubscribe counts.
Contact activity1
- List contact tracking activitySource
Campaign sends, opens, clicks, bounces, opt-outs and forwards for one contact.
Contact lists4
- Create contact listDestinationNot retried automaticallyApproval before production
Creates a list.
- Get contact listSource
One list with its membership count.
- List contact listsSource
Contact lists with membership counts.
- Update contact listDestinationProvider duplicate protectionApproval before production
Changes a list's name, description or favourite flag.
Contacts6
- Create contactDestinationNot retried automaticallyApproval before production
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.
- Search contactsSource
Contacts by segment, or by created, updated or opt-out date ranges, with consent status and custom fields.
- Update contactDestinationProvider duplicate protectionApproval before production
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-upDestinationProvider duplicate protectionApproval before production
Creates or updates a contact by email and adds it to lists (sign-up form endpoint). Only for contacts who gave consent.
Custom fields4
- Create custom fieldDestinationNot retried automaticallyApproval before production
Creates a contact custom field.
- Get custom fieldSource
One contact custom field definition with its type and choices.
- List custom fieldsSource
Contact custom field definitions with types and choices.
- Update custom fieldDestinationProvider duplicate protectionApproval before production
Changes a custom field's label or choices.
Email campaigns4
- Create draft email campaignDestinationNot retried automaticallyApproval before production
Creates a custom-code email campaign as a draft. It has no recipients and is never scheduled or sent by Nexra.
- Get email campaignSource
One campaign with its activities.
- List email campaignsSourceIncremental
Email campaigns with status, optionally changed after or before a date.
- Rename email campaignDestinationProvider duplicate protectionApproval before production
Renames an email campaign. Content, recipients and schedule are not changed.
Segments2
- Get segmentSource
One segment with its criteria.
- List segmentsSource
Contact segments, most recently edited first or by name.
Tags4
- Create tagDestinationNot retried automaticallyApproval before production
Creates a contact tag.
- Get tagSource
One contact tag with its contact count.
- List tagsSource
Contact tags with contact counts.
- Rename tagDestinationProvider duplicate protectionApproval before production
Changes a tag's name.
Access and limits
- 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; account reads also need account_read.
- 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.
- Pagination
- Cursor links in _links.next.href; limits up to 500 (contacts), 1,000 (lists).
- Provider events
- Partner webhooks for billing events only; no contact webhooks for customer apps. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
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.
- 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.
- Intentionally excluded: unsubscribing contacts, scheduling, sending, test-sending or unscheduling campaigns, editing campaign activity content or recipients, bulk activities (imports, list membership jobs) and all deletes. Draft campaigns are created without recipients.
- Campaign tracking fields beyond contact_id, campaign_activity_id, tracking_activity_type, email_address, device_type and created_time (names, link URL, bounce code, opt-out reason) are mapped when present but were not confirmed in the guide examples.
- Account summary and account email reads need the account_read scope; connections authorised before this was added must be reauthorised.
- Constant Contact documents no idempotency key; creates are not repeated automatically when uncertain.
Developer reference
- Create the Constant Contact credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Constant Contact, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/constant-contact and the Connections API.