Skip to content
Dropslate Docs

Automation overview

Everything that publishes through Dropslate goes through one server and one sequence: put a file in the library, plan the post, create it with confirmation, then read its status. The dashboard, a script against the REST API, an AI agent over MCP and a workflow tool such as n8n differ only in who fills in the fields. This page says which to pick, and gives the shared sequence once so the recipes can refer to it.

Which one, for what

Section titled “Which one, for what”
You are Use Example Plan
A person scheduling posts by hand Dashboard A week of Shorts on Friday afternoon Any, including Free
Working in Claude, ChatGPT or Cursor and want to describe the week in words MCP “Schedule these three files Tuesday and Friday at 18:00” Read-only on Free; publishing from Creator
Writing code, or have a pipeline that produces files REST API A render job that uploads its output and schedules it From Creator
Building without code in n8n, Make or Zapier HTTP nodes against the REST API - n8n, Make, Zapier A Google Sheet row becomes a post From Creator
Have the files on your own computer and an agent that can run a shell Claude Cowork “Publish everything in ~/exports” From Creator

Every path is subject to the same plan quota, rate limits, network limits and workspace isolation; there is no back door and no separate metering for agents.

The shared sequence

Section titled “The shared sequence”
  1. Upload. POST /media/uploads with filename, mime and size returns {mediaId, uploadUrl, expiresAt}. PUT the bytes to uploadUrl within the hour; it is single-use. Or POST /media/from-url with a public https URL. Over MCP: dropslate_create_upload or dropslate_upload_from_url.
  2. Wait for ready. GET /media/{id} until status is ready (a video takes seconds to a minute while its duration and thumbnail are read). Over MCP: dropslate_get_media.
  3. Plan. POST /posts/plan with targets, mediaIds, text, when and any perPlatform or overrides. The answer has one row per account with a check; ok: false rows name what would fail. Nothing is created. Over MCP: dropslate_plan_post - and the agent shows you the table.
  4. Create. The same body to POST /posts with confirm: true. One post per account comes back, queued. Over MCP: dropslate_create_post with confirm: true, after you said yes.
  5. Poll. GET /posts/{id} until status is live or failed; externalUrl for a live post, error for a failed one. Over MCP: dropslate_get_post.

Account ids come from GET /accounts (dropslate_list_accounts), never typed by hand; a group id from GET /groups.

Recipes

Section titled “Recipes”

Each recipe is the sequence above applied to one job, with real request bodies:

Section titled “Related”