[APP] Content Rabbit

**Name of app / service**

Content Rabbit — https://contentrabbitai.com

Content Rabbit is a social media scheduling and publishing platform. It manages posts across Twitter/X, LinkedIn, Instagram, Threads, Bluesky, Mastodon, TikTok, Pinterest, Discord, Slack, WordPress, Dev.to and others from one place, with scheduling, a media library, and per-platform analytics.

**Link to developer documentation**

https://contentrabbitai.com/docs/api

The public REST API lives under `/api/public/v1`. Auth is a single team API key sent as `Authorization: Bearer `, which maps cleanly onto a Pipedream key-based app.

**Is lack of support preventing you from moving forward, or do you have a workaround?**

The workaround today is a custom-code step calling the REST API directly, which means every user rebuilds the same auth and pagination handling by hand.

I maintain Content Rabbit and have already written the components — 17 actions and 3 sources — against `@pipedream/platform`. They follow the registry guidelines: `contentrabbit-` prefixed keys, shared `propDefinitions` on the app file with `async options()` for post, account and media pickers, and pagination via `page`.

I'm opening this request because the contributing guide says a new app has to be integrated by Pipedream first, so the `components/contentrabbit/` scaffolding and auth definition exist before component PRs land. Happy to open the PR the moment the app record is created — the code is ready.

**Are there specific actions or triggers you'd like to see for this app?**

These are the ones already written and ready to submit.

Actions:
- Create Post, Update Post, Get Post, Delete Post, List Posts
- Schedule Post, Unschedule Post, Publish Post
- Upload Media, Register Image, Attach Media, List Media
- List Accounts, List Teams, List Activity
- Post Analytics, Platform Analytics

Sources:
- New Post — emits when a post is created or updated
- New Activity Event
- New Webhook Delivery

Auth is one field: a team API key, created in Content Rabbit under Settings → Team → API & Integrations.

Start with the contributing guide and inspect the existing components/contentrabbit/ scaffolding, including the app file and its shared propDefinitions. Confirm what the integration requires before the 17 actions and 3 sources can be submitted. Done means the Content Rabbit app record exists so the prepared component PR can land.

Written by the indexing model from the issue text.