BigMailer MCP integration for AI agents.
Connect AI agents to BigMailer through 13 structured actions, including create list, create contact, and delete contact. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 13
- 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 BigMailer integration exposes
The BigMailer Agent App exposes 13 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent create a contact list in a bigmailer brand, create a contact in a bigmailer brand, and delete a bigmailer contact by id or email address. 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 BigMailer account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BigMailer capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_listREADCreate a contact list in a BigMailer brand.
INPUTS: brandId / name
create_contactWRITECreate a contact in a BigMailer brand.
INPUTS: brandId / validate / email / fieldValues / listIds
delete_contactHIGH IMPACTDelete a BigMailer contact by ID or email address.
INPUTS: brandId / contactId
delete_listHIGH IMPACTDelete a BigMailer contact list without deleting its contacts.
INPUTS: brandId / listId
get_brandREADGet one BigMailer brand by ID.
INPUTS: brandId
get_contactREADGet one BigMailer contact by ID or email address.
INPUTS: brandId / contactId
get_listREADGet one BigMailer contact list by ID.
INPUTS: brandId / listId
list_brandsREADList brands in the BigMailer account.
INPUTS: limit / cursor
list_contactsREADList contacts in a BigMailer brand, optionally filtered by list.
INPUTS: brandId / limit / cursor / listId
list_listsREADList contact lists in a BigMailer brand.
INPUTS: brandId / limit / cursor
update_contactWRITEUpdate a BigMailer contact by ID or email address.
INPUTS: brandId / contactId / fieldValuesOp / listIdsOp / unsubscribeIdsOp
update_listREADUpdate a BigMailer contact list name.
INPUTS: brandId / listId / name
INPUT CONTRACTS
Know what the action needs before it runs.
create_list
brandIdREQUIRED- The BigMailer brand ID.
nameREQUIRED- The list name.
create_contact
brandIdREQUIRED- The BigMailer brand ID.
validateOPTIONAL- Whether BigMailer should validate email deliverability before adding the contact.
emailREQUIRED- The contact email address.
fieldValuesOPTIONAL- Field values to save with the contact. Each name must match a BigMailer field tag name.
listIdsOPTIONAL- IDs of lists the contact should belong to.
delete_contact
brandIdREQUIRED- The BigMailer brand ID.
contactIdREQUIRED- The BigMailer contact ID or email address.
delete_list
brandIdREQUIRED- The BigMailer brand ID.
listIdREQUIRED- The BigMailer list ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create List
Create a contact list in a BigMailer brand. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_listControl Create Contact
Create a contact in a BigMailer brand. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Brand
Get one BigMailer brand by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_brandSAFETY BOUNDARY
Operate BigMailer with explicit limits
- Authorize BigMailer with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` and `delete_list` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BigMailer rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BigMailer task completed successfully.
CONNECTION MODEL
API key
BigMailer REST API key sent in the X-API-Key header. Create or view API keys from the BigMailer API documentation and account settings: https://docs.bigmailer.io/.
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
- 8
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 2
- 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 BigMailer.