Integration

Ambivo integration

Ambivo is a CRM, accounting and ERP platform for small and mid-sized businesses. Create, update, list and aggregate leads, contacts, accounts, deals (opportunities), orders, invoices and tasks, poll records created or updated in a time window, read comments, look up a person's pipeline journey or leads by marketing source, read sales reports (pipeline, deal timeline, leaderboard, agent goals, users) and manage appointments. The Security Q&A module, the raw entity-data passthrough and setting agent goals are not exposed. Authentication is an access token generated in the Ambivo account under Integrations, sent as a Bearer token in the Authorization header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ambivo.Built from the 54 Ambivo tools below, on the connection you add once.

What you can do with Ambivo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Aggregate, 7 operations

  • aggregate_accountsAggregate accountsPOSTAgents: ask firstAggregate accounts by group-by fields, ideal for dashboards, charts, and analytics.
  • aggregate_contactsAggregate contactsPOSTAgents: ask firstAggregate contacts by group-by fields, ideal for dashboards, charts, and analytics.
  • aggregate_dealsAggregate dealsPOSTAgents: ask firstAggregate deals/opportunities by group-by fields, ideal for dashboards, charts, and analytics.
  • aggregate_invoicesAggregate invoicesPOSTAgents: ask firstAggregate invoices by group-by fields, ideal for dashboards, charts, and analytics.
  • aggregate_leadsAggregate leadsPOSTAgents: ask firstAggregate leads by group-by fields, ideal for dashboards, charts, and analytics. Use this endpoint to generate counts, sums, averages, min/max grouped by one or more lead fields.
  • aggregate_ordersAggregate ordersPOSTAgents: ask firstAggregate orders by group-by fields, ideal for dashboards, charts, and analytics.
  • aggregate_tasksAggregate tasksPOSTAgents: ask firstAggregate tasks by group-by fields, ideal for dashboards, charts, and analytics. Use this endpoint to build task distribution charts, workload views, or priority breakdowns.

Created, 5 operations

  • list_created_contactsList created contactsGETAgents: ask firstRetrieve contacts created within a time window (default: last 4 hours). Returns contacts whose `created_ts` falls within the specified date range.
  • list_created_dealsList created dealsGETAgents: ask firstRetrieve deals/opportunities created within a time window (default: last 4 hours). Returns deals whose `timestamp` (creation time) falls within the specified date range.
  • list_created_invoicesList created invoicesGETAgents: ask firstRetrieve invoices created within a time window (default: last 4 hours). Returns invoices whose `timestamp` (creation time) falls within the specified date range.
  • list_created_leadsList created leadsGETAgents: ask firstRetrieve leads created within a time window (default: last 4 hours). Returns leads whose `created_ts` falls within the specified date range.
  • list_created_ordersList created ordersGETAgents: ask firstRetrieve orders created within a time window (default: last 4 hours). Returns orders whose `timestamp` (creation time) falls within the specified date range.

Appointment, 4 operations

  • create_appointmentCreate appointmentPOSTAgents: ask firstCreates an appointment. title and appt_date (epoch seconds) are required; duration defaults to 30 minutes and status to scheduled.
  • delete_appointmentDelete appointmentDELETEAgents: ask firstDeletes an appointment by id.
  • list_appointmentsList appointmentsGETAgents: ask firstLists appointments, optionally filtered by date range, user, type and outcome. Page with last_id.
  • update_appointmentUpdate appointmentPATCHAgents: ask firstUpdates an appointment by id. Send only the fields to change.

Lead, 4 operations

  • create_leadCreate leadPOSTAgents: ask firstCreate a new lead. Adds a lead record to the CRM. Only `name` is required; all other fields are optional.
  • list_leadsList leadsGETAgents: ask firstRetrieve leads with optional filtering, sorting, pagination, and date range. Returns a list of leads matching your criteria.
  • lookup_leads_by_sourceLookup leads by sourcePOSTAgents: ask firstLists leads from one marketing source (lead_source), with their pipeline journey. Paged with page_size and page_num.
  • update_leadUpdate leadPATCHAgents: ask firstUpdate an existing lead by ID. Send only the fields you want to change. Unset fields are left unchanged. Returns 400 if no fields are provided.

Task, 4 operations

  • create_taskCreate taskPOSTAgents: ask firstCreates a task. name is required; link it to a record with subject_type and subject, assign it with userid. status defaults to assigned and action to general.
  • delete_taskDelete taskDELETEAgents: ask firstPermanently deletes a task by id.
  • list_tasksList tasksGETAgents: ask firstRetrieve tasks with optional filtering, sorting, and pagination. Tasks represent actionable work items linked to CRM entities (leads, contacts, accounts, opportunities, etc.).
  • update_taskUpdate taskPATCHAgents: ask firstUpdates a task by id. Send only the fields to change.

Account, 3 operations

  • create_accountCreate accountPOSTAgents: ask firstCreate a new account (company/organization). Only `name` is required. Defaults: source="Unknown", status="customer", relationship_type="customer".
  • list_accountsList accountsGETAgents: ask firstRetrieve accounts (companies/organizations) with optional filtering, sorting, and pagination. Accounts represent business entities such as customers, vendors, or partners.
  • update_accountUpdate accountPATCHAgents: ask firstUpdate an existing account by ID. Send only the fields you want to change. Returns 400 if no fields are provided.

Contact, 3 operations

  • create_contactCreate contactPOSTAgents: ask firstCreate a new contact. Adds a contact record to the CRM. Only `name` is required; all other fields are optional.
  • list_contactsList contactsGETAgents: ask firstRetrieve contacts with optional filtering, sorting, pagination, and date range. Contacts are qualified individuals who have been converted from leads or added directly.
  • update_contactUpdate contactPATCHAgents: ask firstUpdate an existing contact by ID. Send only the fields you want to change. Unset fields are left unchanged. Returns 400 if no fields are provided.

Invoice, 3 operations

  • create_invoiceCreate invoicePOSTAgents: ask firstCreates an invoice for an account. invoice_num, account_id, total_amount and invoice_line_list are required; stage defaults to draft and invoice_type to sales.
  • list_invoicesList invoicesGETAgents: ask firstRetrieve invoices with optional filtering, sorting, pagination, and date range. Returns invoices matching your criteria.
  • update_invoiceUpdate invoicePATCHAgents: ask firstUpdate an existing invoice by ID. Send only the fields you want to change. Returns 400 if no fields are provided.

Order, 3 operations

  • create_orderCreate orderPOSTAgents: ask firstCreates a sales order or quote. account_id or contact_id is required; stage defaults to draft and order_type to sales.
  • list_ordersList ordersGETAgents: ask firstRetrieve orders with optional filtering, sorting, pagination, and date range. Returns orders matching your criteria.
  • update_orderUpdate orderPATCHAgents: ask firstUpdates an order by id. Send only the fields to change.

Updated, 3 operations

  • list_updated_dealsList updated dealsGETAgents: ask firstRetrieve deals/opportunities updated within a time window (default: last 4 hours). Returns deals whose `updated_ts` falls within the specified date range.
  • list_updated_invoicesList updated invoicesGETAgents: ask firstRetrieve invoices updated within a time window (default: last 4 hours). Returns invoices whose `updated_ts` falls within the specified date range.
  • list_updated_ordersList updated ordersGETAgents: ask firstRetrieve orders updated within a time window (default: last 4 hours). Returns orders whose `updated_ts` falls within the specified date range.

Deal, 2 operations

  • list_dealsList dealsGETAgents: ask firstRetrieve deals/opportunities with optional filtering, sorting, pagination, and date range. Deals (also called opportunities) represent potential revenue.
  • list_deals_reportList deals reportGETAgents: ask firstLists deals with report filters: date range, user_id and stage.

Opportunity, 2 operations

  • create_opportunityCreate opportunityPOSTAgents: ask firstCreate a new opportunity/deal. At least one of `account_id` or `contact_id` is required to link the deal to an existing account or contact.
  • update_opportunityUpdate opportunityPATCHAgents: ask firstUpdate an existing opportunity/deal by ID. Send only the fields you want to change. Returns 400 if no fields are provided.

Status updated, 2 operations

  • list_status_updated_contactsList status updated contactsGETAgents: ask firstRetrieve contacts whose status was updated within a time window (default: last 1 hour). Returns contacts where `status_update_date` falls within the specified range.
  • list_status_updated_leadsList status updated leadsGETAgents: ask firstRetrieve leads whose status was updated within a time window (default: last 1 hour). Returns leads where `status_update_date` falls within the specified range.

Agent goal, 1 operation

  • get_agent_goalsGet agent goalsGETAgents: ask firstPer-agent commission goal for a year, with the amount earned and progress toward the goal.

Comment, 1 operation

  • list_commentsList commentsGETAgents: ask firstLists the comments on one record: pass entity_type (lead, contact, account, order, invoice or opportunity) and entity_id.

Event, 1 operation

  • ingest_eventIngest eventPOSTAgents: ask firstIngests an event (event_type from list_event_types, e.g. lead.created) and routes it to the matching handler, which creates or updates the record in data. idempotency_key prevents duplicates.

Leaderboard, 1 operation

  • get_leaderboardGet leaderboardGETAgents: ask firstRanks agents by lead progression and win rate between start_date and end_date (ISO dates, inclusive).

Person, 1 operation

  • lookup_personLookup personPOSTAgents: ask firstSearch for a person by email, phone, internal ID, or external ID and retrieve their complete journey through the sales pipeline (lead → contact → opportunity).

Pipeline, 1 operation

  • get_deals_pipelineGet deals pipelineGETAgents: ask firstPer-stage summary of the deal pipeline between start_date and end_date (ISO dates, inclusive), for all agents or one user_id.

Timeline, 1 operation

  • get_deals_timelineGet deals timelinePOSTAgents: ask firstDeal count and total value bucketed by month or week between start_date and end_date, for all agents or one user_id.

Type, 1 operation

  • list_event_typesList event typesGETAgents: ask firstLists the event types ingest_event accepts.

User, 1 operation

  • list_usersList usersGETAgents: ask firstLists the users of the Ambivo account (the agents), with the ids other reports take as user_id.

Use Ambivo from Claude Code, Cursor or Codex

Connect Ambivo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ambivo operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ambivo

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Ambivo once

    Add your Ambivo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Ambivo integration FAQ

What can you do with the Ambivo integration?

LiveContext exposes 54 operations on Ambivo, covering aggregate, created, appointment and lead.

Popular integrations

Browse the whole catalog