Insights
How the Insights hub reports revenue, quotes, receivables, margin, products, customers and stock from internal CentraKit data, with deterministic forecasts, rule-based insights and CSV or Excel exports.
Integrations
How the integrations marketplace connects WhatsApp Business inbox channels, Google Calendar and signed incoming and outgoing webhooks to an organization.
Insights
How the Insights hub reports revenue, quotes, receivables, margin, products, customers and stock from internal CentraKit data, with deterministic forecasts, rule-based insights and CSV or Excel exports.
Integrations
How the integrations marketplace connects WhatsApp Business inbox channels, Google Calendar and signed incoming and outgoing webhooks to an organization.
How lifecycles move quotes, invoices, tasks, orders, purchase orders and shipments through their stages, and how automations react to events, schedules and webhooks.
Workflows run work for you. A workflow is a graph of steps that starts from a trigger, such as an event, a schedule or a webhook, and runs in the background. Every run is recorded step by step, so you can see what happened and why.
| Route | Purpose |
|---|---|
/{orgSlug}/workflows | List of lifecycles and automations, with search and filters by status and type. |
/{orgSlug}/workflows/create | New workflow form. |
/{orgSlug}/workflows/{workflowId} | Editor tab with the canvas. |
/{orgSlug}/workflows/{workflowId}/details | Details tab with name, description and access. |
/{orgSlug}/workflows/{workflowId}/runs | Runs tab with the run history. |
/{orgSlug}/workflows/{workflowId}/runs/{runId} | One run with its graph, steps, input and output. |
A workflow has one of two purposes:
Platform workflows are marked System and Maintained by the platform. You cannot edit them directly. Select Duplicate to customize to make an organization copy; your copy replaces the platform version once you publish it. When the platform version changes later, the list shows Upstream updated and the editor offers View update. Nothing is merged automatically, so you compare and apply the changes you want.
You can also Turn off for this organization any platform automation you do not want, and Turn on for this organization to restore it.
Each lifecycle starts when its record reaches a starting event:
| Record | Starts on | Main stages |
|---|---|---|
| Quote | Quote sent | Sent, Viewed, Accepted, Invoiced. Also changes requested, deposit paid, rejected, withdrawn and expired. |
| Invoice | Invoice sent | Sent, Viewed, Paid. Also partially paid, overdue, final notice, in collection, cancelled and written off. |
| Task | Task created | In progress, Done. On hold is a flag. |
| Order | Order confirmed | Confirmed, Paid, Picking, Shipped or Ready for pickup, Delivered or Picked up, Invoiced, Completed. Backordered is a flag; Cancelled and Returned end the lifecycle. |
| Purchase order | Purchase order sent | Sent, Confirmed, In transit, Received, Billed. Partially received is a sub-stage, Overdue is a flag and Cancelled ends the lifecycle. |
| Shipment | Shipment shipped | In transit, Out for delivery or Ready for pickup, Delivered. Exception is a flag. |
The platform invoice lifecycle sends payment reminders 3 days before and 7 and 14 days after the due date, and a final notice 21 days after. The platform quote lifecycle reminds the customer and rejects a quote 30 days after it expires. Emails to customers go out only during business hours, 09:00 to 17:00 on weekdays.
A stage is shown as a main step, a sub-stage or a flag. Stages that end the lifecycle are marked Ends the lifecycle. Some stages advance on their own and others wait for a person.
A record uses the first lifecycle it finds in this order:
A running lifecycle can be paused, either indefinitely or until a date, with an optional reason. Delays and customer follow-ups wait while it is paused. Putting a task on hold pauses its lifecycle, and leaving hold resumes it.
Open a template in Content and choose its Workflow tab to connect it to workflows:
Starter automations are ready-made automations you add from a template:
| Starter | What it does |
|---|---|
| Big-ticket quote | Tells the team when a quote over 10,000 goes out. |
| Viewed, not accepted | Reminds the team to follow up when a quote was viewed but not decided in 3 days. |
| B2C 14-day letter | Sends individual customers the 14-day letter once an invoice is overdue. |
| Payment failed | Flags the invoice and alerts the team when an online payment fails. |
| Low stock reorder | Drafts a purchase order when stock runs low and sends it to the supplier. Runs for all products. |
| Purchase order overdue | Reminds the supplier and tells the purchaser when a purchase order is late. |
| Back in stock | Fills backorders when stock arrives and tells customers their order is complete. Runs for all orders. |
| Prepaid order to picking | Releases a prepaid order to picking as soon as it is paid. |
| Ready for pickup | Messages the customer when an order is ready for pickup, and reminds them after 7 days. |
| Delivered, then invoice | Invoices what was delivered and sends it, for orders invoiced on fulfillment. |
The platform also runs automations for every organization. Among them: confirming an accepted quote with a draft invoice and a follow-up task, notifying assignees when a task is assigned, due soon or overdue, following up on agenda items, welcoming new customers, flagging inbox conversations that are unanswered after 4 hours, weekly digests of overdue invoices and stale drafts, looking up customer details in the KvK register, VIES and on the web, reading product details from a photo, and alerting you when a workflow fails.
The editor palette groups steps as follows:
| Group | Steps |
|---|---|
| Triggers | Domain event, schedule, manual, workflow failed and webhook. |
| Flow | Condition, delay, merge, stage, clear flag and wait for event. |
| Actions | Send email, AI agent, call tool, HTTP request, webhook, approval and start workflow. |
| Domain actions | Record-specific steps such as rendering a PDF, sending a reminder, creating an invoice or order, notifying assignees or looking up a company. |
An approval step pauses the run until people decide. It can require any one approver, all approvers or a fixed order.
A workflow is Draft, Published or Archived. Only published workflows run, and only published workflows can be archived.
A run is Queued, Running, Waiting, Completed, Failed or Cancelled. Runs start from a trigger, by hand, from the API or MCP, or from a channel message.
If someone else changes the workflow at the same time, you can Keep my changes or Load server version.
To edit with the assistant, open the side panel on a workflow and describe the change. The assistant proposes graph changes that you review before they are applied.
On the Details tab, Access controls who can use the workflow. Automatic means anyone with workflow permissions in this organization can view and run it. Restricted means only the teams and users you grant.
The run detail page shows the graph, the list of steps with their status and attempts, and an inspector with the input and output of the selected step. When a run waits on an approval, approvers see Approve and Deny with an optional comment.
| Key | Grants |
|---|---|
organization.workflows.view | View workflows, runs and run status. |
organization.workflows.create | Create and duplicate workflows, and customize platform workflows. |
organization.workflows.update | Edit details, access and the graph, publish, archive, turn platform automations off or on and set the default lifecycle. |
organization.workflows.delete | Delete workflows and their run history. |
organization.workflows.run | Start manual and test runs, cancel runs and decide approvals. |
Adding a starter automation to a template also needs organization.templates.update. Platform administrators manage platform workflows with system.workflows.manage; see Admin workflows. See Access control for roles.
The assistant can read workflows and runs and start runs through the same tools as MCP:
| MCP tool | Access | Purpose |
|---|---|---|
listWorkflowDefinitions | Read | List workflows. |
getWorkflowDefinition | Read | Get one workflow with its graph. |
listWorkflowRuns | Read | List runs. |
getWorkflowRun | Read | Get one run with its steps. |
startWorkflowRun | Write | Start a run. |
Workflow steps count toward the workflow.steps usage meter. See Billing and usage.
Paths are relative to /api/v1/organizations/{organizationId}.
| Method | Path | Operation | Permission |
|---|---|---|---|
| GET | /workflows/definitions | listWorkflowDefinitions | organization.workflows.view |
| GET | /workflows/definitions/{definitionId} | getWorkflowDefinition | organization.workflows.view |
| POST | /workflows/definitions/{definitionId}/publish | publishWorkflowDefinition | organization.workflows.update |
| POST | /workflows/definitions/{definitionId}/runs | startWorkflowRun | organization.workflows.run |
| GET | /workflows/runs | listWorkflowRuns | organization.workflows.view |
| GET | /workflows/runs/{runId} | getWorkflowRun | organization.workflows.view |
| POST | /workflows/runs/{runId}/cancel | cancelWorkflowRun | organization.workflows.run |
| POST | /workflows/runs/{runId}/approval | decideWorkflowRunApproval | organization.workflows.run |
Tasks, quotes, invoices and orders also have GET .../lifecycle and POST .../lifecycle/advance routes on the record. Purchase orders and shipments do not have lifecycle routes yet.
Incoming webhooks start workflows from outside; see Integrations. See OpenAPI for schemas.
Last updated on
Insights
How the Insights hub reports revenue, quotes, receivables, margin, products, customers and stock from internal CentraKit data, with deterministic forecasts, rule-based insights and CSV or Excel exports.
Integrations
How the integrations marketplace connects WhatsApp Business inbox channels, Google Calendar and signed incoming and outgoing webhooks to an organization.
