Airtable-Driven Multi-Platform Social Content Publisher using Postiz - n8n Workflow

• Content Marketing Teams: Seeking automated, error-free multi-platform distribution.


• n8n Automation Specialists: Users requiring advanced data transformation (Code nodes) within an n8n workflow.


• Agencies: Managing high-volume social media posting for multiple clients.


• Technical Bloggers/Creators: Who use Airtable as their central content database.

This comprehensive n8n workflow template solves the significant challenge of reliable, multi-platform social media distribution. Instead of manually uploading media and copying captions, this n8n automation creates a seamless pipeline. It utilizes Airtable as the single source of truth for both media file IDs (stored in Google Drive) and platform-specific content (captions, titles). The automation first securely downloads the media files using the Google Drive n8n node and uploads them to the Postiz publishing platform, ensuring media accessibility. Subsequently, the content workflow fetches the structured text, uses dedicated Code n8n node blocks to clean the JSON data (removing line breaks and quotes that cause API errors), and routes the content through a Postiz API n8n node to publish simultaneously to up to five platforms, including multiple X/Twitter accounts. This sophisticated n8n workflow significantly boosts efficiency and posting reliability.

The entire process is organized around three primary n8n trigger points (Webhooks) that execute distinct parts of the overall n8n workflow.

Phase 1: Media Preparation (Upload Trigger)

1. Trigger and Fetch: An external system triggers the 🎯 Upload webhook, passing the required Airtable Record ID. The 📊 Content Database (Media) Airtable n8n node retrieves the Google Drive file IDs and existing Postiz paths.


2. Download: Parallel Google Drive n8n node operations (📥 Download Video and 📥 Download Image) download the binary media data.


3. Postiz Upload: The media is uploaded via HTTP Request n8n node to the self-hosted Postiz API endpoint using multipart-form-data.


4. Path Saving: The Postiz file paths are immediately saved back to the Airtable record using the 💾 Save Path Airtable n8n node, making them instantly available for the posting phase.

Phase 2: Content Posting (Post Trigger)

1. Content Retrieval: The Post webhook initiates the main content publishing branch. The 📊 Content Database (Posts) Airtable n8n node retrieves all platform captions (instagrampost, linkedinpost, twitter single, etc.).


2. Validation and Cleaning: The 🔍 Content Validator & Cleaner1 Code n8n node performs critical data manipulation—removing problematic JSON characters like \n, escaping quotes, and enforcing character limits to ensure API compatibility.


3. Routing: After a validation check (📋 Content Availability Check1), the n8n workflow fetches social integration IDs from Postiz and uses the 🔀 Platform Router Switch n8n node to route the flow to platform-specific cleaning and publishing branches.


4. Publishing: For platforms like Instagram and LinkedIn, dedicated Code n8n node blocks perform final content cleaning before sending platform-specific POST requests to the Postiz API using the pre-uploaded media paths.


5. Result Processing: The 📊 Fixed Results Processor Code n8n node collects all API responses and summarizes the success/failure status for tracking.

Phase 3: Video Posting (Video Trigger)

1. A dedicated parallel workflow is triggered by the Video webhook.


2. Similar cleaning and routing logic (🧹 Instagram Video Cleaner, 🔀 Video Platform Router) prepares content and publishes the video media paths (postiz video) to Instagram Reels, Facebook Video, and YouTube via dedicated HTTP Request n8n node steps.

To deploy this powerful n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON and import it into your n8n instance.


2. Airtable Credentials: Set up credentials for the Airtable n8n node. This requires an API token or Personal Access Token and must have access to the specified Base (appTFomwpoQ8GVsSo) and Table (tblRnaXqxrvcQhqBw).


3. Google Drive Credentials: Configure Google Drive OAuth2 credentials (cMdQMNaewaEQ6Mi3) with read access to the folder containing your media files.


4. Postiz API Credentials (HTTP Header Auth): The core of this n8n workflow relies on HTTP Header Authentication for the Postiz platform (mEU0ecS6LOVkcowP). You will need to replace https://postiz.yourdomain.com with your actual Postiz instance URL in all HTTP Request n8n node settings and ensure the authentication header (likely a Bearer token or API key) is configured.


5. Adjust Integration IDs: The 🔀 Platform Router Switch n8n node uses hardcoded Postiz integration IDs (e.g., cmcotolny0001pnal2i86mkrh). You must update these values to match the unique integration IDs provided by your Postiz setup.


6. Set Webhook Triggers: Ensure the Webhook n8n trigger nodes (🎯 Upload, Post, Video) are active and note their URLs for external calling systems.

This complex n8n workflow utilizes numerous specialized n8n node types for data handling, transformation, and API communication:

Airtable n8n node (📊 Content Database (Media), (Posts), (Video)):
Function: Serves as the central content management system. It retrieves file IDs (for Google Drive) and text captions/titles (for social posts).
Key Configuration: Uses the Get operation by record ID, referencing the record ID dynamically from the incoming webhook payload.

Google Drive n8n node (📥 Download Video, 📥 Download Image):
Function: Downloads the binary media content from Google Drive using file IDs retrieved from Airtable.
Key Configuration: Operation set to Download. Output is binary data, required for the subsequent Postiz multipart-form-data upload.

HTTP Request n8n node (Multiple Instances):
Function: Core communication with the Postiz API for media uploads (/upload) and content publishing (/posts).
Key Configuration: Uses HTTP Header Auth. Publishing nodes are configured to send a complex JSON body containing the Postiz integration ID, cleaned content, and the required postiz image or postiz video path saved in Airtable.

Code n8n node (e.g., 🔍 Content Validator & Cleaner1, 🧹 Instagram Content Cleaner):
Function: Crucial for robust posting. These n8n node instances use JavaScript to perform comprehensive content cleaning—removing carriage returns (\r), line feeds (\n), and tabs (\t)—to prevent the Postiz API from rejecting malformed JSON payloads. Also includes character limit checks.

Switch n8n node (🔀 Platform Router, 🔀 Video Platform Router):
Function: Controls the flow path based on the integration IDs fetched from Postiz. This ensures that the correct content (e.g., Twitter captions vs. LinkedIn captions) is sent to the corresponding publishing n8n node.
Key Configuration: Checks if the Postiz integration ID ({{ $json.id }} or {{ $json.identifier }}) matches specific hardcoded values for each platform (Instagram, Facebook, X/Twitter, etc.).