Integration docs.
Signed webhook events, the read-only MCP tools and every export format, with the plan each needs.
Outbound events · Team plan
Webhooks for Power Automate, Zapier or n8n.
A master adds an address on the Resources page (Agents and automations), picks the events, and copies the signing secret, which is shown once. Entrilla then posts a small JSON body to that address each time one of the five events happens. The automation lives in your tool.
| Event | When | Fields besides event, at and org_id |
|---|---|---|
| workflow_created | A process was added, or a draft was shared | workflow_id, workflow (its name), department, draft |
| analysis_run | An analysis finished | workflow_id, findings and recommendations (how many of each) |
| proposal_adopted | A proposed change became the current process | workflow_id, workflow, proposal (its name) |
| card_in_build | A build board card moved to In build | card_id, title, workflow_id, chosen_play |
| fill_answered | Someone answered a fill-in question | workflow_id, step_id, fact (who or system), detail |
The request
POST <your address>
Content-Type: application/json
User-Agent: Entrilla-Webhook/1
X-Entrilla-Signature: sha256=<hex HMAC-SHA256 of the raw body, keyed with the signing secret>
{"event":"analysis_run","at":"2026-10-23T01:02:03.000Z","org_id":1,"workflow_id":42,"findings":3,"recommendations":5}Checking the signature
// Node.js: compare before you parse the body.
const crypto = require("crypto");
const expected = "sha256=" + crypto.createHmac("sha256", SIGNING_SECRET).update(rawBody).digest("hex");
const ok = expected.length === signature.length &&
crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));- Addresses must be https and public; a private or internal address is refused, and redirects are never followed.
- Each event is posted once, with an 8-second timeout. The answer (or the error) is shown beside the address.
- The Resources page sends a test event: workflow_created with test: true and workflow_id 0.
- A draft is never announced until it is shared. Events stop if the organisation leaves the Team plan, and an address stops when the master who added it leaves.
MCP · Team plan
Let Claude, Copilot or Cursor read your maps.
Nine read-only tools over MCP. Nothing can be edited through them, hourly rates and dollar figures are kept out, and a key sees only its own organisation. A master makes the key on the Resources page; it is shown once and only its hash is stored.
claude mcp add --transport http entrilla https://<your workspace>/api/mcp \
--header "Authorization: Bearer ent_…"| Tool | What it returns |
|---|---|
| list_workflows | Every mapped process: id, name, department, how often it runs, step count and hands-on minutes per run. Optional department filter. |
| get_workflow | One process in full: its steps (who, system, minutes, people, friction, confirmation), the connections between steps with any waits, and open notes. |
| get_summary | One process's Summary: hands-on time per run, steps, people, the recommendations by status with the minutes each frees, and what each needs. |
| list_recommendations | Every recommendation across the organisation, a year at a time: department, status, effort, minutes freed per run and per year, and what it needs. Filters: workflow_id, status, department. |
| list_themes | The cross-process themes from the last organisation review: what to build once, the processes behind it and what it waits on. |
| get_shelf | Your tool shelf: each item, its state (have, incoming, chasing, parked, not available) and when it is expected. |
| get_rules | The plain-English rules you have set for the AI, for the whole organisation or a department. |
| list_build_board | The build board: each card's status, the chosen play, and the three plays (Now, 80/20, Ideal) with what each needs. |
| search | Search processes, steps and friction notes for a word or phrase. Returns process ids and step numbers for get_workflow. |
- Streamable HTTP, stateless: POST JSON-RPC, get one JSON reply. A batch holds at most 20 calls.
- Each key gets 600 calls an hour. Drafts and proposed versions are left out.
- A key stops working when the master who made it leaves or is no longer a master.
Exports
Everything comes out.
| Export | What is in it | Plan |
|---|---|---|
| Everything, one ZIP (entrilla-export/1) | Every process (JSON and Markdown, with its versions), attachments, departments, the tool shelf, the build board, analyses, rules, written procedures, people (users.csv) and the activity log (activity.csv), with README.md, FORMAT.md and manifest.json | Every plan; masters and admins, because it carries pay rates |
| BPMN 2.0 | One process: lanes, branches, minutes and pain notes, for any tool that reads BPMN 2.0 | Every plan |
| PowerPoint | One process's Summary: the map, the win and the biggest fixes | Every plan |
| Markdown | One process's figures, fixes and step table, ready to paste into Confluence | Every plan |
| Print or PDF | The whole map on A4, A3 or one long sheet, and the written procedure, from your browser | Every plan |
| Savings review and board pack | The organisation-wide list as a spreadsheet, a one-page print and the whole-organisation CFO report | Team plan |
- Text is UTF-8. CSV files start with a byte-order mark and use CRLF line ends, and a cell that starts like a formula gets a ' in front, so a spreadsheet keeps it as text.
- All times are UTC. Ids connect the files: a step's workflow_id is the number at the start of its process's file name.
- Each full export adds a line to the activity log. Dollar figures appear in an export only for the people who can see pay rates; everyone else gets hours.
Prove the procedure is followedFor IT and automation leadsSecurity answers