Skip to content
Development
Skill

/accelo

Accelo integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Accelo data.

From plugin
application-skills
272200 skills

Claude Code

$ npx -y skills add membranedev/application-skills --skill accelo --agent claude-code

SKILL.md

accelo.SKILL.md
name: accelo
description: |
  Accelo integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Accelo 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, Project Management"

Accelo

Accelo is a business automation platform designed for service-based businesses. It helps manage clients, projects, sales, and billing in one integrated system. Professional services teams like IT, marketing, and consulting firms use it to streamline operations and improve profitability.

Official docs: https://developers.accelo.com/

Accelo Overview

  • **Company**
  • **Contact**
  • **Task**
  • **Project**
  • **Sale**
  • **Invoice**
  • **Ticket**
  • **Timesheet**
  • **Object**
  • **Attachment**
  • **Activity**
  • **Staff**
  • **Product**
  • **Purchase**
  • **Subscription**
  • **Leave Request**
  • **Bill**
  • **Credit**
  • **Queue**
  • **Custom Field**
  • **Email Template**
  • **Recurring Invoice**
  • **Material**
  • **Retainer**
  • **Order**
  • **Contract**
  • **Budget**
  • **Delivery**
  • **Asset**
  • **Build**
  • **Production Run**
  • **BOM**
  • **Transfer**
  • **Pick**
  • **Pack**
  • **Ship**
  • **Receive**
  • **Count**
  • **Adjustment**
  • **Work Order**
  • **RMA**
  • **Opportunity**
  • **Pay Run**
  • **Payment**
  • **Expense**
  • **Pay Item**
  • **Training**
  • **Group**
  • **Campaign**
  • **List**
  • **Landing Page**
  • **Form**
  • **Automation**
  • **Knowledge Base**
  • **Article**
  • **Forum**
  • **Topic**
  • **Reply**
  • **Survey**
  • **Question**
  • **Response**
  • **Location**
  • **Equipment**
  • **Booking**
  • **Checklist**
  • **Template**
  • **License**
  • **Integration**
  • **User**
  • **Role**
  • **Permission**
  • **Profile**
  • **Setting**
  • **Notification**
  • **Report**
  • **Dashboard**
  • **Widget**
  • **Filter**
  • **View**
  • **Layout**
  • **Theme**
  • **Language**
  • **Currency**
  • **Tax**
  • **Term**
  • **Unit**
  • **Category**
  • **Tag**
  • **Status**
  • **Priority**
  • **Type**
  • **Reason**
  • **Source**
  • **Stage**
  • **Resolution**
  • **SLA**
  • **Workflow**
  • **Trigger**
  • **Action**
  • **Condition**
  • **Event**
  • **Schedule**
  • **Log**
  • **Error**
  • **Backup**
  • **Restore**
  • **Import**
  • **Export**
  • **Merge**
  • **Clean**
  • **Archive**
  • **Delete**
  • **Test**
  • **Deploy**
  • **Upgrade**
  • **Monitor**
  • **Alert**
  • **Incident**
  • **Problem**
  • **Change**
  • **Release**
  • **Request**
  • **Service**
  • **Configuration**
  • **Inventory**
  • **Capacity**
  • **Demand**
  • **Forecast**
  • **Plan**
  • **Risk**
  • **Issue**
  • **Decision**
  • **Goal**
  • **Strategy**
  • **Policy**
  • **Procedure**
  • **Guideline**
  • **Standard**
  • **Framework**
  • **Model**
  • **Simulation**
  • **Analysis**
  • **Report**
  • **Dashboard**
  • **Widget**
  • **Filter**
  • **View**
  • **Layout**
  • **Theme**
  • **Language**
  • **Currency**
  • **Tax**
  • **Term**
  • **Unit**
  • **Category**
  • **Tag**
  • **Status**
  • **Priority**
  • **Type**
  • **Reason**
  • **Source**
  • **Stage**
  • **Resolution**
  • **SLA**
  • **Workflow**
  • **Trigger**
  • **Action**
  • **Condition**
  • **Event**
  • **Schedule**
  • **Log**
  • **Error**
  • **Backup**
  • **Restore**
  • **Import**
  • **Export**
  • **Merge**
  • **Clean**
  • **Archive**
  • **Delete**
  • **Test**
  • **Deploy**
  • **Upgrade**
  • **Monitor**
  • **Alert**
  • **Incident**
  • **Problem**
  • **Change**
  • **Release**
  • **Request**
  • **Service**
  • **Configuration**
  • **Inventory**
  • **Capacity**
  • **Demand**
  • **Forecast**
  • **Plan**
  • **Risk**
  • **Issue**
  • **Decision**
  • **Goal**
  • **Strategy**
  • **Policy**
  • **Procedure**
  • **Guideline**
  • **Standard**
  • **Framework**
  • **Model**
  • **Simulation**
  • **Analysis**

Working with Accelo

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

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

membrane connection ensure "https://www.accelo.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 authen
Read more

Stars on GitHub

Momentum

stars in total
272
Star history of membranedev/application-skills on GitHub, a chart by star-history.com

Other skills on application-skills.

1c

1c

1C-Bitrix integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1C-Bitrix data.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about accelo.

Which coding agents can use accelo?
accelo installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.