n8n

What this is

There’s no dedicated Dropslate n8n node - the REST API is plain bearer-token JSON, so a standard HTTP Request node does everything, chained for upload → post the same way a curl script would.

Set up the node

• Method: POST (or whichever the route needs), URL: https://api.dropslate.top/v1/posts.
• Authentication → Generic Credential Type → Header Auth: Name Authorization, Value Bearer ds_live_... - saved as an n8n credential, not typed into the workflow body.
• Body: JSON, the same shape as the curl scenario.

Chain upload then post

Three HTTP Request nodes in sequence:

1. POST /media/uploads → returns uploadUrl and mediaId.
2. A second HTTP Request node does the PUT of the file’s bytes to uploadUrl directly - no Authorization header on this one, the URL is signed on its own.
3. POST /posts with the mediaId from step 1.

Common errors

See Errors for the {code, message, hint} shape every failed node’s response carries - n8n surfaces the response body as is, so the same code values apply.