Accelo
Work with Accelo PSA: companies, contacts, activities and time, tasks, jobs, issues, requests, prospects, invoices and staff.
About
Accelo ships in the w6w first-party pack. It declares 34 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.accelo- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Project Management · Customer Relationship Management · Productivity
Overview
Accelo is a professional services automation (PSA) platform that runs client work from first request to final invoice: prospects and quotes, projects (jobs) and their tasks, ongoing retainers, support issues, time tracking and billing, all tied to the companies and contacts they belong to.
This app lets a workflow read and write the core of that record: create and update companies and contacts, log notes, calls and meetings (and billable time) against any object, open and update tasks, jobs and issues, capture inbound requests, move prospects through the pipeline, and read invoices and staff.
Every Accelo customer has its own API host, so a connection records the deployment it belongs to and the app only ever calls that account’s own subdomain. It authenticates as a Service Application using OAuth 2 client credentials, so it runs in scheduled and background workflows with no browser sign-in. Health checks track Accelo’s status page, this account’s host, and the hourly request allowance.
Build with Accelo
Three routes to the same 34 actions. The Workflow tab is generated from Accelo's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Activity
activity-create Log a note, call, meeting or email against an object, optionally with billable time. File it against a task to log time on that task.
List Activities
activity-list List activities (notes, calls, meetings, emails). Filter by owner, what they are against, or date; e.g. `against_type(job)`, `date_created_after(1490140800)`.
List Companies
company-list List companies. Search covers name, website, phone and fax; filters include `standing`, `manager_id`, `custom_id` and `date_created`.
Update Company
company-update Change a company's name, website, phone, fax or comments. Unset fields are left alone.
Create Contact
contact-create Create a contact and, in the same call, its affiliation with a company (company id, phone, email, position).
Update Contact
contact-update Change a contact's name, title, comments or standing. Phone, email and address belong to the affiliation, not the contact.
Update Issue
issue-update Change an issue's title, assignee, priority, status or resolution. Unset fields are left alone.
Update Job
job-update Change a job's title, manager, status, contract or due date. Unset fields are left alone.
Update Prospect
prospect-update Change a prospect's title, value, owner or progress. Unset fields are left alone.
Create Request
request-create Log an inbound client request. Pass an affiliation id, or let Accelo match or create one from the name, company and email.
Create Task
task-create Create a task against an object (typically a job, milestone, issue or company).
Update Task
task-update Change a task's title, description, people, priority or dates. Unset fields are left alone.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Accelo's real ids.
{
"manifestVersion": "2",
"name": "accelo-example",
"steps": [
{
"id": "activity-create",
"uses": {
"app": "io.w6w.accelo",
"action": "activity-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"subject": "<subject>",
"againstType": "<againstType>",
"againstId": "<againstId>"
}
}
]
}Here are some of the things you can do
-
Create Activity
performactivity-create -
Get Activity
readactivity-get -
List Activities
readactivity-list -
Create Company
performcompany-create -
Get Company
readcompany-get
+29 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Accelo, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Accelo. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "activity-create",
payload: {
subject: "<value>",
// body: "<value>",
againstType: "<value>",
againstId: "<value>",
// medium: "<value>",
// details: "<value>",
// priorityId: "<value>",
// classId: "<value>",
// taskId: "<value>",
// ownerType: "<value>",
// ownerId: "<value>",
// dateStarted: "<value>",
// dateEnded: "<value>",
// billable: "<value>",
// nonbillable: "<value>",
// fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action activity-create --payload '{"subject":"<value>","againstType":"<value>","againstId":"<value>"}'Give an AI agent Accelo — without giving it Accelo's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.accelo#activity-create",
"input": {
"subject": "<subject>",
"againstType": "<againstType>",
"againstId": "<againstId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Accelo connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Accelo's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Accelo itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Accelo declares its own checks, so its health is a property of the app rather than something the host guesses at.
Accelo platform status
Atlassian Statuspage rollup for status.accelo.com. Page-level only: Accelo publishes no per-component state, so this is informational. Unauthenticated and unsigned.
Deployment host reachable
Unauthenticated request to this connection's Accelo deployment. A 401 passes — it proves the host is serving; credential validity is the `auth:*` check's job.
API rate-limit headroom
Requests remaining in this deployment's hourly window (5000/hour), read off the `X-RateLimit-*` headers.