Ambivo MCP integration for AI agents.
Connect AI agents to Ambivo through 10 structured actions, including list contacts, create contact, and delete task. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 10
- 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 Ambivo integration exposes
The Ambivo Agent App exposes 10 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent list ambivo crm contacts with optional filters, sorting, and date range, create a new ambivo crm contact, and delete an ambivo crm task by id. 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 Ambivo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ambivo capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_contactsREADList Ambivo CRM contacts with optional filters, sorting, and date range.
INPUTS: matchFilter / evalObjectId / sort / pageSize / startDate
create_contactWRITECreate a new Ambivo CRM contact.
INPUTS: name / email / phone / source / status
delete_taskHIGH IMPACTDelete an Ambivo CRM task by ID.
INPUTS: taskId
create_leadWRITECreate a new Ambivo CRM lead.
INPUTS: name / email / phone / source / status
create_taskWRITECreate a new Ambivo CRM task.
INPUTS: name / description / status / priority / dueDate
list_leadsREADList Ambivo CRM leads with optional filters, sorting, pagination, and date range.
INPUTS: matchFilter / evalObjectId / sort / pageSize / pageNum
list_tasksREADList Ambivo CRM tasks with optional filters, sorting, and pagination.
INPUTS: matchFilter / sort / pageSize / pageNum
update_contactWRITEUpdate an existing Ambivo CRM contact by ID.
INPUTS: contactId / name / email / phone / source
update_leadWRITEUpdate an existing Ambivo CRM lead by ID.
INPUTS: leadId / name / email / phone / source
update_taskWRITEUpdate an existing Ambivo CRM task by ID.
INPUTS: taskId / name / description / status / priority
INPUT CONTRACTS
Know what the action needs before it runs.
list_contacts
matchFilterOPTIONAL- MongoDB-style filter object encoded into Ambivo's match_filter_dict query parameter.
evalObjectIdOPTIONAL- Whether Ambivo should evaluate ObjectId syntax in matchFilter.
sortOPTIONAL- Sort fields encoded into Ambivo's sort_dict query parameter. Use 1 for ascending and -1 for descending.
pageSizeOPTIONAL- The number of records to request from Ambivo.
startDateOPTIONAL- Start of the Ambivo created-date range in ISO 8601 format or YYYY-MM-DD.
create_contact
nameREQUIRED- Full name for the Ambivo lead or contact.
emailOPTIONALphoneOPTIONALsourceOPTIONALstatusOPTIONAL
delete_task
taskIdREQUIRED- The Ambivo task record ID.
create_lead
nameREQUIRED- Full name for the Ambivo lead or contact.
emailOPTIONALphoneOPTIONALsourceOPTIONALstatusOPTIONAL
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Contacts
List Ambivo CRM contacts with optional filters, sorting, and date range. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_contactsControl Create Contact
Create a new Ambivo CRM contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with List Leads
List Ambivo CRM leads with optional filters, sorting, pagination, and date range. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_leadsSAFETY BOUNDARY
Operate Ambivo with explicit limits
- Authorize Ambivo with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_task` 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 Ambivo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ambivo task completed successfully.
CONNECTION MODEL
API key
Ambivo API token used in the Authorization header with the Bearer scheme. Generate and view integration tokens in your Ambivo account integrations page: https://account.ambivo.com/integrations.
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
- 3
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 1
- 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 Ambivo.