Automation recipes: n8n, Make & Zapier

All three tools talk to Clapr through the plain REST API — no custom app or plugin needed. Cards your workflows create land in the first board column with an Agent badge, so your team reviews everything before it ships.

One-time setup (all tools)

• Generate a token in Clapr → Settings → API & AI tools (looks like clapr_mcp_…).
• Every request needs the header Authorization: Bearer clapr_mcp_… and the base URL https://www.clapr.io/api/v1.
• Test the credential with GET /me — it returns your user id and workspaces. Copy the workspace_idyou want to write to; you'll need it for creating cards.

n8n

Fastest start — import the ready-made template: clapr-n8n-auto-draft-ideas.json (in n8n: Workflows → Import from File, or paste https://www.clapr.io/templates/clapr-n8n-auto-draft-ideas.json into Import from URL). It contains the full weekly pipeline below plus a sticky note with the two things to fill in: your Header-Auth credential and your workspace_id.

Building it manually instead: create a credential of type Header Auth (Name: Authorization, Value: Bearer clapr_mcp_…), then use the standard HTTP Request node.

Recipe — auto-draft video ideas every Monday: Schedule Trigger (Mon 08:00) → your research step (RSS Read, HTTP scrape, or an AI node that drafts titles + hooks) → HTTP Request:

Method: POST
URL: https://www.clapr.io/api/v1/cards
Authentication: Header Auth (your Clapr credential)
Body Content Type: JSON
Body:
{
  "workspace_id": "YOUR_WORKSPACE_ID",
  "title": "{{ $json.title }}",
  "description": "Hook: {{ $json.hook }}",
  "scheduled_date": "{{ $json.targetDate }}"
}

The response is { "id": "…", "created": true } — use the id in follow-up nodes, e.g. POST /cards/{id}/references to attach the source article.

Make

Use the HTTP → Make a request module (the generic one; no Clapr app required):

URL: https://www.clapr.io/api/v1/cards
Method: POST
Headers:
  Authorization: Bearer clapr_mcp_…
  Content-Type: application/json
Body type: Raw · JSON
Request content:
{
  "workspace_id": "YOUR_WORKSPACE_ID",
  "title": "{{title}}",
  "description": "{{hook}}"
}

Recipe — ideas from a spreadsheet: Google Sheets “Watch New Rows” → HTTP request as above. Every row your team (or an AI scenario) adds becomes a reviewable card.

Zapier

Use Webhooks by Zapier as the action step (available on paid Zapier plans), action event Custom Request:

Method: POST
URL: https://www.clapr.io/api/v1/cards
Data (JSON):
{
  "workspace_id": "YOUR_WORKSPACE_ID",
  "title": "New idea from form",
  "description": "Submitted via Typeform"
}
Headers:
  Authorization: Bearer clapr_mcp_…
  Content-Type: application/json

Recipe — capture from anywhere: Trigger on a new Typeform submission, a starred Slack message, or a note in Notion → the card shows up in your Idea column, badged for review.

Recipe: weekly performance report

Works the same in all three tools — three HTTP steps on a weekly schedule:

• GET /cards?workspace_id=…&limit=200 and keep the ones with a published_url.
• For each: GET /cards/{id}/performance → latest holds views, likes, comments.
• Sort by views and post the top 5 to Slack, email or your dashboard.

Good to know

• Rate limit: 120 requests/minute per token — batch runs should add a small delay between items (all three tools have a built-in option).
• Avoid duplicates: GET /cards?workspace_id=… first and skip titles that already exist, or dedupe in your workflow before posting.
• Writes need the owner or editor role; a viewer token can read and comment but not create cards.
• Full endpoint and error reference: REST API docs · machine-readable spec at /api/v1/openapi.json.