Multi-platform social media publisher with Airtable, Google Drive, and Postiz

1335 views

2/3/2026

Conditional Logic JSON Extraction Webhook Validation API

📝 POSTIZ MEDIA UPLOAD WORKFLOW

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 PURPOSE: Automated media upload pipeline that downloads videos and images from Google Drive and uploads them to Postiz storage for social media posting.

🔄 WORKFLOW PROCESS:

Webhook triggers the workflow
Fetch media metadata from Airtable
Download video + image from Google Drive
Upload both files to Postiz storage
Save Postiz file paths back to Airtable

🔧 TECHNICAL DETAILS: • API: Postiz /upload endpoint (multipart-form-data) • Storage: Converts Google Drive files → Postiz URLs • Integration: Updates Airtable with Postiz paths • Required: All media must be uploaded before posting

📱 SOCIAL MEDIA POSTING WORKFLOW

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 PURPOSE: Automated multi-platform social media posting using Postiz API. Distributes content across Instagram, Twitter/X (2 accounts), LinkedIn, and Facebook with platform-specific content cleaning and formatting.

🔄 COMPLETE WORKFLOW PROCESS:

📊 Fetch social media content from Airtable database
🔗 Get integration IDs for all connected social platforms
🔀 Route each platform to appropriate content processor
🧹 Clean content to prevent JSON formatting errors
📱 Post to respective social media platforms simultaneously

📋 PLATFORM COVERAGE: • 📸 Instagram (Visual content + captions) • 🐦 Twitter/X Main Account (Text + images) • 🐦 Twitter/X Alt Account (Duplicate posting) • 💼 LinkedIn (Professional content) • 📘 Facebook (Meta ecosystem posting)

⚠️ CRITICAL CONTENT CLEANING: • Removes line breaks (\n), carriage returns (\r), tabs (\t) • Replaces multiple spaces with single spaces • Prevents 'JSON parameter needs to be valid JSON' errors • ESSENTIAL: Without cleaning, all API calls fail!

🔧 TECHNICAL SPECIFICATIONS: • API: Postiz /posts endpoint (POST) • Authentication: HTTP Header Auth • Content-Type: application/json • Posting Type: Immediate ('now') + 1 minute delay • Media: References pre-uploaded Postiz image paths • Rate Limit: 30 requests/hour (API beta limitation)

🔗 DATA SOURCES: • Content: Airtable • Media: Pre-uploaded via separate media upload workflow • Fields: instagram_caption, linkedin_post, twitter single, faceboook • Images: References 'postiz image' field paths

⚡ EXECUTION FLOW: Airtable → Integrations → Platform Router → Content Cleaners → Social Publishers

🚨 TROUBLESHOOTING: • JSON Errors: Check content cleaning nodes • 500 Errors: Verify integration IDs and account connections • Missing Media: Ensure media upload workflow ran first • Rate Limits: Space out executions (30/hour limit)

🔄 DEPENDENCIES: • Requires: Media upload workflow (for image/video paths) • Connects to: Analytics and monitoring workflows • Updates: Airtable with posting status and URLs

⚠️ CRITICAL NOTES: • Cannot use external URLs in Postiz posts • Files must be uploaded to google drive first - id referenced in airtable • Enables reference tracking for all platforms

📊 DATA FLOW: Google Drive → Download → Postiz Upload → Airtable Update

🔗 CONNECTS TO: Main social media posting workflows that reference these uploaded file paths for Instagram, Twitter, LinkedIn, Facebook, and YouTube posting.

🎬 VIDEO POSTING WORKFLOW

🎯 PURPOSE: Automated video content distribution across Instagram, Facebook, and YouTube using Postiz API. Specialized workflow for video content with platform-specific processing and cleaning.

🔄 WORKFLOW EXECUTION:

📊 Fetch video content from Airtable database (recuoYjg4icStHsMK)
🔗 Get integration IDs for video-enabled platforms
🔀 Route platforms to appropriate video processors
🧹 Clean content for Instagram & Facebook (YouTube bypassed)
📹 Publish to video platforms simultaneously

📹 PLATFORM COVERAGE: • 📱 Instagram: Video posts & Reels (✅ Working) • 📘 Facebook: Video content (⚠️ Test mode) • 🎬 YouTube: Long-form videos (🚨 Broken)

⚡ EXECUTION FLOW: Airtable → Integrations → Video Router → [3 Parallel Paths] ├── Instagram: Cleaner → Publisher ├── Facebook: Cleaner → Publisher
└── YouTube: [Direct] → Publisher

🗄️ DATA SOURCE: • Base: Netkreatives.com • Table: Youtube tool • Video Field: 'postiz video' • Content Fields: instagram_caption, faceboook

🔧 TECHNICAL SPECS: • Method: POST • Auth: HTTP Header (Postiz credentials) • Timing: Immediate posting (+1 minute delay) • Media: Pre-uploaded video paths • Content-Type: application/json

Multi-Platform Social Media Publisher with Airtable, Google Drive, and Postiz

This n8n workflow automates the process of publishing social media content across multiple platforms, leveraging Airtable for content management, Google Drive for media storage, and a custom API for posting. It allows users to manage their social media calendar and assets in a structured way and then automatically publish them based on predefined conditions.

What it does

This workflow streamlines your social media publishing process through the following steps:

Triggers Manually: The workflow is initiated manually, allowing for on-demand publishing.
Retrieves Content from Airtable: It connects to Airtable to fetch social media posts.
Filters for Publishable Content: It checks if the Published field in Airtable is set to false, ensuring only new content is processed.
Processes Content:
- If Published is false:
  - It prepares the data for publishing by setting the Published field to true and adding a Postiz_ID (presumably for tracking successful posts).
  - It then updates the Airtable record to mark the content as published.
  - It retrieves the image from Google Drive using the provided Image_ID.
  - It constructs a payload for the Postiz API, including the post text, image URL, and platform details.
  - It sends an HTTP POST request to the Postiz API to publish the content.
  - A sticky note indicates the successful posting to Postiz.
- If Published is true:
  - The workflow stops with an error, indicating that the content has already been published.
  - A sticky note explains that the item was already published.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Airtable Account: With a base containing your social media content, including fields for Published (boolean), Image_ID (text/URL), and the actual post content.
Google Drive Account: To store your social media images, with appropriate sharing settings for n8n to access.
Postiz Account/API: Access to the Postiz API (or a similar custom API) for publishing content, including the API endpoint and any required authentication.
n8n Credentials: Configured credentials for Airtable, Google Drive, and the HTTP Request node (for Postiz API).

Setup/Usage

Import the Workflow: Download the provided JSON and import it into your n8n instance.
Configure Credentials:
- Set up your Airtable credential.
- Set up your Google Drive credential.
- Configure the HTTP Request node with the necessary API key or authentication for your Postiz API.
Customize Airtable Node:
- Select your Airtable Base and Table Name.
- Ensure the fields referenced in the workflow (e.g., Published, Image_ID) match your Airtable schema.
Customize Google Drive Node:
- Ensure the Image_ID from Airtable correctly maps to the file ID or URL in Google Drive.
Customize HTTP Request Node (Postiz):
- Update the URL to your Postiz API endpoint.
- Adjust the HTTP method and body to match the Postiz API documentation for publishing content.
Activate the Workflow: Once configured, activate the workflow.
Execute Manually: Click "Execute workflow" to trigger the publishing process. The workflow is currently set up for manual execution. You might adapt the trigger to a schedule or a webhook from Airtable for automated publishing.

Related Templates

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

By Wessel Bulte

247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

By Davide

1616

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

By MANISH KUMAR

113