/agiled

name: agiled
description: |
  Agiled integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Agiled 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: ""

Agiled

Agiled is an all-in-one business management platform. It's used by small businesses and freelancers to manage projects, clients, invoices, and other business operations in one place.

Official docs: https://agiled.freshdesk.com/support/home

Agiled Overview

• **Task**
• **Comment**
• **Project**
• **Task**
• **Client**
• **User**
• **Time Entry**
• **Invoice**

Use action names and parameters as needed.

Working with Agiled

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

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

membrane connection ensure "https://agiled.app/" --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 Users | list-users | Get a list of all users | | List Products | list-products | Get a list of all products | | List Tickets | list-tickets | Get a list of all support tickets | | List Employees | list-employees | Get a list of all employees | | List Invoices | list-invoices | Get a list of all invoices | | List Projects | list-projects | Get a list of all projects | | List Tasks | list-tasks | Get a list of all tasks | | List Deals | list-deals | Get a list of all CRM deals | | List Accounts | list-accounts | Get a list of all accounts | | List Contacts | list-contacts | Get a list of all contacts | | Get Product | get-product | Get a specific product by ID | | Get Ticket | get-ticket | Get a specific ticket by ID | | Get Employee | get-employee | Get a specific employee by ID | | Get Invoice | get-invoice | Get a specific invoice by ID | | Get Project | get-project | Get a specific project by ID | | Get Task | get-task | Get a specific task by ID | | Get Deal | get-deal | Get a specific deal by ID | | Get Account | get-account | Get a specific account by ID | | Get Contact | get-contact | Get a specific contact by ID | | Create Invoice | create-invoice | Create a new invoice |

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

When the available actions don't cover your use case, you can send requests directly to the Agiled API through Membr