BRIEF.

Outbound webhooks

BRIEF. POSTs JSON from your phone to URLs you save, so captured briefs flow into Zapier's 5,000+ app directory, Make, n8n, or your own API. Sends are intentional—nothing is dispatched from our servers—you tap send on OUT, Log, or Test POST under Webhooks.

Quick start

1. Paste your webhook URL under Tune → Webhooks.
2. Toggle Manual POST to show or hide the SEND action on your captured briefs.
3. Tap Test POST on the destination card and confirm the payload in your automation provider.

Up to five labeled destinations · optional Bearer secrets under Connection details · each delivery is tapped from the device · use HTTPS in production.

Connection details

Request headers

• Content-Type: application/json
• X-Brief-Webhook-Schema: 2
• Authorization: Bearer <secret>— only present when that destination's Bearer secret is set in the app

When to use each field

• architect — Structured briefs into databases or doc systems such as Notion or Airtable.
• assistant — Checkbox task surfaces for task trackers and reminders.
• ghostwriter — Ready-to-send messaging for Slack, email, or other short-form channels.
• meta — Content data — word counts and light tags derived from the outputs for filters without re-parsing slots.
• metadata — System data — timing and capture envelope (sentAt, duration, optional audio URI).
• schemaVersion and X-Brief-Webhook-Schema — Version gates if you ingest multiple payload shapes over time.

Payload (schema version 2)

Top-level architect, assistant, and ghostwriter strings are stable for field mapping across platforms.

Naming cheat sheet: meta is content data (stats from what you captured). metadata is system data (when the POST fired and recording context). Easiest mistake in integrations — treat them as unrelated objects.

The sample uses // comments to explain keys. Copy grabs valid JSON without those lines for Postman or schema tooling.

{
  // Which shape of payload this is — branch your parser on this or X-Brief-Webhook-Schema
  "schemaVersion": 2,
  // Markdown-style brief — good for databases and docs (Notion, Airtable, Notion-linked sheets)
  "architect": "string — Markdown brief",
  // Checkbox-style task lists — handy for todos and task tooling
  "assistant": "string — checkbox task surface",
  // Narrative prose you can paste into messages — email, Slack, DM tools
  "ghostwriter": "string — sendable prose",
  // Raw transcript fed into enrichment (often used for QA or archiving)
  "transcript": "string — raw transcript used for enrich",
  // Content data — word counts / tags derived from the outputs (not send timing)
  "meta": {
    "rawWordCount": 120,
    "wordCountBySlot": { "architect": 80, "assistant": 95, "ghostwriter": 110 },
    "combinedBriefWordCount": 285,
    "approxFillerHits": 6,
    "lexicalDiversity": 0.52,
    "repeatedWordHints": ["latency", "pilot"],
    "tags": ["Rich capture", "Briefs tightened"]
  },
  // System data — when/how this POST was emitted (milliseconds since Unix epoch where noted)
  "metadata": {
    "sentAt": 1735689600000,
    "durationMs": 12000,
    "audioUri": "file:///… or null"
  }
}

Setup and tips

1. Add or edit URLs under Tune → Webhooks (subscription required).
2. Optionally set a Bearer secret per destination — your stack should verify Authorization in middleware or Zapier routing rules when present.
3. Test POST is rate limited per destination so iterative wiring does not overwhelm your inbox or workflow runs.
4. Branch ingestion on schemaVersion when you onboard an older client or change mappings.

Platform recipes

Zapier

Add Webhooks by Zapier, choose Catch Hook (or webhook trigger), paste the hook URL into BRIEF., then tap Test POST or send from OUT. Map architect, assistant, and ghostwriter onto your next Zap steps.

Make

Create a Custom webhook module, copy the webhook URL into BRIEF., and fire a test POST. Inspect the bundle body fields and attach routers or filters downstream.

n8n

Add a Webhook node set to POST, activate the workflow, paste the webhook URL into BRIEF., then hit test or SEND to capture a sample execution.

Custom APIs

Verify optional Bearer secrets, validate JSON bodies, enqueue work, fan out notifications, log raw transcripts — mirror whatever compliance needs you enforce on ingress.

Maintainers — keep canonical payload prose in-repo at docs/WEBHOOK_RECIPES.md when schemas change ( bump BRIEF_WEBHOOK_SCHEMA_VERSION in the mobile app).