Constant Contact connector for AI agents

Tools your email marketing agent reaches for on Constant Contact, scoped per user.

CALL ANY TOOL

95 tools for email marketing in Constant Contact: create and update contacts, manage lists, tags, segments, and custom fields, create, test, and schedule email campaigns, read open, click, and bounce reports, and manage events.

constantcontact_account_email_create

Create account email

Add an email address to the account. Constant Contact emails it a confirmation link; it stays UNCONFIRMED until clicked. Returns the new address with its confirm_status. Use to add a sender address for campaigns. Returns 409 if the address already exists.

Parameters

Name

Type

Required

Description

email_address

string

Required

The email address to add (max 80 characters).

constantcontact_account_emails_list

List account emails

constantcontact_account_physical_address_get

Get account physical address

constantcontact_automation_get

Get automation

constantcontact_contact_counts_get

Get contact counts

constantcontact_contact_delete

Delete contact

constantcontact_contact_list_create

Create contact list

constantcontact_contact_list_update

Update contact list

constantcontact_contact_resubscribe

Contact resubscribe

constantcontact_contact_update

Update contact

Replace an existing contact's properties. Properties you leave out are cleared; sub-resources you leave out (lists, tags, custom fields, phones, addresses, notes) are kept. Returns the updated contact. Updating a deleted contact revives it. Use to edit a known contact by contact_id. Use Create or Update Contact for a partial update by email.

Parameters

Name

Type

Required

Description

contact_id

string

Required

The unique ID (UUID) of the contact. Get it from List Contacts.

update_source

string

Required

Who is updating the contact: Account or Contact. Use Account to revive a deleted contact. One of: `Account`, `Contact`.

anniversary

string

Optional

Anniversary date, for example the date the contact became a customer. Accepted formats include YYYY-MM-DD and MM/DD/YYYY (max 10 characters).

birthday_day

integer

Optional

Birthday day of month, 1 to 31. Must be sent together with birthday_month.

birthday_month

integer

Optional

Birthday month, 1 to 12. Must be sent together with birthday_day.

company_name

string

Optional

The company the contact works for (max 50 characters).

custom_fields

array

Optional

Custom field values, up to 25. Each item names a custom field by its custom_field_id and gives its value (or choice_ids for select fields). Example: [{"custom_field_id": "1b4fa3a6-3fdd-11e9-87e4-fa163e56c9b0", "value": "Gold"}].

email_address

string

Optional

The contact's email address (max 80 characters). Must be unique in the account. Only send it when the contact gave explicit permission to receive email.

first_name

string

Optional

The contact's first name (max 50 characters).

job_title

string

Optional

The contact's job title (max 50 characters).

last_name

string

Optional

The contact's last name (max 50 characters).

list_memberships

array

Optional

Contact list IDs to subscribe the contact to, up to 50. Get list IDs from List Contact Lists.

notes

array

Optional

Notes about the contact. Each item has content (max 2000 characters). Example: [{"content": "Met at the spring trade show."}].

permission_to_send

string

Optional

Permission the account has to email this contact. Sent with email_address. Valid values: explicit, implicit, not_set, pending_confirmation, temp_hold, unsubscribed. One of: `explicit`, `implicit`, `not_set`, `pending_confirmation`, `temp_hold`, `unsubscribed`.

phone_numbers

array

Optional

Phone numbers, up to 3. Each item has a phone_number (max 25 characters) and a kind: home, work, mobile or other. Example: [{"phone_number": "+1-555-555-0100", "kind": "work"}].

sms_channel

object

Optional

The contact's SMS channel, only when the contact gave explicit SMS consent. Holds full_sms_address (the number including dial code) and sms_channel_consents (an array of consent objects). See the Constant Contact contacts API reference for the consent shape.

street_addresses

array

Optional

Street addresses, up to 3. Each item needs a kind (home, work or other) and can have street, city, state, postal_code and country. Example: [{"kind": "home", "street": "123 Main St", "city": "Boston", "state": "MA", "postal_code": "02108", "country": "United States"}].

taggings

array

Optional

Tag IDs to assign to the contact, up to 50. Get tag IDs from List Tags.

constantcontact_contact_upsert

Upsert contact

Create a contact, or update it if the email address (or SMS number) already exists. Updates are partial and append lists and custom fields. Returns the contact_id and whether the contact was created or updated. Use when you don't know if the contact exists. Use Create Contact or Update Contact for full control of sub-resources.

Parameters

Name

Type

Required

Description

list_memberships

array

Required

Contact list IDs to add the contact to: at least 1 and up to 50. Get list IDs from List Contact Lists.

anniversary

string

Optional

Anniversary date. Accepted formats include YYYY-MM-DD and MM/DD/YYYY.

birthday_day

integer

Optional

Birthday day of month, 1 to 31. Must be sent together with birthday_month.

birthday_month

integer

Optional

Birthday month, 1 to 12. Must be sent together with birthday_day.

company_name

string

Optional

The company the contact works for (max 50 characters).

custom_fields

array

Optional

Custom field values, up to 50. Each item has a custom_field_id and a value. Example: [{"custom_field_id": "1b4fa3a6-3fdd-11e9-87e4-fa163e56c9b0", "value": "Gold"}].

email_address

string

Optional

The contact's email address (max 50 characters). Identifies the contact: an existing address is updated, a new one creates a contact. Required unless sms_channel is given.

first_name

string

Optional

The contact's first name (max 50 characters).

job_title

string

Optional

The contact's job title (max 50 characters).

last_name

string

Optional

The contact's last name (max 50 characters).

phone_number

string

Optional

The contact's phone number (max 25 characters).

sms_channel

object

Optional

The contact's SMS details, only with explicit SMS consent. Holds sms_address (number without country code), dial_code, country_code and sms_channel_consents (array of consent objects).

street_address

object

Optional

One street address. Needs a kind (home, work or other) and can have street, city, state, postal_code and country. Example: {"kind": "home", "street": "123 Main St", "city": "Boston", "state": "MA", "postal_code": "02108", "country": "United States"}.

constantcontact_contacts_add_tags

Contacts add tags

constantcontact_contacts_export_file_get

Get contacts export file

constantcontact_contacts_remove_from_lists

Contacts remove from lists

constantcontact_custom_field_delete

Delete custom field

constantcontact_email_ab_test_create

Create email ab test

constantcontact_email_bounces_report

Email bounces report

constantcontact_email_campaign_activity_preview_get

Get email campaign activity preview

constantcontact_email_campaign_activity_test_send

Send email campaign activity test

constantcontact_email_campaign_activity_update

Update email campaign activity

Update an email campaign activity's sender, subject, content and recipients. Only primary_email activities in DRAFT or DONE status can be updated. Returns the updated activity. Properties you leave out are cleared; html_content, physical_address_in_footer and document_properties are kept if omitted. Use to set recipients (contact_list_ids or segment_ids) before scheduling. Call Get Email Campaign Activity first to keep current values.

Parameters

Name

Type

Required

Description

campaign_activity_id

string

Required

The unique ID (UUID) of the email campaign activity. Get it from the campaign_activities array returned by Get Email Campaign (the activity with role primary_email holds the email content).

from_email

string

Required

The sender email address. Must be a CONFIRMED account email address.

from_name

string

Required

The sender name shown to contacts.

reply_to_email

string

Required

The reply-to email address. Must be a CONFIRMED account email address.

subject

string

Required

The email subject line.

contact_list_ids

array

Optional

Contact list IDs to send to. Cannot be combined with segment_ids.

document_properties

object

Optional

Optional settings for legacy email formats (format_type 1 and 2), such as text_content, permission_reminder and view_as_webpage_enabled. Ignored for other formats.

html_content

string

Optional

The email HTML, for custom code emails (format_type 5). Include [[trackingImage]].

physical_address_in_footer

object

Optional

The organization's physical address shown in the email footer. Needs address_line1, country_code (ISO 3166-1 two-letter, uppercase) and organization_name; state_code is required for US addresses. Can also have address_line2, address_line3, address_optional, city, postal_code and state_non_us_name. Leave empty to use the account's physical address. Example: {"organization_name": "Acme Inc.", "address_line1": "123 Main St", "city": "Boston", "state_code": "MA", "postal_code": "02108", "country_code": "US"}.

preheader

string

Optional

A short summary shown after the subject line.

segment_ids

array

Optional

A single segment ID to send to, as a one-item array. Cannot be combined with contact_list_ids.

constantcontact_email_campaign_get

Get email campaign

constantcontact_email_campaign_rename

Email campaign rename

constantcontact_email_campaigns_list

List email campaigns

constantcontact_email_didnotopens_report

Email didnotopens report

constantcontact_email_opens_report

Email opens report

constantcontact_email_resend_to_non_openers_delete

Delete email resend to non openers

constantcontact_email_unique_opens_report

Email unique opens report

constantcontact_event_create

Create event

constantcontact_event_registration_get

Get event registration

constantcontact_segments_list

List segments

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Constant Contact tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["constantcontact"], toolNames: [
    "constantcontact_contact_upsert",
    "constantcontact_email_campaign_create",
    "constantcontact_email_campaign_activity_schedule"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Create the June Update email and schedule it for Thursday at 10am" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["constantcontact"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Create the June Update email and schedule it for Thursday at 10am" }],
  tools,
});

// Execute the tool call with the user's vaulted Constant Contact OAuth token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["constantcontact"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Create the June Update email and schedule it for Thursday at 10am" }],
  tools,
});

// Tool call runs with the user's vaulted Constant Contact OAuth token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["constantcontact"] }, pageSize: 100,
});

const agent = new Agent({
  name: "email_marketing_agent",
  model: "gemini-2.5-pro",
  instruction: "Constant Contact tools scoped to this user",
  tools,
});

await agent.run("Create the June Update email and schedule it for Thursday at 10am");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Constant Contact tool. Click to copy, paste into your agent, done.

Contacts

Copy the prompt

Copied

Add jordan@acme.com to the Newsletter list, or update them if they already exist.

Copy the prompt

Copied

Tag every contact on the Spring Event list as attendee.

Copy the prompt

Copied

Export the contacts on the VIP list to a CSV file.

Campaigns

Copy the prompt

Copied

Create a draft email campaign called June Update from this HTML.

Copy the prompt

Copied

Send a test of the June Update email to me.

Copy the prompt

Copied

Schedule the June Update email for Thursday at 10am.

Reports

Copy the prompt

Copied

Show open and click rates for campaigns sent last month.

Copy the prompt

Copied

List contacts who did not open the spring sale email.

Copy the prompt

Copied

Which links in the spring sale email got the most clicks?

SEE HOW AUTH WORKS

Each user signs in to Constant Contact once, and Scalekit stores and refreshes their tokens. Credentials stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Constant Contact

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Constant Contact

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Constant Contact

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Constant Contact

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other email marketing connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Constant Contact token looks fine in a demo. In production every campaign send looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Constant Contact today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Constant Contact as the user or through a shared service account?

As the user. Each user signs in to Constant Contact once, and Scalekit stores and refreshes their tokens. Contact changes and campaign sends are attributed to that user in your audit trail, not a shared service account.

Where is the Constant Contact OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Constant Contact?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example contact and report tools without constantcontact_contacts_bulk_delete or constantcontact_email_campaign_delete. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Constant Contact access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent send a Constant Contact campaign right away?

Yes. constantcontact_email_campaign_activity_schedule sends an email campaign activity now or schedules it for a date. constantcontact_email_campaign_activity_test_send sends a test copy to up to 5 addresses first, and constantcontact_email_campaign_activity_unschedule cancels a scheduled send.