Flexmail MCP integration for AI agents.
Connect AI agents to Flexmail through 24 structured actions, including get contact, add contact interest subscription, delete interest, and unsubscribe conta…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Flexmail integration exposes
The Flexmail Agent App exposes 24 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent fetch a flexmail contact by id, subscribe a flexmail contact to an interest, and delete a flexmail interest by uuid. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. 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 Flexmail account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Flexmail capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADFetch a Flexmail contact by id.
INPUTS: id
add_contact_interest_subscriptionWRITESubscribe a Flexmail contact to an interest.
INPUTS: contactId / interestId
delete_interestHIGH IMPACTDelete a Flexmail interest by UUID.
INPUTS: id
unsubscribe_contactREVIEWUnsubscribe a Flexmail contact from all future communication.
INPUTS: id
add_contact_preference_subscriptionWRITESubscribe a Flexmail contact to a preference.
INPUTS: contactId / preferenceId
create_contactWRITECreate a Flexmail contact in a specific source.
INPUTS: email / first_name / name / language / custom_fields
create_interestWRITECreate a Flexmail interest.
INPUTS: name / visibility / label / description
get_interestREADFetch a Flexmail interest by UUID.
INPUTS: id
get_sourceREADFetch a Flexmail source by id.
INPUTS: id
list_account_contact_languagesREADFetch the contact languages configured for the Flexmail account.
list_contact_interest_subscriptionsREADList the interests to which a Flexmail contact is subscribed.
INPUTS: id
list_contact_preferencesREADList preferences selected by a Flexmail contact.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
idREQUIRED- The Flexmail contact id.
add_contact_interest_subscription
contactIdREQUIRED- The Flexmail contact id.
interestIdREQUIRED- The Flexmail interest UUID.
delete_interest
idREQUIRED- The Flexmail interest UUID.
unsubscribe_contact
idREQUIRED- The Flexmail contact id.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Fetch a Flexmail contact by id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactControl Add Contact Interest Subscription
Subscribe a Flexmail contact to an interest. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_contact_interest_subscriptionVerify with Get Interest
Fetch a Flexmail interest by UUID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_interestSAFETY BOUNDARY
Operate Flexmail with explicit limits
- Authorize Flexmail with Custom credentials and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_interest`, `remove_contact_interest_subscription`, and `remove_contact_preference_subscription` 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 Flexmail rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Flexmail task completed successfully.
CONNECTION MODEL
Custom credentials
Flexmail uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 14
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 1
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 Flexmail.