ActiveCampaign MCP integration for AI agents.
Connect AI agents to ActiveCampaign through 6 structured actions, including get contact, upsert contact, and get current user. Review authentication, inputs…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ActiveCampaign integration exposes
The ActiveCampaign Agent App exposes 6 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent get one activecampaign contact by identifier, create or update an activecampaign contact using the official contact sync endpoint, and get the current activecampaign user associated with the api token. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ActiveCampaign account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ActiveCampaign capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADGet one ActiveCampaign contact by identifier.
INPUTS: contactId
upsert_contactWRITECreate or update an ActiveCampaign contact using the official contact sync endpoint.
INPUTS: email / firstName / lastName / phone / fieldValues
get_current_userREADGet the current ActiveCampaign user associated with the API token.
list_contactsREADList ActiveCampaign contacts with pagination, search, and filtering support.
INPUTS: limit / offset / search / emailLike / listId
list_fieldsREADList ActiveCampaign custom contact fields.
INPUTS: limit / offset
list_listsREADList ActiveCampaign mailing lists with pagination and optional name filtering.
INPUTS: limit / offset / name
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
contactIdREQUIRED- ActiveCampaign contact identifier.
upsert_contact
emailREQUIRED- Contact email address used as the sync key.
firstNameOPTIONAL- Contact first name to create or update.
lastNameOPTIONAL- Contact last name to create or update.
phoneOPTIONAL- Contact phone number to create or update.
fieldValuesOPTIONAL- Custom field values to write during the contact sync.
list_contacts
limitOPTIONAL- Maximum number of contacts to return.
offsetOPTIONAL- Offset for retrieving the next ActiveCampaign page.
searchOPTIONAL- Free-text search applied to contact names, email, phone, or organization.
emailLikeOPTIONAL- Substring filter applied to the contact email address.
listIdOPTIONAL- Only return contacts associated with this list identifier.
list_fields
limitOPTIONAL- Maximum number of custom fields to return.
offsetOPTIONAL- Offset for retrieving the next ActiveCampaign custom fields page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Get one ActiveCampaign contact by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactControl Upsert Contact
Create or update an ActiveCampaign contact using the official contact sync endpoint. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
upsert_contactVerify with Get Current User
Get the current ActiveCampaign user associated with the API token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate ActiveCampaign with explicit limits
- Authorize ActiveCampaign with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ActiveCampaign rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ActiveCampaign task completed successfully.
CONNECTION MODEL
API key
ActiveCampaign API token sent with the Api-Token request header. Find it on the Developer settings page: https://help.activecampaign.com/hc/en-us/articles/207317590-Getting-started-with-the-API.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ActiveCampaign.