Blotato n8n integrationAutomate Blotato with n8n.
One workflow, nine social platforms, no copy paste. The Blotato n8n integration exposes 8 operations across 4 resources: media, posts, sources and visuals. Media holds the files, Post writes and checks, No Blotato trigger exists, so a Schedule Trigger opens the run.
Community node This node is not shipped with n8n: it is a community package (@blotato/n8n-nodes-blotato) you install from Settings › Community nodes on a self-hosted instance. npm
Verified Trustpilot reviews · AI, automation & growth agency
What does the Blotato n8n integration give you?
The Blotato n8n integration lets a workflow do the whole publishing chain without a human in the middle: push an image or a video into Blotato, write the post, pick the platform and the connected account, fire it now or at a chosen time, then read back the status. Four resources cover it. Media holds the files, Post writes and checks, Source turns a link or a block of text into usable content, Video builds a visual from a template.
Take a weekly repurposing run. A Schedule Trigger wakes up on Monday, Google Sheets hands over the list of YouTube links published last week, source.create sends each one for extraction with an instruction like reformat into five bullet points, and source.get collects the cleaned transcript once it is ready. The text lands in post.create, one branch per platform.
Second pattern, the approval loop. A draft comes out of OpenAI, a human reads it, and only then does the workflow publish. An If node splits approved from rejected, the approved branch calls media.upload for the visual and post.create with a Scheduled Time set to the evening slot. Nothing leaves n8n until someone said yes.
Third pattern, the visual factory. video.create builds a carousel or an infographic from a template, video.get polls until the render is done, and the finished asset goes into the next post. Old renders get cleaned up with video.delete so the library stays readable.
The node covers those 8 operations and nothing else. Anything the Blotato API offers beyond them goes through the HTTP Request node, which calls any endpoint while reusing the same credential through predefined authentication. There is also no Blotato trigger, so a workflow never starts from Blotato itself.
Worth knowing before you build: binary uploads stop at 15MB, and publishing is asynchronous, which means post.create returns a submission you still have to check. If you are weighing platforms before committing, the n8n review covers the hosting and cost side in detail.
How do you install and connect Blotato in n8n?
- 01
Install the community package
Blotato is not shipped with n8n. Open Settings, then Community nodes, and install the npm package
@blotato/n8n-nodes-blotato(version1.0.10). This works on a self-hosted instance, whether it runs through Docker or npm. On n8n Cloud, only verified community nodes can be installed. Once the package is in, Blotato appears in the node panel like any other node. - 02
Create the Blotato credential
Open the Credentials menu in n8n and create a Blotato credential. You only do this once: the same credential is reused across every workflow on the instance, and the node offers it in its dropdown as soon as it is saved. Keep it on the instance that already runs your content workflows, so the publishing steps and the rest of the chain share one setup.
- 03
Pick the resource and the operation
Drop the Blotato node on the canvas, select the credential, then choose the resource (Media, Post, Source or Video) and its operation. Start with a low risk one,
post.geton a submission ID you already have, to confirm the credential answers before anything gets published. Fields marked required stop the node from running when they are empty, so fill them in before the first execution.
What can the Blotato node do?
The Blotato node exposes 8 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Media
1 operationUpload media
media.uploadWhat you see in n8n
Notes & use cases
Blotato needs the image or the video in its own library before a post can use it. This operation pushes the file in and hands back the media reference.
Key parameters
- Use Binary Data: on, the node takes the binary from the previous node instead of a URL. Binary uploads are limited to 15MB.
- Media URL: the public URL of the image or video. For larger files, stay on URL upload with Google Drive (up to 60MB), Dropbox, Frame.io, or S3/GCS buckets.
- Input Binary Field: the name of the binary property that carries the media.
Post
2 operationsCreate post
post.createWhat you see in n8n
Notes & use cases
Here is where the publishing actually happens. The operation sends text, media and platform options to one connected account, immediately or at a time you set.
Key parameters
- Platform: required, one of
bluesky,facebook,instagram,linkedin,pinterest,threads,tiktok,twitter,youtube. - Account: required, your Blotato social media account ID. Facebook Page, Pinterest Board and Video Title become required on their own platforms.
- Text: required, the main text for your post. Media URLs takes a comma separated list, and Scheduled Time pushes the post to a future slot.
Get post
post.getWhat you see in n8n
Notes & use cases
Publishing does not resolve on the spot. The create step hands back a submission, and this operation reads the status attached to it, which is how a workflow knows a post really went out.
Key parameters
- Post Submission ID: required, the ID of the post submission to check, a UUID in the shape
123e4567-e89b-12d3-a456-426614174000, usually pulled from the create step with an expression.
Source
2 operationsCreate source
source.createWhat you see in n8n
Notes & use cases
Raw material goes in here. The operation submits a YouTube video, a TikTok, an article, a PDF, an audio file, a block of text or a research query, and Blotato extracts content from it.
Key parameters
- Source Type: required,
urlfor a link with auto-detected type,textfor raw text with optional AI transformation,perplexity-queryfor an AI research query. - URL, Text or Query: required depending on the type chosen just above.
- Optional Instructions: AI instructions to transform the extracted content, for example summarize, translate or reformat.
Get source
source.getWhat you see in n8n
Notes & use cases
Extraction runs on its own clock, so submitting a source and reading it are two separate steps. This one retrieves the extracted content once Blotato is done with it.
Key parameters
- Source ID: required, the ID of the source resolution to retrieve, returned by the submission step.
- Clean Transcript: on, timestamps are stripped and the transcript is cleaned up for YouTube, TikTok and audio sources, which makes the text easier to use for content repurposing.
Video
3 operationsCreate visual
video.createWhat you see in n8n
Notes & use cases
Templates turn into assets at this step. The operation builds a visual, a video, a carousel or an infographic, from a template you picked, filling its fields with data from the workflow.
Key parameters
- Template: required, the template used to create the video, selected from the list the node loads.
- Template Inputs: required, the mapping of the input fields the selected template asks for, wired to values coming from the previous node.
- Prompt: a new prompt to generate the template with, useful to regenerate the same visual for another audience.
Get visual
video.getWhat you see in n8n
Notes & use cases
Rendering takes time, and a workflow that publishes too early publishes nothing. Reading a visual by its ID is how the run waits for the asset to actually exist.
Key parameters
- Video ID: required, the ID of the video, a UUID like
123e4567-e89b-12d3-a456-426614174000, taken from the creation step.
Delete video
video.deleteWhat you see in n8n
Notes & use cases
Libraries fill up fast when a workflow generates visuals every day. This operation removes one video by its ID, which is the cleanup end of the chain rather than a publishing step.
Key parameters
- Video ID: required, the ID of the video to remove. Deletion is not reversible, so check the ID is the one the run created and not one a previous execution left behind.
Need help automating Blotato with n8n?
A person reads every message.
