Publish image & video to multiple social media (X, Instagram, Facebook and more)
This Workflow streamlines the process of publishing posts (image or video) to multiple social media platforms using a unified form and a third-party API service called Upload-Post.
The automation starts with a form trigger, allowing users to submit content (text and media) through a simple frontend interface. Users select the platform (Instagram, LinkedIn, Facebook, X, TikTok, Threads), choose the profile name, write a caption, and upload a photo or video.
How It Works
Automates cross-platform social media posting via Upload-Post, handling both images (JPEG) and videos (MP4). Here’s the process:
-
Trigger:
- A form submission captures user inputs:
- Platform (Instagram, LinkedIn, Facebook, X, TikTok, Threads).
- Account (pre-configured profile name).
- Caption and file (image/video).
- Optional Facebook Page ID for targeted posting.
- A form submission captures user inputs:
-
Routing:
- The "Video or Photo?" Switch node checks the file’s MIME type:
- Image: Routes to the "Post photo" HTTP node (uploads via
upload_photosAPI). - Video: Routes to the "Post video" HTTP node (uploads via
uploadAPI).
- Image: Routes to the "Post photo" HTTP node (uploads via
- The "Video or Photo?" Switch node checks the file’s MIME type:
-
API Integration:
- Both nodes send data to Upload-Post.com’s API, including:
- Caption, account name, platform, and file binary.
- Facebook ID (if provided).
- Both nodes send data to Upload-Post.com’s API, including:
-
Success/Failure Handling:
- The "Result Photo/Video" nodes parse the API response.
Setup Steps
Prerequisites:
- Upload-Post.com API Key:
- Get it from the API Keys dashboard.
- Free tier allows 10 uploads/month.
Configuration:
-
API Authentication:
- In the HTTP Request nodes (
Post photo/Post video), set theAuthorizationheader:Name:AuthorizationValue:Apikey YOUR_API_KEY_HERE.
- In the HTTP Request nodes (
-
Form Customization:
- Adjust the "On form submission" node to:
- Add/remove platforms (e.g., YouTube when approved).
- Modify file type restrictions (default:
.jpg,.mp4).
- Adjust the "On form submission" node to:
-
Account Mapping:
- Ensure the "Account" field matches profiles configured in Upload-Post.com (e.g.,
test1,test2).
- Ensure the "Account" field matches profiles configured in Upload-Post.com (e.g.,
-
Facebook Page Integration:
- Optional: Add a Facebook Page ID field for page-specific posts.
-
Testing:
- Submit test forms with images/videos.
- Verify API responses and success/failure messages.
Optional Enhancements:
- Add error logging (e.g., save failed attempts to a database).
- Extend to YouTube once API support is confirmed.
Key Features:
- Multi-Platform: Post to 6+ social networks simultaneously.
- User-Friendly: Simple form interface for non-technical users.
- Error Handling: Clear feedback for success/failure cases.
Need help customizing?
Contact me for consulting and support or add me on Linkedin.
n8n Form Trigger with Conditional Logic
This n8n workflow demonstrates how to use an n8n Form Trigger to initiate a workflow and then apply conditional logic to process the submitted data. It's a foundational example for building interactive forms that trigger automated actions based on user input.
Description
This workflow simplifies the process of receiving data via a custom n8n form and then routing that data through different paths based on specific conditions. It's ideal for scenarios where you need to collect information and perform varied actions depending on the values submitted in the form.
What it does
- Listens for Form Submissions: The workflow starts when a user submits data through a custom n8n form.
- Processes Form Data: The submitted data is then passed to an "Edit Fields (Set)" node, which can be used to modify or add fields to the incoming data if necessary.
- Applies Conditional Logic (If): An "If" node evaluates a condition based on the data received. Items that meet the condition are routed through the
truebranch, while others go through thefalsebranch. - Applies Conditional Logic (Switch): A "Switch" node further categorizes the data based on multiple possible values of a field, directing items to different outputs depending on which case they match.
- Performs HTTP Request: An "HTTP Request" node is included, typically used to send the processed data to an external API or service.
Prerequisites/Requirements
- n8n Instance: An active n8n instance where you can import and run this workflow.
- Basic understanding of n8n Forms: Familiarity with creating and using n8n forms.
- HTTP Endpoint (Optional): If you intend to use the "HTTP Request" node, you will need an external API endpoint to send data to.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots next to "New workflow" and select "Import from JSON".
- Paste the JSON code and click "Import".
- Configure the n8n Form Trigger:
- Open the "On form submission" node.
- Design your form by adding the necessary fields. The workflow will process the data submitted through this form.
- Activate the workflow to make the form publicly accessible.
- Configure the Edit Fields (Set) Node:
- Adjust the "Edit Fields" node to transform or add any data fields as required for your specific use case.
- Configure the If Node:
- Open the "If" node and define the condition(s) that will determine whether items follow the
trueorfalsepath.
- Open the "If" node and define the condition(s) that will determine whether items follow the
- Configure the Switch Node:
- Open the "Switch" node and define the expression and cases to route data based on multiple possible values.
- Configure the HTTP Request Node:
- If you plan to send data to an external service, configure the "HTTP Request" node with the appropriate URL, method (e.g., POST), headers, and body content.
- Activate the Workflow: Once configured, activate the workflow to start processing form submissions.
This workflow provides a flexible foundation for building sophisticated form-driven automations with conditional processing.
Related Templates
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.
Competitor intelligence agent: SERP monitoring + summary with Thordata + OpenAI
Who this is for? This workflow is designed for: Marketing analysts, SEO specialists, and content strategists who want automated intelligence on their online competitors. Growth teams that need quick insights from SERP (Search Engine Results Pages) without manual data scraping. Agencies managing multiple clients’ SEO presence and tracking competitive positioning in real-time. What problem is this workflow solving? Manual competitor research is time-consuming, fragmented, and often lacks actionable insights. This workflow automates the entire process by: Fetching SERP results from multiple search engines (Google, Bing, Yandex, DuckDuckGo) using Thordata’s Scraper API. Using OpenAI GPT-4.1-mini to analyze, summarize, and extract keyword opportunities, topic clusters, and competitor weaknesses. Producing structured, JSON-based insights ready for dashboards or reports. Essentially, it transforms raw SERP data into strategic marketing intelligence — saving hours of research time. What this workflow does Here’s a step-by-step overview of how the workflow operates: Step 1: Manual Trigger Initiates the process on demand when you click “Execute Workflow.” Step 2: Set the Input Query The “Set Input Fields” node defines your search query, such as: > “Top SEO strategies for e-commerce in 2025” Step 3: Multi-Engine SERP Fetching Four HTTP request tools send the query to Thordata Scraper API to retrieve results from: Google Bing Yandex DuckDuckGo Each uses Bearer Authentication configured via “Thordata SERP Bearer Auth Account.” Step 4: AI Agent Processing The LangChain AI Agent orchestrates the data flow, combining inputs and preparing them for structured analysis. Step 5: SEO Analysis The SEO Analyst node (powered by GPT-4.1-mini) parses SERP results into a structured schema, extracting: Competitor domains Page titles & content types Ranking positions Keyword overlaps Traffic share estimations Strengths and weaknesses Step 6: Summarization The Summarize the content node distills complex data into a concise executive summary using GPT-4.1-mini. Step 7: Keyword & Topic Extraction The Keyword and Topic Analysis node extracts: Primary and secondary keywords Topic clusters and content gaps SEO strength scores Competitor insights Step 8: Output Formatting The Structured Output Parser ensures results are clean, validated JSON objects for further integration (e.g., Google Sheets, Notion, or dashboards). Setup Prerequisites n8n Cloud or Self-Hosted instance Thordata Scraper API Key (for SERP data retrieval) OpenAI API Key (for GPT-based reasoning) Setup Steps Add Credentials Go to Credentials → Add New → HTTP Bearer Auth* → Paste your Thordata API token. Add OpenAI API Credentials* for the GPT model. Import the Workflow Copy the provided JSON or upload it into your n8n instance. Set Input In the “Set the Input Fields” node, replace the example query with your desired topic, e.g.: “Google Search for Top SEO strategies for e-commerce in 2025” Execute Click “Execute Workflow” to run the analysis. How to customize this workflow to your needs Modify Search Query Change the search_query variable in the Set Node to any target keyword or topic. Change AI Model In the OpenAI Chat Model nodes, you can switch from gpt-4.1-mini to another model for better quality or lower cost. Extend Analysis Edit the JSON schema in the “Information Extractor” nodes to include: Sentiment analysis of top pages SERP volatility metrics Content freshness indicators Export Results Connect the output to: Google Sheets / Airtable for analytics Notion / Slack for team reporting Webhook / Database for automated storage Summary This workflow creates an AI-powered Competitor Intelligence System inside n8n by blending: Real-time SERP scraping (Thordata) Automated AI reasoning (OpenAI GPT-4.1-mini) Structured data extraction (LangChain Information Extractors)