/ambivo

name: ambivo
description: |
  Ambivo integration. Manage Organizations, Pipelines, Users, Filters, Activities, Notes and more. Use when the user wants to interact with Ambivo data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

Ambivo

Ambivo is a customer data platform (CDP) that helps businesses unify and activate their customer data. It's used by marketing, sales, and customer service teams to personalize customer experiences and improve engagement.

Official docs: https://www.ambivo.com/docs

Ambivo Overview

• **Project**
• **Document**
• **User**
• **Template**

Use action names and parameters as needed.

Working with Ambivo

This skill uses the Membrane CLI to interact with Ambivo. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Ambivo

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://www.ambivo.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Orders | list-orders | Retrieve a list of orders from Ambivo | | List Invoices | list-invoices | Retrieve a list of invoices from Ambivo | | List Deals | list-deals | Retrieve a list of deals from Ambivo | | List Contacts | list-contacts | Retrieve a list of contacts from Ambivo | | List Leads | list-leads | Retrieve a list of leads from Ambivo | | Get Order | get-order | Retrieve a specific order by ID | | Get Invoice | get-invoice | Retrieve a specific invoice by ID | | Get Deal | get-deal | Retrieve a specific deal by ID | | Get Contact | get-contact | Retrieve a specific contact by ID | | Get Lead | get-lead | Retrieve a specific lead by ID | | Create Order | create-order | Create a new order in Ambivo | | Create Invoice | create-invoice | Create a new invoice in Ambivo | | Create Deal | create-deal | Create a new deal in Ambivo | | Create Contact | create-contact | Create a new contact in Ambivo | | Create Lead | create-lead | Create a new lead in Ambivo | | Update Order | update-order | Update an existing order in Ambivo | | Update Invoice | update-invoice | Update an existing invoice in Ambivo | | Update Deal | update-deal | Update an existing deal in Ambivo | | Update Contact | update-contact | Update an existing contact in Ambivo | | Update Lead | update-lead | Update an existing lead in Ambivo |

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the `output` field of the response.

Proxy requests

Whe