KosmoKrator

productivity

Accelo CLI for AI Agents

Use the Accelo CLI from KosmoKrator to call Accelo tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Accelo CLI Setup

Accelo can be configured headlessly with `kosmokrator integrations:configure accelo`.

Install, configure, and verify 
# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure accelo --set access_token="$ACCELO_ACCESS_TOKEN" --set deployment="$ACCELO_DEPLOYMENT" --enable --read allow --write ask --json
kosmokrator integrations:doctor accelo --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

KeyEnv varTypeRequiredLabel
access_token ACCELO_ACCESS_TOKEN Secret secret yes Access Token
deployment ACCELO_DEPLOYMENT Text string yes Deployment Name
url ACCELO_URL URL url no Custom Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call 
kosmo integrations:call accelo.accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json
Provider shortcut 
kosmo integrations:accelo accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands 
kosmo integrations:docs accelo --json
kosmo integrations:docs accelo.accelo_list_tickets --json
kosmo integrations:schema accelo.accelo_list_tickets --json
kosmo integrations:search "Accelo" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

accelo.accelo_list_tickets

List support issues, also known as tickets, in Accelo. Returns a paginated list optionally filtered by standing.

Read read
Parameters
limit, page, status
Generic call 
kosmo integrations:call accelo.accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json
Shortcut 
kosmo integrations:accelo accelo_list_tickets '{"limit":1,"page":1,"status":"example_status"}' --json

accelo.accelo_get_ticket

Get details of a specific support issue, also known as a ticket, in Accelo by its ID.

Read read
Parameters
id
Generic call 
kosmo integrations:call accelo.accelo_get_ticket '{"id":1}' --json
Shortcut 
kosmo integrations:accelo accelo_get_ticket '{"id":1}' --json

accelo.accelo_create_ticket

Create a new support issue, also known as a ticket, in Accelo. Requires a title and body. Optionally associate with a contract and set priority.

Write write
Parameters
title, body, contract_id, priority
Generic call 
kosmo integrations:call accelo.accelo_create_ticket '{"title":"example_title","body":"example_body","contract_id":1,"priority":1}' --json
Shortcut 
kosmo integrations:accelo accelo_create_ticket '{"title":"example_title","body":"example_body","contract_id":1,"priority":1}' --json

accelo.accelo_list_tasks

List tasks in Accelo. Returns a paginated list of tasks, optionally filtered by standing.

Read read
Parameters
limit, page, status
Generic call 
kosmo integrations:call accelo.accelo_list_tasks '{"limit":1,"page":1,"status":"example_status"}' --json
Shortcut 
kosmo integrations:accelo accelo_list_tasks '{"limit":1,"page":1,"status":"example_status"}' --json

accelo.accelo_get_task

Get details of a specific task in Accelo by its ID.

Read read
Parameters
id
Generic call 
kosmo integrations:call accelo.accelo_get_task '{"id":1}' --json
Shortcut 
kosmo integrations:accelo accelo_get_task '{"id":1}' --json

accelo.accelo_list_projects

List projects in Accelo. Accelo exposes these records through the jobs API resource.

Read read
Parameters
limit, page, status
Generic call 
kosmo integrations:call accelo.accelo_list_projects '{"limit":1,"page":1,"status":"example_status"}' --json
Shortcut 
kosmo integrations:accelo accelo_list_projects '{"limit":1,"page":1,"status":"example_status"}' --json

accelo.accelo_get_current_user

Get token information for the current Accelo access token, including user email and expiry details.

Read read
Parameters
none
Generic call 
kosmo integrations:call accelo.accelo_get_current_user '{}' --json
Shortcut 
kosmo integrations:accelo accelo_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

accelo.accelo_list_tickets 3 parameters
Schema command 
kosmo integrations:schema accelo.accelo_list_tickets --json
ParameterTypeRequiredDescription
limit integer no Number of tickets to return per page (default: 25, max: 100).
page integer no Page number for pagination (1-based).
status string no Filter issues by standing (e.g. "open", "closed", "resolved").
accelo.accelo_get_ticket 1 parameters
Schema command 
kosmo integrations:schema accelo.accelo_get_ticket --json
ParameterTypeRequiredDescription
id integer yes The Accelo ticket ID.
accelo.accelo_create_ticket 4 parameters
Schema command 
kosmo integrations:schema accelo.accelo_create_ticket --json
ParameterTypeRequiredDescription
title string yes The ticket title or subject.
body string yes The ticket description or body content.
contract_id integer no Optional contract ID to associate with the ticket.
priority integer no Issue priority ID.
accelo.accelo_list_tasks 3 parameters
Schema command 
kosmo integrations:schema accelo.accelo_list_tasks --json
ParameterTypeRequiredDescription
limit integer no Number of tasks to return per page (default: 25, max: 100).
page integer no Page number for pagination (1-based).
status string no Filter tasks by standing (e.g. "active", "inactive", "completed").
accelo.accelo_get_task 1 parameters
Schema command 
kosmo integrations:schema accelo.accelo_get_task --json
ParameterTypeRequiredDescription
id integer yes The Accelo task ID.
accelo.accelo_list_projects 3 parameters
Schema command 
kosmo integrations:schema accelo.accelo_list_projects --json
ParameterTypeRequiredDescription
limit integer no Number of projects to return per page (default: 25, max: 100).
page integer no Page number for pagination (1-based).
status string no Filter jobs by standing (e.g. "active", "inactive", "completed").
accelo.accelo_get_current_user 0 parameters
Schema command 
kosmo integrations:schema accelo.accelo_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.