Automation tools

Zapier, Make, n8n and similar tools connect to AUGMTD in both directions with plain webhooks. Both are set up by an owner or admin of a company workspace in Settings → Connections. No code on either side.

From AUGMTD to your automation

1. In your automation tool, start a flow with its "catch a webhook" trigger (each tool has one) and copy the address it gives you.
2. In AUGMTD, open Settings → Connections → Send to your tools, choose A link to your tool, paste the address and pick what to send. The presets are a starting point: Client activity (emails with clients, promises made and kept, meetings held) and Promises and approvals (every change to promises, approvals and process runs).
3. Keep the whsec_… secret shown once. A code step in your flow can check the signature (see Use it from your own app); a flow that cannot should at least ignore a repeated webhook-id.
4. Each member decides whether their own email and meetings count. Until they do, nothing of theirs is sent.

A tool that prefers to poll can use A feed your tool reads instead: an HTTP step calls GET https://app.augmtd.ai/api/record/feed with the feed's token and keeps the cursor.

To read a person's work or propose a step from a flow (rather than receive changes), call the REST API with that person's key: for example GET https://app.augmtd.ai/api/v1/promises?status=open.

From your automation to AUGMTD

When something happens in another tool (a task closed, a deliverable sent, an invoice paid), your flow can tell AUGMTD, so the record knows where the work stands.

1. In AUGMTD, open Settings → Connections → Receive from your tools and add a source. The Automation tool preset expects a small JSON body:

{ "event": "deliverable.sent", "when": "2026-10-23T09:00:00Z", "augmtd_id": "<promise id>",
  "client_email": "sam@acme.example", "record_id": "R-7", "stage": "Sent" }

2. AUGMTD shows the source's own address, https://app.augmtd.ai/api/record/in/<source id>, and its whsec_… secret (once).
3. Your flow posts to that address, signed the Standard Webhooks way (webhook-id, webhook-timestamp, webhook-signature), within five minutes of the timestamp. Each event is taken once, by its id. A body is at most 64 KB.

The kinds of update a source may send: case.moved, task.done, deliverable.sent, invoice.sent, invoice.paid, meeting.held, touch.logged, stage.changed, work.updated. The Generic JSON and Task tool webhook presets map other shapes; every mapping is data you can edit.

What an update does

An update is evidence, never a decision. It is matched to open work (by our id, by the client's address or domain, never a free email address, or by your tool's own id once learned) and may put a card in front of a person: "Task closed in the project tool: mark the promise to Acme kept?". Nothing closes until they confirm. A source the admin allows to start a process starts a run that only prepares: it waits at its first approval, within a daily limit.

Every accepted or refused update is in the admin's activity. A source that keeps failing its mapping is paused, and the admin gets a card.