/agile-crm

name: agile-crm
description: |
  Agile CRM integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Agile CRM 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: "CRM, Sales"

Agile CRM

Agile CRM is a customer relationship management platform used by sales and marketing teams. It helps businesses manage contacts, track deals, automate marketing, and provide customer support.

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

Agile CRM Overview

• **Contact**
• **Company**
• **Deal**
• **Task**
• **Case**
• **Email**
• **Campaign**
• **Automation**
• **Report**
• **User**
• **Tag**

Use action names and parameters as needed.

Working with Agile CRM

This skill uses the Membrane CLI to interact with Agile CRM. 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 Agile CRM

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

membrane connection ensure "https://www.agilecrm.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 Contacts | list-contacts | Retrieve a paginated list of contacts | | List Companies | list-companies | Retrieve a paginated list of companies | | List Deals | list-deals | Retrieve a paginated list of deals | | List Tasks | list-tasks | Retrieve a list of tasks with optional filters | | Get Contact by ID | get-contact-by-id | Retrieve a contact by its unique ID | | Get Company by ID | get-company-by-id | Retrieve a company by its unique ID | | Get Deal by ID | get-deal-by-id | Retrieve a deal by its unique ID | | Get Task by ID | get-task-by-id | Retrieve a task by its unique ID | | Create Contact | create-contact | Create a new contact in Agile CRM | | Create Company | create-company | Create a new company in Agile CRM | | Create Deal | create-deal | Create a new deal in Agile CRM | | Create Task | create-task | Create a new task in Agile CRM | | Update Contact | update-contact | Update properties of an existing contact by ID | | Update Company | update-company | Update properties of an existing company by ID | | Update Deal | update-deal | Update an existing deal by ID | | Update Task | update-task | Update an existing task by ID | | Delete Contact | delete-contact | Delete a contact by ID | | Delete Company | delete-company | Delete a company by ID | | Delete Deal | delete-deal | Delete a deal by ID | | Delete Task | delete-task | Delete a task by ID |

Running actions

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

To pass JSON parameters:

membrane action run <actionId> --conne