Skip to content
Content Rabbit

Quick summary: Generate a Team API key in Settings → Team → API Key, then paste it into the Content Rabbit Zapier app using the API Key authentication option.

Requirements

  • Content Rabbit account with access to the team you want to automate
  • API key generated for that team
  • Zapier account (any plan that supports the Zapier CLI or custom apps)
  • Node.js 18+ if you plan to work with the Zapier CLI locally

Generate a Team API Key

  1. Open Settings → Team.
  2. Pick the team you want to automate.
  3. Switch to the API Key tab.
  4. Click Generate API key and copy the value immediately. Rotate it if you lose the key later.
  5. Note the Team ID (visible in the URL). You will use it in the Zapier auth fields.

Add the Content Rabbit Zap (UI)

  1. Search for Content Rabbit inside Zapier and add the app to your Zap.
  2. When prompted for authentication, choose the API Key auth method.
  3. Paste the Team API key and the Team ID.
  4. Save the connection and continue configuring your Zap.

Zapier CLI Setup (optional)

If you prefer working with the Zapier CLI:

npm install -g zapier-platform-cli
zapier login

Initialize a local app:

zapier init content-rabbit-automation --template=typescript

Replace the generated files with the ones in integrations/zapier/ from this repository (they already include API key auth and starter trigger/action stubs). Finally, push the app:

zapier push

Available Triggers & Actions

  • Trigger: New or Updated Draft
    • Polls /v1/drafts with the Team API key.
    • Supports updatedSince so only new or changed drafts run the Zap.
  • Action: Create Draft
    • Calls POST /v1/drafts with content, status, schedule, and media IDs.

You can extend this CLI app with additional triggers or actions (for example, publishing a scheduled draft) by adding new files to the integrations/zapier directory and pushing a new version.

Testing & Troubleshooting

  • 401 Unauthorized → Confirm you pasted the correct API key and Team ID. API keys are scoped per team.
  • 404 Draft Not Found → The draft moved or was deleted between polls; the trigger will automatically recover on the next run.
  • Rate limit headers → Requests return X-RateLimit-* headers; back off if you see a 429 response.
  • Rotate keys regularly → If a key is compromised, rotate it in the API Key panel and update the Zapier connection.
Was this helpful?