What can you do with the Constant Contact integration?

LiveContext exposes 20 operations on Constant Contact, covering contact, contact list, email campaign and custom field. Common uses include rename a list, cancel a draft and render tag picker.

Which OAuth scopes does Constant Contact require?

It depends on the operation: each one declares the scopes Constant Contact requires for it. The most common are contact_data (15 operations), campaign_data (4 operations) and account_read (1 operation).

LiveContext

All integrations

Constant Contact integration

Constant Contact V3 marketing platform API. Manage contacts, contact lists, custom fields, tags, and email campaigns. Build and schedule HTML email campaigns, segment audiences, and read account details. Ideal for email marketing automation, CRM-to-newsletter sync, lead nurture, and audience analytics integrations.

20 toolsOAuthAPI docs

Connect Constant Contact How integrations work

Common Constant Contact use cases

rename a list
cancel a draft
render tag picker
clean up old lists
unsubscribe leaver
display list picker
onboarding a new lead
display contact profile
bootstrap a tag taxonomy
incremental contact sync

What you can do with Constant Contact

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 6 operations

POSTcreate_contact
Creates a new Constant Contact contact with email and at least one list membership.
POSTcreate_or_update_contact
Creates or updates a Constant Contact contact in a single call, matching by email_address.
DELETEdelete_contact
Deletes a Constant Contact contact (soft delete; status=deleted).
GETget_contact
Retrieves a single Constant Contact contact by UUID with optional embedded sub-resources.
GETlist_contacts
Lists Constant Contact contacts with filters by email, list, segment, tag, status, or update window.
PUTupdate_contact
Replaces editable fields of an existing Constant Contact contact (PUT semantics).

Contact list, 5 operations

POSTcreate_contact_list
Creates a new Constant Contact mailing list with a unique name.
DELETEdelete_contact_list
Deletes a Constant Contact contact list.
GETget_contact_list
Retrieves a single Constant Contact contact list by UUID.
GETlist_contact_lists
Lists Constant Contact contact lists (mailing lists) with optional name and status filters.
PUTupdate_contact_list
Renames or restyles a Constant Contact contact list (PUT replace).

Email campaign, 3 operations

POSTcreate_email_campaign
Creates a Constant Contact email campaign with its primary email activity.
DELETEdelete_email_campaign
Deletes a Constant Contact email campaign (soft delete).
GETlist_email_campaigns
Lists Constant Contact email campaigns with optional name and last-edited filters.

Custom field, 2 operations

POSTcreate_custom_field
Creates a new Constant Contact custom field (string or date).
GETlist_custom_fields
Lists the custom fields configured on the Constant Contact account.

Tag, 2 operations

POSTcreate_tag
Creates a new Constant Contact contact tag.
GETlist_tags
Lists Constant Contact contact tags with optional total count.

Account, 1 operation

GETget_account_details
Retrieves the authenticated Constant Contact account summary.

Email campaign schedule, 1 operation

POSTschedule_email_campaign
Schedules a Constant Contact email campaign activity (immediate or future send).

OAuth scopes Constant Contact requires

Each operation declares the scopes Constant Contact requires for it.

contact_dataneeded by create_contact, create_contact_list, create_custom_field and 12 more
campaign_dataneeded by create_email_campaign, delete_email_campaign, list_email_campaigns and 1 more
account_readneeded by get_account_details

Constant Contact API rate limits

4 requests per second
10,000 requests per day

Default V3 API rate limit is 4 requests per second per account, with a 10,000 daily cap. Burst rates above 4/s receive 429.

These are the limits Constant Contact documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Constant Contact documentation for current values.

Use Constant Contact from Claude Code, Cursor or Codex

Connect Constant Contact in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Constant Contact operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Constant Contact

Create your workspace
Sign up free. Nothing to install.
Connect Constant Contact once
Add your Constant Contact connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Constant Contact integration FAQ

What can you do with the Constant Contact integration?: LiveContext exposes 20 operations on Constant Contact, covering contact, contact list, email campaign and custom field. Common uses include rename a list, cancel a draft and render tag picker.
Which OAuth scopes does Constant Contact require?: It depends on the operation: each one declares the scopes Constant Contact requires for it. The most common are contact_data (15 operations), campaign_data (4 operations) and account_read (1 operation).
What are the Constant Contact API rate limits?: Constant Contact documents 4 requests per second and 10,000 requests per day. Default V3 API rate limit is 4 requests per second per account, with a 10,000 daily cap. Burst rates above 4/s receive 429. Limits are set by Constant Contact and can depend on your plan.