Overview - Rules by Different Platforms
Diffetent Rules for the RedPanda social scheduler — naming, connect flows, media and caption rules, and analytics by network.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Posting rules by network
What each connected channel accepts before RedPanda sends a post.
Diferent platforms has diffetent rules on caption length, attachment count, and extra fields. RedPanda ships eleven channels today.
This section is the reference how they disagree when you write in the dashboard, schedule through the API, or use MCP tools.
Tip
For step-by-step connect flows, see Connect a channel. For operator developer apps on self-host, see Social integrations. For JSON field names on create post, see Provider settings.
Names in the app vs API
The dashboard and marketing site use short labels. The public API, CLI, MCP tools, and integration list use a fixed channel key for each connection.
| What you see | Channel key |
|---|---|
| instagram-business or instagram-standalone | |
| Facebook / Facebook Page | |
| LinkedIn Page | linkedin-page |
| Dev.to | devto |
| Bluesky | bluesky |
Most other networks use the same name in the app and in the API (for example threads, tiktok, x). The full list with channel keys is in Connect rules.
When you select two Instagram connections or two LinkedIn connections in one post, RedPanda treats them as one family each. Shared caption and media must pass the stricter rules in that family. See Media rules and Global vs per-channel.
Extra parts after the main post
RedPanda uses a few glossaries for multi-part posts. This table shows how RedPanda defined it across different platform.
| Term in RedPanda | What it means |
|---|---|
| Main post | The caption and media that publish first |
| Follow-up comments | Extra rows you add in the composer after the main post, each with its own delay |
| Thread reply | On Threads and X, a follow-up publishes as another post in the same thread |
| Comment | On Instagram, LinkedIn, and Facebook, a follow-up publishes as a comment on the main post |
| Thread finisher | On X (and thread-style channels), an optional closing reply after all follow-ups |
| Plugs | Automations after publish — not the same as follow-up comments. See Internal plugs and Cross-account plugs |
This table then shows whether you can add multi-part in the post editor, and which glossary term applies when RedPanda publishes them.
| Network | Channel key | Follow-up comments | What RedPanda calls the extra part |
|---|---|---|---|
| Threads, X, Bluesky | threads, x, bluesky | Yes | Thread reply (media allowed on follow-ups) |
| Instagram (both), LinkedIn (both) | instagram-business, instagram-standalone, linkedin, linkedin-page | Yes | Comment (text only on follow-ups) |
| Facebook Page | Yes | Comment (one image per follow-up, no video) | |
| YouTube, TikTok, Dev.to | youtube, tiktok, devto | No | — |
Facebook Stories do not support follow-up comments. How to add rows and delays in the composer is in Threads and comments. Attachment and length rules for follow-ups are in Media rules.
How rules are enforced
RedPanda checks posts in two places:
- Composer — The post editor blocks invalid combinations before you schedule. The preview column and messages under the media strip show many issues early.
- Publish — The backend runs the same rules when a scheduled post goes out. The API and MCP enforce length limits on schedule; draft may store longer text.
Upload limits (file size and format) are separate from per-network rules. See Media → Limits and formats.