Community
Community tutorials for Status 200 Uploads
Tutorials that people outside Status 200 Uploads wrote and published on their own sites: a workflow, a lesson or a walkthrough built on one of our integrations. Each card names the author, says what the tutorial builds and which integration it uses, and shows the day we last read it. A tutorial is its author's own work: we read it, we did not run its steps.
- Checked on
Every community tutorial
Written and published by people outside Status 200 Uploads, on their own sites. The title of each card opens the tutorial on its author's own site.
- Publish a Law Firm's Weekly Tip to LinkedIn and Facebook From n8n
by Robert Breen (Ynteractive, n8n Ambassador)
A free practice lesson in your browser: install our n8n node, then schedule a tip on LinkedIn and Facebook, with a dry run first.
Uses n8n. Read on 15 November 2026.
learn.ynteractive.com
How a tutorial is listed
A tutorial here is someone else's work. It is written and published on the author's own site, under the author's name. We do not host it, edit it or change its steps.
We read a tutorial before it is listed, and its card shows the day of the last read. The card gives the author's name as the tutorial's own page does, and one sentence on what the tutorial says it builds.
A card shows only while the tutorial's last read is at most 30 days older than the day this page was last checked, the "Checked on" date at the top. A card with an older read is left off this page, and by the same rule off its integration's page, until the tutorial is read again.
A tutorial is not a test of ours. What we tested ourselves, and on which day, is on each integration's own page.
When a link was given in return for something, for example for the tutorial itself, it is marked as sponsored for search engines.
Write your own tutorial
Anyone can write a tutorial about Status 200 Uploads. These four steps make one that readers can follow.
Pick one job
Build one thing from start to finish, for example one workflow that sends one video to one network. Name the integration it uses and the networks it posts to: each network has its own settings and file limits.
Say what the reader needs
Say which plan your tutorial needs. The REST API, the Python package and the n8n node work with an API key, and API keys are on every plan, Free included. The AI connector, Telegram and Discord are on the paid plans, and so is importing from a Google Drive share link.
Let readers try it without posting
A post sent with dryRun set to true runs every check a real post runs and sends nothing, so a reader can follow your steps before anything goes out. Then show the real run and what comes back.
Publish it, then tell us
Publish the tutorial on your own site, under your own name, and send its address through the Support page. We read a tutorial before we list it, and we decide which ones are listed. A listed tutorial shows your name and a link to your page.
What a tutorial can be about
A tutorial can be about any of these. Each one has a page of its own with the setup, the limits and how it was checked.
REST API
Post with one HTTPS request
Python
pip install status200uploads
n8n
Community node, verified by n8n
AI agents (MCP)
Hosted MCP server for AI apps
Claude
Claude on the web, Desktop and iPhone
Claude Code
Post files from your computer
Google Drive links
Post a shared Google Drive file
Telegram
Send a clip, tap Post
Discord
Post a clip from a server or DM
Questions
People outside Status 200 Uploads, who publish them on their own sites. Each card gives its author's name the way the tutorial's own page does, and says which integration the tutorial uses.
No. A tutorial is its author's own work, and we did not run its steps. We read it on the day shown on its card. What we tested ourselves, and when, is on each integration's own page.
A tutorial is listed here only while its last read is at most 30 days older than the day this page was last checked. One with an older read is left off until it is read again.
Publish it on your own site and send its address through the Support page. We read every tutorial before it is listed, and we decide which ones are listed. A listed tutorial shows your name and a link to your page.
It depends on the integration. The REST API, the Python package and the n8n node work with an API key, and API keys are on every plan, Free included. The AI connector, Telegram and Discord are on the paid plans, and so is importing from a Google Drive share link. A tutorial that posts to X also needs the X add-on. The plan's posts and limits apply either way.
In the API reference and on the page of each integration. Those are written by us and checked against the product. A community tutorial adds an example written by someone outside Status 200 Uploads.
Build the workflow from a tutorial
The REST API, the Python package and the n8n node work with an API key, and API keys are on every plan, Free included.