# Social media integrations: REST API, n8n, Python and AI apps

Canonical: https://status200uploads.com/integrations

Checked on 26 October 2026.

Status 200 Uploads posts to the social accounts you connected from more places than the dashboard: your own code through the REST API, Python through our package, n8n through our community node or its HTTP Request node, and AI apps such as Claude through our hosted MCP server. Every one of them sends the same post through the same server checks and the same plan limits; the AI connector adds a few of its own, such as asking you for TikTok and YouTube privacy.

On every plan, Free included, automate through our [REST API](https://status200uploads.com/docs/api) with n8n, Python or your own scripts. There is no Zapier or Make app: their HTTP steps (Webhooks by Zapier, on Zapier's paid plans; Make's HTTP module) can call the REST API too (not tested by us yet).

## Every integration

- **[REST API](https://status200uploads.com/integrations/rest-api)**: One POST to /api/v2/posts with your API key publishes a post to the networks you connected, or schedules it for later. Tested on 22 October 2026. On every plan, Free included.
- **[Python](https://status200uploads.com/integrations/python)**: The status200uploads package (pip install status200uploads) calls the REST API for you from a script or a notebook. Tested on 12 November 2026 with Python 3.11 and the status200uploads 0.1.0 package. On every plan, Free included.
- **[n8n](https://status200uploads.com/integrations/n8n)**: Our community node is verified by n8n: on n8n Cloud an owner or admin adds it from the nodes panel, on self-hosted n8n it installs from Settings. The HTTP Request node calls the REST API on any n8n. Tested on 12 November 2026 with self-hosted n8n. On every plan, Free included.
- **[AI agents (MCP)](https://status200uploads.com/integrations/mcp)**: A hosted MCP server: an AI app signs in once and can then publish, schedule and check posts for you. Tested on 13 October 2026 with Claude (web, Desktop, iPhone). Included in every paid plan, from Beginner.
- **[Claude](https://status200uploads.com/integrations/claude)**: Add the MCP server to Claude as a custom connector, then ask for a post in plain words. Tested on 13 October 2026 with Claude (web, Desktop, iPhone). Included in every paid plan, from Beginner.
- **[Claude Code](https://status200uploads.com/integrations/claude-code)**: Add the MCP server to Claude Code and post or schedule from the terminal you already work in. Tested on 9 October 2026 with Claude Code. Included in every paid plan, from Beginner.
- **[Google Drive links](https://status200uploads.com/integrations/cloud-links)**: Import a video or an image from a Google Drive share link, then post it like any other file. Tested on 9 October 2026. Included in every paid plan, from Beginner.
- **[Telegram](https://status200uploads.com/integrations/telegram)**: Send a video or a photo to our Telegram bot, check the card and tap Post: it goes to the networks you switched on. Tested on 13 November 2026 with Telegram. Included in every paid plan, from Beginner.
- **[Discord](https://status200uploads.com/integrations/discord)**: Use /post in Discord, or right-click a clip someone shared: a card only you see shows where it goes, and Post sends it. Tested on 13 November 2026 with Discord. Included in every paid plan, from Beginner.

## Which one fits

- You post by hand, now or at a set time: The dashboard.
- Your own app, backend or script, in any language: REST API.
- A Python script, a notebook or a cron job written in Python: Python.
- A workflow that posts when something happens (a new row, a feed item, a form): n8n.
- You would rather ask for a post in plain words: Claude or Claude Code (other AI apps are not tested yet).
- Your files are in Google Drive: Google Drive links.
- Your clips are on your phone, in Telegram: Telegram.
- Your clips are shared in a Discord server: Discord.

## One API under every integration

The REST API is the base of every integration: the Python package, the n8n node and the MCP server send their posts through it, so a post it refuses is refused the same way whichever of them you used.

The REST API and API keys are on every plan, Free included. Create a key in the dashboard under API and send it as a Bearer token. Keep it secret: it can post to every account you connected.

Send an Idempotency-Key header with a post to retry it safely: for 24 hours the same key gets the first answer back, and nothing is posted twice.

Your plan's limits count every post, whichever way it was sent.

A post sent through the API over the day's limit is queued for the next day instead of failing, and the answer says so.

Video sizes are the same for every way in. Image sizes are checked in the dashboard; through the API, some networks decide for themselves. The file limits page lists the largest video and image each network takes.

## Which AI apps can connect

**Which AI apps can connect.** Tested with Claude and Claude Code. Another AI app can connect only if it supports MCP sign-in (OAuth) and, after you sign in, sends you back to a web address (https) or to your own computer. An app that offers only its own kind of address, such as app://, cannot sign in. If we do not recognise the app and it does not sign in on your own computer, it can only read until you tick "I trust this app and accept the risk". An app that cannot sign in can send the rl_* API key of an account on a paid plan instead, and gets a smaller set of 5 tools.

**Sign in, or send a key.** Signing in needs no key: you approve the app on our page and choose read-only or read and publish. A client that cannot sign in sends an rl_* dashboard key over HTTPS instead. The AI connector is included in every paid plan, from Beginner, both ways; on Free, use the REST API.

**The tools, in plain view.** A signed-in app gets 17 tools: accounts, media (a file already in your media library, one from your computer, or a URL), a check before posting, publish, schedule, retry, history and post numbers. An rl_* key gets five tools for media and posting. n8n and your own scripts use the REST API, which publishes and schedules posts and imports media.

Claude on the web, in Claude Desktop and on iPhone, and Claude Code each signed in to the MCP server and used its tools.

Cursor's sign-in worked on 9 October 2026; its tools are not tested yet.

The AI connector is included in every paid plan, from Beginner.

[The MCP server page](https://status200uploads.com/integrations/mcp)

## Questions

### Which integration should I use?

The one that matches where your posts start. Code you write calls the REST API, or the Python package if it is Python. A workflow tool calls it through n8n. If you would rather ask in plain words, an AI app such as Claude or Claude Code uses the MCP server. They all post to the same connected accounts.

### Do I need to write code?

No. n8n workflows are built from nodes, and an AI app takes a request in plain words. The dashboard needs no code either. Only the REST API and the Python package expect you to write a few lines.

### Which integrations are on the Free plan?

The REST API, the Python package and the n8n node all work with an API key, and API keys are on every plan, Free included. The AI connector is included in every paid plan, from Beginner. Importing from a Google Drive share link and posting from Telegram or Discord are on the paid plans too.

### Is there a Zapier or Make app?

There is no Zapier or Make app. Their HTTP steps (Webhooks by Zapier, on Zapier's paid plans; Make's HTTP module) can call the REST API with your API key, but we have not tested a Zap or a Make scenario yet.

### Can I use several integrations on one account?

Yes. An API key, an n8n workflow and an AI app can all post to the accounts you connected, and every post counts toward the same plan limits, whichever way it was sent.

### Can an integration delete a post from a network?

No. Status 200 Uploads cannot delete a post from a network once it is out, whichever way it was sent. A scheduled post can be cancelled until it goes out, and changed in the dashboard or by an AI app.

### How do I know an integration still works?

Each integration page says the day it was last checked and the date of the test it rests on. A claim whose proof is more than 30 days older than that day drops off the page until it is tested again.
