Agile CRM integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Agile CRM data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agile-crm75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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/
Use action names and parameters as needed.
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 Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/climembrane login --tenantA browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search agile-crm --elementType=connector --jsonoutput.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --jsonWhen you are not sure if connection already exists:
membrane connection list --jsonconnectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --jsonThis will return action objects with id and inputSchema in it, so you will know how to run it.
| 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 |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --jsonTo pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"When the available actions don't cover your use case, you can send requests directly to the Agile CRM API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpointCommon options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.d19a82b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.