Apps for AI agents

Zapier & Make automation

Ounie is a step, not a destination. Point a Zap or a scenario at a brain and content flows in from whatever you already use — then ask that same brain a question mid-workflow and get a cited answer back into the next step.

https://zapier.com/apps/ounie/integrations

Actions#

Both integrations expose the same two actions, backed by the v1 REST API. They are the two wires leaving the workflow at the top of this page — save out to the brain, answer back from it.

Add source to brain#

Choose a brain from a dropdown populated live from your account, then provide either a URL (Ounie fetches and synthesizes the page) or a title and text body. Set Text mode to Note to store text verbatim without LLM processing. Link body:

{
  "kind": "link",
  "url": "https://example.com/article",
  "externalId": "article-42"
}

Text body:

{
  "kind": "text",
  "title": "Meeting notes 2026-06-12",
  "content": "…",
  "mode": "synthesize",
  "externalId": "meeting-2026-06-12"
}

The action returns the source record plus a created flag. When created is false the source already existed (idempotent replay — see External ID):

{
  "source": {
    "id": "src_01abc",
    "type": "link",
    "title": "Getting Started with Ounie",
    "status": "pending",
    "externalId": "article-42"
  },
  "created": false
}

Ask brain#

Asks a grounded question against a brain and returns an answer with inline citations. Choose a brain from the dropdown and type or map a question:

{
  "question": "What did we decide about the Q3 roadmap?"
}

{
  "id": "ask_01abc",
  "answer": "The Q3 roadmap focuses on [API expansion](https://ounie.com/b/ada/ai/api-expansion).",
  "citations": [
    {
      "slug": "api-expansion",
      "title": "API expansion",
      "url": "https://ounie.com/b/ada/ai/api-expansion"
    }
  ],
  "thin": false
}

The answer field contains markdown with citations rewritten to absolute links. The citations array carries the same links as structured data. When the brain has too few sources to answer confidently, thin is true — worth branching on, so a scheduled digest never mails out an answer the brain could not support.

The Free plan draws a one-time, non-expiring bank of questions; paid plans draw a rolling 30-day quota sized by the plan. Current figures live on the pricing page rather than here, so this page can never quote a stale number at you. Notes and links carry no storage cost, so a text-only automation never moves you toward the storage cap.

// 402 — question bank empty (Free plan)
{ "error": "bank_empty", "code": "BANK_EMPTY" }

// 429 — monthly quota exceeded (paid plan)
{ "error": "quota_exceeded", "code": "QUOTA_EXCEEDED" }

// 403 — plan source limit reached
{ "error": "Source limit reached", "code": "SOURCE_LIMIT" }

In Zapier these surface as task errors carrying the message above. In Make, the typed errors let you add a separate error-handler route per status code — one that pauses the scenario on 429 and one that alerts you on 401 are the two worth wiring first.

Example automations#

Six shapes worth stealing. The ones that create a source name the External ID that makes them safe to re-run; the ones that only ask do not need one, because nothing is created.