HumationHuman + Automation
Back to Catalog

Publishing videos across multiple platforms with Blotato (Instagram, YouTube)

AnthonyAnthony
159 views
2/3/2026
TranslationGoogle SheetsWebhookData ProcessingAutomation
Official Page

Description

This workflow automates video distribution to 9 social platforms simultaneously using Blotato's API. It includes both a scheduled publisher (checks Google Sheets for videos marked "Ready") and a subworkflow (can be called from other workflows). Perfect for creators and marketers who want to eliminate manual posting across Instagram, YouTube, TikTok, Facebook, LinkedIn, Threads, Twitter, Bluesky, and Pinterest.

How It Works

Scheduled Publisher Workflow

  1. Schedule Trigger – Runs daily at 10 PM (configurable).
  2. Fetch Video – Pulls video URL and description from Google Sheets where "ReadyToPost" = "Ready".
  3. Upload to Blotato – Sends video to Blotato's media service.
  4. Broadcast to 9 Platforms – Publishes simultaneously to all connected social accounts.
  5. Update Sheet – Changes "ReadyToPost" to "Finished" so it won't repost.

Subworkflow: Video Publisher (Reusable)

  1. Receive Input – Gets URL, title, and description from parent workflow.
  2. Fetch Credentials – Pulls Blotato API key from n8n Data Table.
  3. Upload & Distribute – Uploads to Blotato, then posts to all platforms.
  4. Completion Signal – Returns to parent workflow when done.

> 💡 Tip: The subworkflow can be called from ANY workflow - great for posting videos generated by AI workflows, webhook triggers, or manual forms.

Test Workflow (Optional)

  1. Form Submission – Upload a video file with title and description.
  2. Upload to Dropbox – Generates shareable URL via "[SUB] Dropbox Upload Link" subworkflow.
  3. Trigger Publisher – Calls the subworkflow above to distribute the video.

Setup Instructions

Estimated Setup Time: 20-25 minutes

Step 1: Blotato Account Setup

  1. Create account at Blotato Dashboard
  2. Connect all your social media accounts (most time-consuming step)
  3. Go to Settings and copy your account IDs for each platform
  4. Go to API Settings and copy your API key

Step 2: Configure Workflow

  1. Update Social IDs:

    • Open "Assign Social Media IDs" node
    • Replace placeholder IDs with your actual Blotato account IDs: 
      {
  "instagram_id": "YOUR_ID",
  "youtube_id": "YOUR_ID",
  "tiktok_id": "YOUR_ID",
  ...
}

  2. Create Data Table:

    • Create n8n Data Table named "Credentials"
    • Add columns: service and token
    • Add row: service = blotato, token = YOUR_API_KEY

  3. Set Up Google Sheet:

    • Create sheet with columns: URL VIDEO, ReadyToPost, Description, Titre (Title)
    • Add video data
    • Set ReadyToPost to "Ready" for videos you want to post

  4. Connect Your Sheet:

    • Update "Get my video" node with your Google Sheet ID

> ⚙️ Pro Tip: If you don't need the scheduled version, just use the subworkflow and call it from other workflows.

Use Cases

  • AI Video Workflows: Automatically post videos generated by Veo, Sora, or other AI models to all platforms.
  • Content Schedulers: Queue videos in Google Sheets, let the scheduler post them automatically.
  • Batch Publishing: Generate 10 videos, mark them all "Ready", and let the workflow distribute them.
  • Marketing Campaigns: Coordinate multi-platform launches with a single click.
  • Agencies: Manage multiple client accounts by swapping Blotato credentials in the Data Table.

Customization Options

  • Remove Unused Platforms: Disconnect any social media nodes you don't use (speeds up execution).
  • Change Schedule: Modify the Schedule Trigger to run multiple times per day or on specific days.
  • Different File Hosts: Replace Dropbox with Google Drive, S3, or Cloudinary in the test workflow.
  • Platform-Specific Captions: Add IF nodes before each platform to customize descriptions or add hashtags.
  • Add Approval Step: Insert a WhatsApp or Telegram notification before posting for manual review.
  • Watermarks: Add a Code node to overlay branding before uploading to Blotato.

Important Notes

⚠️ Two Workflows in One File:

  • Lines 1-600: Scheduled publisher (checks Google Sheets)
  • Lines 600+: Subworkflow (called by other workflows)

⚠️ Data Table vs. Hardcoding:

  • Scheduled workflow: Hardcoded API keys in HTTP nodes
  • Subworkflow: Uses Data Table for API keys (recommended approach)

⚠️ Why Use the Subworkflow?

  • Can be called from ANY workflow
  • Easier to manage API keys (one place to update)
  • More flexible for complex automation systems

n8n Video Publishing Workflow

This n8n workflow provides a framework for automating the process of publishing videos across multiple platforms. While the provided JSON is a starter, it includes core components for data handling, API interactions, and sub-workflow execution, laying the groundwork for a robust video distribution system.

What it does

This workflow, as defined by its current JSON structure, sets up the foundational elements for a video publishing automation:

  1. Triggers: It can be initiated in several ways:
    • On a Schedule: A Schedule Trigger allows the workflow to run at predefined intervals (e.g., daily, hourly).
    • Via Form Submission: An n8n Form Trigger can be used to manually input video details or trigger the process via a web form.
    • By Another Workflow: An Execute Workflow Trigger enables this workflow to be called as a sub-workflow from a larger, orchestrating workflow.
  2. Data Management:
    • Google Sheets: Integrates with Google Sheets, likely to read video metadata, publication schedules, or track publishing status.
    • Data Table: A Data Table node is present, which can be used to store or manipulate tabular data within the workflow, potentially for temporary storage or transformation of video details.
  3. Data Transformation:
    • Edit Fields (Set): The Edit Fields (Set) node is included for transforming or setting specific data fields, which is crucial for formatting video information to match different platform APIs.
  4. API Interaction:
    • HTTP Request: An HTTP Request node is available for making API calls to various video platforms (e.g., Instagram, YouTube, Blotato) to upload videos, post descriptions, or update statuses.
  5. Workflow Orchestration:
    • Execute Sub-workflow: The Execute Sub-workflow node indicates the capability to call other n8n workflows, allowing for modularization of complex publishing logic (e.g., a dedicated sub-workflow for YouTube publishing, another for Instagram).
    • No Operation, do nothing: A No Operation node serves as a placeholder or a way to temporarily disable a path in the workflow without removing nodes.
  6. Documentation:
    • Sticky Note: A Sticky Note is included for adding comments or explanations directly within the workflow canvas, aiding in documentation and understanding.

Prerequisites/Requirements

To effectively use and expand this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Account: For the Google Sheets node to access your spreadsheets.
  • Video Platform Accounts: Accounts for the video platforms you intend to publish to (e.g., YouTube, Instagram, Blotato).
  • API Keys/Credentials: Corresponding API keys or OAuth credentials for each video platform you wish to integrate with via the HTTP Request node.
  • Understanding of Platform APIs: Knowledge of the specific API endpoints and data formats required by each video platform for publishing.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New Workflow".
    • Click the "Import from JSON" button and paste the copied JSON.
  2. Configure Credentials:
    • For the Google Sheets node, you will need to set up a Google Sheets credential.
    • For the HTTP Request node, you will need to configure credentials for the video platforms you are targeting. This might involve OAuth2, API keys, or other authentication methods depending on the platform.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency for checking for new videos or initiating publication.
    • n8n Form Trigger: If using, customize the form fields to collect relevant video information.
    • Google Sheets: Configure the spreadsheet ID, sheet name, and operation (e.g., "Read" new video data, "Append" publication status).
    • Edit Fields (Set): Map and transform data from your input (e.g., Google Sheets) into the format required by the target video platform APIs.
    • HTTP Request:
      • Specify the URL for the target video platform's API endpoint.
      • Set the HTTP method (e.g., POST for uploading, PUT for updating).
      • Construct the request body with video metadata and content, potentially using expressions to pull data from previous nodes.
      • Add any necessary headers for authentication or content type.
    • Execute Sub-workflow: If you plan to modularize, create separate workflows for each platform and configure this node to call them.
  4. Activate the Workflow: Once configured, activate the workflow to enable its scheduled runs or form-based triggers.
  5. Monitor and Test: Thoroughly test the workflow with dummy data to ensure it publishes correctly to all intended platforms and handles errors gracefully.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247