Constant Contact

Constant Contact

This connector uses the Constant Contact V3 API (https://api.cc.email/v3), the email marketing service for small businesses: contacts with their email consent, lists, tags, custom fields and segments, email campaigns (create from HTML, set the audience, preview, test, schedule) and the reports of sent campaigns and of single contacts. It signs in with OAuth through an application you register in the Constant Contact developer portal. Events, SMS campaigns, social posts and partner endpoints are not part of it.

Setup (about 10 minutes)

1. Open the V3 developer portal at https://app.constantcontact.com/pages/dma/portal and sign in with the Constant Contact login of the account you want to connect (new applications are private: until Constant Contact approves them, only the user who created the app can authorize it).
2. Click New Application, give it a name (users see it on the consent screen), choose Authorization Code Flow and Implicit Flow and a refresh token type: Rotating Refresh Tokens (recommended) or Long Lived Refresh Tokens. Create it.
3. Open the app (Edit), add the redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP server URL>/api/mcp-oauth/callback when you host AnythingMCP yourself, then click Generate Client Secret. The secret is shown only once. Save.
4. Copy the API Key into CONSTANT_CONTACT_CLIENT_ID and the secret into CONSTANT_CONTACT_CLIENT_SECRET, leave CONSTANT_CONTACT_REFRESH_TOKEN empty and install.
5. Click Authorize with Provider and sign in to Constant Contact. The connector asks for the scopes account_read contact_data campaign_data offline_access (offline_access is what returns a refresh token). Run constant_contact_get_account_summary to check.

Tokens: an access token lasts 24 hours and is renewed automatically with the refresh token. With rotating refresh tokens every renewal returns a new refresh token and the previous one stops working, so do not use the stored token elsewhere; with long-lived ones the same token keeps working. Either kind expires when it is not used for 180 days: then authorize again. What the agent may do also depends on the privileges of the Constant Contact user who signed in (constant_contact_get_user_privileges).

Workflow

• Account: constant_contact_get_account_summary, constant_contact_list_account_emails (the confirmed sender addresses), constant_contact_get_user_privileges.
• Find contacts: constant_contact_list_contacts (by email, status, lists, tags, segment, dates; include adds lists, tags, custom fields, phones, addresses), constant_contact_get_contact, constant_contact_get_contact_counts.
• Add or change contacts: constant_contact_create_or_update_contact is the safe default (by email, partial update, adds to lists). constant_contact_create_contact fails when the email exists. constant_contact_update_contact replaces the whole contact, so read it first. constant_contact_delete_contact is installed switched off.
• Lists: constant_contact_list_contact_lists, constant_contact_get_contact_list, constant_contact_create_contact_list, constant_contact_update_contact_list; constant_contact_delete_contact_list is installed switched off. Membership in bulk: constant_contact_add_contacts_to_lists, constant_contact_remove_contacts_from_lists.
• Tags: constant_contact_list_tags, constant_contact_get_tag, constant_contact_create_tag, constant_contact_update_tag, constant_contact_add_tags_to_contacts, constant_contact_remove_tags_from_contacts.
• Custom fields and segments: constant_contact_list_custom_fields, constant_contact_get_custom_field, constant_contact_create_custom_field; constant_contact_list_segments, constant_contact_get_segment.
• Bulk changes run in the background and return an activity_id: follow it with constant_contact_get_activity until state is completed; constant_contact_list_activities shows recent ones.
• Campaigns: constant_contact_list_email_campaigns, then constant_contact_get_email_campaign for its activities; work on the activity with role primary_email: constant_contact_get_email_campaign_activity, constant_contact_get_email_preview, constant_contact_get_email_schedule, constant_contact_get_email_send_history.
• Build and send an email: constant_contact_create_email_campaign (your HTML with [[trackingImage]], sender from constant_contact_list_account_emails), constant_contact_update_email_campaign_activity to set contact_list_ids or segment_ids, constant_contact_rename_email_campaign if needed, constant_contact_get_email_preview and constant_contact_send_test_email to check, then constant_contact_schedule_email_campaign_activity (installed switched off) and constant_contact_unschedule_email_campaign_activity to stop a scheduled send.
• Results: constant_contact_list_email_campaign_summaries for recent campaigns, constant_contact_get_email_campaign_stats by campaign, constant_contact_get_email_campaign_activity_stats by activity, constant_contact_get_email_links_report per link, constant_contact_get_email_tracking_report for the contacts behind each number. One contact: constant_contact_get_contact_activity_details, constant_contact_get_contact_activity_summary, constant_contact_get_contact_open_click_rates.

Sending and consent are real: confirm first. Scheduling sends to every contact on the lists and cannot be undone once sending starts. Show the user the subject, sender, audience and time and schedule only after a clear yes. Add contacts only when they agreed to receive email from the business; never set permission_to_send to explicit for people who did not opt in. Unsubscribed contacts cannot be re-subscribed through the API without their own action.

Reading the answers: ids of contacts, lists, tags, custom fields, campaigns and campaign activities are UUIDs; segment ids are integers. A campaign has several activities: reports, previews, tests and schedules take the campaign_activity_id of the primary_email activity, not the campaign_id. Times are ISO 8601 in UTC (2026-10-30T14:05:00.000Z). Campaign current_status: Draft, Scheduled, Executing, Done, Error, Removed. Email permission_to_send: explicit, implicit, not_set, pending_confirmation, temp_hold, unsubscribed. Report counts are unique contacts unless the report says otherwise; rates are percentages.

Paging: list answers carry _links.next.href while more pages exist; stop when it is missing. Contacts, lists, tags, custom fields, activities and campaigns use a cursor= value in that link: pass it as cursor. Reports and segments use next=: pass it as next. Keep the other filters the same between pages.

Limits: 10,000 requests a day per application key (reset at 00:00 UTC) and 4 requests a second; over either the API answers 429 (quota_exceeded or throttled). Test emails: 50 recipients a day.

Errors: 401 an expired or revoked token (authorize again); 403 a missing scope or user privilege (check constant_contact_get_user_privileges); 404 an unknown id; 409 a duplicate (an email, list, tag or campaign name that already exists); 400 with error_key and error_message for invalid input; 202 from constant_contact_list_contacts with a segment while the result is still being built (ask again).