Workflow Templates

Trello Task-Sync Assistant Description This n8n workflow automates task management by integrating Trello, Supabase, and Telegram to streamline card creation, user assignment, and due date notifications. It ensures seamless synchronization of Trello card data with a Supabase database and sends timely Telegram notifications to keep team members informed about task assignments and deadlines. Key Features Trello Card Syncing**: Automatically registers new Trello cards in Supabase and keeps card details (e.g., due dates, URLs) updated. User Management**: Tracks Trello user assignments in Supabase, creating new user entries and linking them to cards as needed. Real-Time Notifications**: Sends Telegram messages when users are added to or removed from Trello cards, using dynamic, engaging message templates. Due Date Reminders**: Schedules daily checks to notify users via Telegram about tasks due on the current day. Workflow Structure Trello Trigger Flow: Trigger: Activates when a new Trello card is created. Actions: Registers the card in Supabase (cards table) with details like ID, name, and board. Sets up a Trello webhook for real-time updates on the card. Syncs due date changes to Supabase. Detects member additions/removals, checks for existing users in Supabase, creates new user entries if needed, and links users to cards in the card_user table. Webhook Event Flow: Trigger: Processes Trello webhook events (e.g., member changes, due date updates). Actions: Validates event types (add/remove member). Maps Trello usernames to Telegram handles. Sends formatted Telegram notifications with card details and playful, randomized messages for engagement. Due-Date Notification Flow: Trigger: Runs twice daily (every 12 hours) via a scheduled trigger. Actions: Fetches cards due on the current day from Supabase. Retrieves assigned users for each card. Sends Telegram reminders with urgent, formatted messages including card name, board, URL, and due date. Technical Details Tools Used**: Trello: Triggers on card creation and updates via webhooks. Supabase: Stores card, user, and card-user relationship data in cards, users, and card_user tables. Telegram: Sends notifications using a bot. Credentials Required**: Trello API key and token. Supabase URL and key. Telegram bot token and chat ID. Scheduling**: Due date checks run every 12 hours (adjustable). Error Handling**: Includes checks for user existence and conditional logic to manage add/remove events. Use Case Ideal for teams using Trello for project management, this workflow ensures real-time data syncing with Supabase and keeps members informed via Telegram, reducing manual oversight and improving task accountability. It’s particularly useful for remote or distributed teams needing automated task tracking and reminders. Setup Requirements Configure Trello webhooks to point to the n8n webhook URL. Set up Supabase with the required tables (cards, users, card_user). Provide Telegram bot token and chat IDs Test the workflow by creating a Trello card, assigning a member, and setting a due date to verify Supabase entries and Telegram notifications. This workflow enhances productivity by automating task synchronization and communication, ensuring no deadline is missed.

This workflow automates plant care reminders and records using Google Sheets, Telegram, and OpenWeather API. It checks when each plant needs watering or fertilizing, sends a personalized reminder, and lets you confirm the task with a single button. When confirmed, it updates your Google Sheet and shows a confirmation HTML page. Who is it for? Home gardeners who want to automate watering and fertilizing schedules. Anyone managing a plant collection, greenhouse, or garden and wanting a lightweight, no-code reminder system. How it works Schedule Trigger starts the workflow once per day. Read Settings (Google Sheets) checks if vacation_mode is active. Read Plants (Google Sheets) retrieves all plants with columns such as id, plant, last_water, water_freq, etc. DecideDue (Code Node) compares today’s date with the last watering/fertilizing date and marks which plants are due. OpenWeather Request (optional) fetches local forecast for plants with coordinates and weather_delay = true. WeatherGate (Code Node) skips or delays watering if it recently rained or if rain is expected soon. Telegram Send Message sends a reminder for each due task. The message contains an inline button “Mark as done” linking to your webhook URL (opens confirmation window). Webhook – Confirm Done receives the click, update dates on Google Sheets, appends an optional log entry, and returns an HTML confirmation page. Setup steps Principal Workflow Spreadsheet- Create a Google Sheets document with: plants sheet: (id, plant, last_water, water_freq, last_fert, fert_freq, lat, lon, weather_delay , indoor, thirst_level) settings sheet: (vacation_mode, timezone) log sheet: (ts, plant_id, action message_id) Connect your Google account Configure the Schedule Trigger Enable weather integration (Get a free OpenWeather API key) and add it to the HTTP Request node parameters appid. https://openweathermap.org/api Configure Telegram with your credential and your chat id on {YOUR_CHAT_ID}. Configure "Send Dues" node with your custom url https://{YOUR_PROJECT_URL}.app.n8n... Setup steps Sub-Workflow (Webhook) Trigger: Configure your custom Path. Google Sheets: Connect your Google Account and Map sheets and columns. Requirements · A Google account with access to Google Sheets. . A spreadsheet containing three sheets with headers matching the field names used in the workflow. . A telegram bot. . OpenWeather API key for climate-aware watering. How to customise it Add plant photos: Include a photo URL column and show it in the Telegram message. Extend actions: Add pruning, repotting or any other periodic task by duplicating the existing logic.

Who’s it for This template is ideal for IT support teams, internal helpdesk automation engineers, and developers building intelligent ticketing systems. It helps streamline ITSM workflows by automatically classifying user queries, retrieving relevant knowledge base entries, and triggering incident creation in ServiceNow. How it works / What it does This workflow uses Google Gemini and Qdrant to power an intelligent ITSM assistant. When a user submits a query via chat: The Text Classifier categorizes the input as an Incident, Request, or Other. Based on the category: Incidents are automatically logged in ServiceNow. Requests trigger an HTTP call (e.g., for provisioning or access). Other queries are routed to an AI Agent that searches the FAQBase in Qdrant and responds contextually. The Gemini LLM enriches responses and summaries. The Qdrant Vector Store retrieves semantically similar answers from a pre-embedded FAQ knowledge base. The Summarization Chain condenses incident details for better tracking. Sticky notes are used throughout the workflow to document each node’s purpose and improve maintainability. How to set up Connect your Google Gemini API, Qdrant, and ServiceNow credentials. Populate the FAQBase collection in Qdrant with your ITSM knowledge base. Deploy the webhook to receive chat inputs. Test the flow using the Manual Trigger node. Customize the classifier categories and Gemini prompts as needed. Requirements Google Gemini API access Qdrant vector database with embedded FAQ data ServiceNow account with API access n8n instance with LangChain nodes installed How to customize the workflow Modify the Text Classifier categories to suit your organization’s ticket types. Add more FAQ entries to Qdrant for broader coverage. Replace the HTTP Request node with integrations relevant to your ITSM tools. Adjust the Gemini prompts to reflect your tone and support style. Extend the workflow with Slack, Teams, or email notifications for ticket updates.

Telegram AI Assistant with Memory, Tasks, and Live Search (Airtable + Google Calendar) This workflow creates an intelligent Telegram-based AI assistant that remembers user details, manages lists, integrates with Google Calendar, and can fetch live information from the web. It is designed for everyday use and improves over time with your feedback. What It Does Personal Memory:** Saves user preferences and instructions in Airtable. Task & Grocery Lists:** Add, search, or delete grocery and to-do items directly in Telegram. Calendar Management:** Create, update, delete, and search events (single or recurring) with Google Calendar. Voice Support:** Send voice messages—these are transcribed and processed like text. Web Search:** (Optional) Fetch real-time answers using SerpAPI. Prerequisites n8n (Cloud or self-hosted instance). Telegram Bot (create via @BotFather on Telegram). Airtable account with a new Base containing 3 tables: User Memory Grocery's To Do List Google Account with Calendar enabled (for OAuth2). OpenAI API Key (for AI responses + voice transcription). SerpAPI Key (optional, for live web search). Airtable Schema Inside your new Airtable Base, create the following tables and fields: User Memory Memory (text) User (text) Time (created time) Grocery's Item (text) User (text) Created (created time) To Do List Task (text) Project or Class (text) User (text) Created (created time) > Field names must match exactly. Setup Instructions Import the workflow JSON into n8n. Configure credentials for each service in the workflow: Telegram API → Paste in your bot token. Airtable → Add your Airtable personal access token. After this, Airtable nodes will show dropdowns where you can select your Base and then your Tables (no need to paste IDs). Google Calendar → Connect your Google account. Once credentials are added, simply pick your Calendar from the dropdown (e.g., “primary” or any shared calendar). OpenAI → Add your API key for chat + voice transcription. SerpAPI → Add your API key (optional). For Telegram Trigger: Click “Listen for Test Event” and send a message to your bot to register the webhook. In group chats: disable privacy mode in @BotFather so the bot can see all messages. Activate the workflow and start chatting with your bot. How to Use Memory** “Remember my coffee order is oat milk latte.” “Keep replies shorter.” Grocery List** “Add eggs.” → “Added eggs.” “What’s on my grocery list?” → Lists all items “Remove bread.” → “Removed bread.” To-Do List** “Add finish report for work.” “What’s on my to-do list?” “Remove finish report.” Calendar** “Create event ‘Team sync’ tomorrow 3–4 pm.” “Make a recurring study session every Friday at 2 pm.” “Delete the dentist appointment at 4 pm.” Web Search** “Get news.” → Summarizes top 5–6 stories from the past 24 hours. Configuration Notes You don’t need to enter Airtable IDs or Calendar IDs manually — just use the dropdowns after credentials are set up. Airtable “User” field is filled automatically with the Telegram username. Voice messages are downloaded and transcribed by OpenAI before being processed as text. Security All API keys and tokens are stored securely in n8n Credentials. No hard-coded IDs, emails, or secrets in this template. Webhook IDs are not included; n8n generates them automatically on import. Troubleshooting Bot not responding?** Ensure the workflow is active, Telegram Trigger is listening, and bot privacy settings are configured for groups. Airtable errors?** Check that your base and tables exist, and that field names match exactly. Calendar issues?** Confirm the Google account has access to the selected calendar. Voice transcription failing?** Verify your OpenAI credentials and Telegram bot permissions. Why This Template Works for Everyone Uses dropdown selections for Airtable and Google Calendar (no IDs needed). Includes clear setup instructions. Credentials are handled securely through n8n. Flexible: works with groceries, tasks, memory, calendar, and optional live web search.

In this tutorial, I’ll walk you through a step-by-step N8N workflow that combines the power of OpenAI and Claude AI to generate professional, ready-to-use lead magnet plans for any niche. This workflow helps marketers, agencies, and freelancers create engaging lead magnets — such as guides, blueprints, and checklists — with zero manual writing and complete AI automation. Who is this for? Marketers and content strategists creating high-converting lead magnets Agencies looking to scale client content deliverables Freelancers offering marketing automation services Anyone who wants to combine AI + automation for efficient content creation What problem is this workflow solving? Manually writing lead magnets can be slow and inconsistent. This workflow eliminates that by: Using OpenAI and Claude AI to co-create detailed content frameworks Automating research, structure, and formatting of lead magnet documents Allowing full customization for different industries or audiences Reducing production time from hours to minutes What this workflow does This automation connects OpenAI, Claude AI, and Google Drive (or Docs) inside n8n to produce well-structured lead magnet documents. The process includes: Collecting a topic or niche input from a form or webhook. Generating an outline and content blocks using OpenAI. Refining, expanding, and organizing the text using Claude AI. Formatting the content and converting it to clean HTML or Google Docs format. Saving or uploading the final version to Google Drive or Notion. By the end of the tutorial, you’ll have a fully automated content agent that builds lead magnet plans from scratch — ready to deliver to clients or publish instantly. Setup Create Accounts: Sign up for n8n.io. Obtain API access for OpenAI, Claude (via OpenRouter), and Google Drive API. Add API Keys in n8n: Go to Credentials and add your OpenAI and Claude API keys securely. Build the Workflow: Use a Form Trigger or Webhook Node to capture topic input. Add OpenAI Node to generate structure and section ideas. Add HTTP Request Node for Claude API (OpenRouter) to expand sections into polished paragraphs. Use a Function Node to merge sections and format them into Markdown or HTML. Add Google Drive Node to upload or store the final file. Test Your Workflow: Input a test topic (e.g., “Dental Marketing Blueprint”). Wait for the AI to generate, merge, and store your lead magnet content automatically. How to customize this workflow to your needs Modify prompt templates to fit your target audience or writing style. Integrate Notion, Airtable, or Slack for automatic delivery. Add a scheduling trigger (e.g., weekly lead magnet generation). Incorporate branding or styling logic using Markdown → HTML conversion. Expand prompts for multilingual or niche-specific lead magnets. Notes This workflow requires API keys for both OpenAI and Claude (via OpenRouter). Ensure proper handling of text formatting nodes to avoid Markdown errors. Google Drive integration requires OAuth setup in n8n credentials. Works on both n8n Cloud and self-hosted environments. 🎥 Watch the Full Tutorial 👉 YouTube Video Tutorial

Who this is for This workflow is designed for researchers, marketing teams, customer success managers, and survey analysts who want to automatically generate AI-powered summaries of form responses collected via Jotform — turning raw feedback into actionable insights. It is ideal for: Teams conducting market research or post-event surveys. Customer experience teams that collect feedback via forms and need instant, digestible summaries. Product managers seeking concise overviews of user comments and suggestions. Analysts who want to compare comprehensive vs. abstract summaries for richer intelligence. What problem this workflow solves Analyzing open-ended Jotform responses manually can be slow, repetitive, and error-prone. This workflow automates the process by generating two AI summaries for every response: Comprehensive Summary — captures all factual details from the response. Abstract Summary — rephrases and synthesizes insights at a higher, conceptual level. With this workflow: Each response is summarized instantly using Google Gemini AI. Both comprehensive and abstract summaries are automatically generated and stored. Data is persisted in Google Sheets, DataTable, and Google Docs for further use. What this workflow does This n8n workflow transforms Jotform submissions into structured summaries using Google Gemini. Step-by-Step Breakdown Webhook Trigger (Jotform Integration) Listens for new Jotform submissions using the Webhook node. Receives full form data via the Webhook response. Set the Input Fields Extracts and assigns key fields like: FormTitle SubmissionID Body (the formatted form data) Prepares structured JSON to feed into the AI summarization stage. Comprehensive & Abstract Summarizer Powered by Google Gemini Chat Model (models/gemini-2.0-flash-exp). Custom prompt: You are an expert comprehensive summarizer. Build a detailed and abstract summary of the following {{ $json.body.pretty }}. Produces two distinct summaries: comprehensive_summary abstract_summary Structured Output Parser Ensures Gemini output matches a defined JSON schema: { "comprehensive_summary": "", "abstract_summary": "" } Guarantees reliable downstream integration with Sheets and Docs. Persist on DataTable Saves both summaries into an n8n DataTable for historical tracking or visualization. Useful for teams running internal analytics within n8n Cloud or self-hosted environments. Append or Update Row in Google Sheets Writes both summaries into a connected Google Sheet. Columns: comprehensive_summary abstract_summary Create Google Document Automatically generates a Google Docs file titled: {FormTitle}-{SubmissionID} Acts as a per-submission record with a placeholder ready for AI summary insertion. Update Google Document Inserts both summaries directly into the newly created Google Doc: Comprehensive Summary: [Full detailed summary] Abstract Summary: [Conceptual summary] Each doc becomes a polished, shareable insight artifact. Concepts Used in the Workflow Comprehensive Summarization Comprehensive summarization captures every important detail in a factual, exhaustive way — ideal when accuracy and completeness matter. Goal: Provide a detailed understanding of user responses without losing nuance. Best For: Research surveys Customer service logs Support ticket summaries Feedback traceability Abstract Summarization Abstract summarization rephrases and synthesizes ideas, offering high-level insights rather than copying text. Goal: Capture the essence and implications of feedback — ideal for storytelling and executive reviews. Best For: Executive summaries Marketing insights Customer trend analysis Blog-style recaps Setup Instructions Pre-requisite If you are new to Jotform, Please do signup using Jotform Signup For the purpose of demonstation, we are considering the Jotforms Prebuilt Form as a example. Follow these steps to deploy and customize the workflow: Step 0: Local n8n This step is required for the locally hosted n8n only. Please make sure to setup and install ngrok and follow the steps to configure and run ngrok on your local with the n8n port. This is how you can run. ngrok http 5678 Copy the base URL ex: https://2c6ab9f2c746.ngrok-free.app/ as it will be utilized as part of the webhook configuration for the Jotform. Step 1: Configure Jotform Webhook Copy the webhook URL generated by n8n’s Jotform Trigger node. In your Jotform dashboard, go to: Settings → Integrations → Webhooks → Add Webhook If you are executing this workflow on a self hosted n8n instance, please follow the steps for setting up ngrok and format the Webhook URL so that the Jotform can make a Webhook POST over the public URL. Copy the Webhook URL generated by n8n. You can copy the URL by double clicking on the Jotform Trigger node. Make sure to replace the base url with the above Step 0, if you are running the workflow from your local machine. Step 2: Connect Google Gemini Navigate to n8n → Credentials → Google Gemini (PaLM API). Add API credentials and select the model: models/gemini-2.0-flash-exp Test the connection before proceeding. Step 3: Configure the Structured Output Parser Open the Structured Output Parser node. Ensure the schema includes: { "comprehensive_summary": "", "abstract_summary": "" } Modify or expand schema fields if additional summaries (e.g., “sentiment_summary”) are needed. Step 4: Connect Google Sheets Link your Google Sheets OAuth2 credentials. Specify: Document ID (Google Sheet URL) Sheet Name (e.g., “Sheet1”) Map columns to: comprehensive_summary abstract_summary Step 5: Enable DataTable Storage (Optional) Use the DataTable node to maintain a permanent database within n8n Cloud. Configure the schema fields for: comprehensive_summary abstract_summary Step 6: Generate and Update Google Docs Link your Google Docs account under n8n credentials. The workflow auto-creates and updates a doc per submission, embedding both summaries for easy sharing. How to Customize Add Sentiment Analysis** After generating the summary, insert another Google Gemini node to classify the tone of each response — for example, Positive, Neutral, or Negative. This helps you track user sentiment trends over time. Send Alerts for Urgent Feedback** Use an IF node to check if the abstract summary contains words such as “urgent,” “issue,” or “negative.” If triggered, automatically send an alert through Slack, Gmail, or Discord, so the team can respond immediately. Enable Multi-Language Support** Insert a Language Detection node before the Gemini summarizer. Once the language is detected, modify the summarizer prompt dynamically to summarize in that same language — ensuring localized insights. Add Topic Extraction** Include an additional Gemini text extraction node that identifies major topics or recurring themes from each response before summarization. This creates structured insights ready for analytics or tagging. Integrate with CRM or Ticketing Systems** Connect your workflow to HubSpot, Salesforce, or Zendesk to automatically create new records or tickets based on the feedback type or sentiment. This closes the loop between survey collection and actionable response. Summary This workflow automates survey intelligence generation from Jotform submissions — powered by Google Gemini AI — delivering dual-layer summarization outputs directly into Google Sheets, DataTables, and Google Docs. Benefits: Instant comprehensive and abstract summaries per submission. Ready-to-use outputs for reports, dashboards, and client deliverables.

Who is this for? This workflow is designed for software teams, project managers, and developers who manage work across Azure DevOps and GitHub. It helps organizations that use Azure DevOps for work item tracking but rely on GitHub for issue management and collaboration. If you need to ensure that your DevOps Stories and Tasks are mirrored in GitHub issues while keeping a single source of truth in Google Sheets, this workflow is for you. What problem is this workflow solving? / Use case Managing projects across multiple platforms often leads to missed updates and poor traceability. Stories created in Azure DevOps may not be tracked properly in GitHub.\ Tasks under Stories often lose visibility when teams split between platforms.\ Manual syncing between tools takes time and causes human errors. This workflow solves that problem by automating the sync between Azure DevOps Stories and GitHub Issues, while also keeping a Google Sheets record for cross-referencing and reporting. What this workflow does Triggers from Azure DevOps Stories -- When a Story is created or updated, the workflow is activated.\ Creates a GitHub Issue -- A new issue is generated in the specified GitHub repository.\ Assigns a random collaborator -- One repository collaborator is randomly assigned to the issue.\ Logs mapping in Google Sheets -- The Azure DevOps Story ID, GitHub Issue number, and URL are stored for tracking.\ Triggers from Azure DevOps Tasks -- When a Task linked to a Story is created, the workflow looks up its parent in Google Sheets.\ Updates the GitHub Issue -- The parent GitHub Issue is updated with a clickable link to the new Task for better visibility. Setup Connect your accounts GitHub (OAuth2 or personal token)\ Google Sheets (OAuth2)\ Azure DevOps (Webhook integration) Configure Webhooks Add the workflow's webhook URLs to Azure DevOps service hooks for Work Item Created/Updated events. Update repository details Set the GitHub repository where issues should be created. Customize Sheets Use the provided Google Sheet or link your own for issue mappings. How to customize this workflow to your needs Modify assignment logic**: Instead of random collaborator assignment, edit the Code node to assign issues based on workload or labels.\ Change Sheet schema**: Add more fields (e.g., State, IterationPath) to your Google Sheet for richer reporting.\ Expand task linking**: Customize the way Tasks are appended to GitHub issues (e.g., group by state, show due dates). Powered By Concept Recall https://conceptrecall.com

This n8n workflow is designed for security monitoring and incident response when suspicious login events are detected. It can be initiated either manually from within the n8n UI for testing or automatically triggered by a webhook when a new login event occurs. The workflow first extracts relevant data from the incoming webhook payload, including the IP address, user agent, timestamp, URL, and user ID. It then splits into three parallel processing paths. In the first path, it queries GreyNoise's Community API to retrieve information about the investigated IP address. Depending on the classification and trust level received from GreyNoise, the alert is given a High, Medium, or Low priority. This priority is assigned based on the best practices documentation from GreyNoise on how to apply their data to analysis. Once a priority is assigned, a message is sent to a Slack channel to notify users about the alert. The second path involves fetching geolocation data about the IP address using IP-API's Geolocation API and merging it with data from the UserParser node. This data is then combined with the data obtained from GreyNoise. In the third path, the UserParser node queries the Userparser IP address and user agent lookup API to obtain information about the user's IP and user agent. This data is merged with the IP-API data and GreyNoise data. The workflow then checks if the IP address is considered an unknown threat by examining both the noise and riot fields from GreyNoise. If it is considered an unknown threat, the workflow proceeds to retrieve the last 10 login records for the same user from a Postgres database. If there are any discrepancies in the login information, indicating a new location or device/browser, the user is informed via email. Potential issues when setting up this workflow include ensuring that credentials are correctly entered for GreyNoise and UserParser nodes, and addressing any discrepancies in the data sources that could lead to false positives or negatives in threat detection. Additionally, the usage of hardcoded API keys should be replaced with credentials for security and flexibility. Thorough testing and validation with sample data are crucial to ensure the workflow performs as expected and aligns with security incident response procedures.

This n8n workflow is designed to analyze email headers received via a webhook. The workflow splits into two main paths based on the presence of the received and authentication results headers. In the first path, if received headers are present, the workflow extracts IP addresses from these headers and then queries the IP Quality Score API to gather information about the IP addresses, including fraud score, abuse history, organization, and more. Geolocation data is also obtained from the IP-API API. The workflow collects and aggregates this information for each IP address. In the second path, if authentication-results headers are present, the workflow extracts SPF, DKIM, and DMARC authentication results. It then evaluates these results and sets fields accordingly (e.g., SPF pass/fail/neutral). The paths merge their results, and the workflow responds to the original webhook with the aggregated analysis, including IP information and authentication results. Potential issues during setup include ensuring proper configuration of the webhook calls with header authentication, handling authentication and API keys for the IP Quality Score API, and addressing any discrepancies or errors in the logic nodes, such as handling SPF, DKIM, and DMARC results correctly. Additionally, thorough testing with various email header formats is essential to ensure accurate analysis and response.

This AI-powered customer support automation built in n8n handles your e-commerce queries instantly — from order tracking to personalized product recommendations and support ticket management. Features: 🛒 Order Status Tracking: Instantly retrieve order details from your database. 🎯 AI Product Recommendations: GPT-powered suggestions based on customer preferences. 📩 Support Ticket Automation: Auto-create and manage tickets via email or CRM. 🔄 Context-Aware Conversations: AI agent with memory for smooth follow-ups. ⚡ Real-Time Webhook Responses: Instant, API-driven replies to customers. Tech Stack: n8n, OpenAI GPT, Webhooks, Supabase, Email API. Perfect for Shopify, WooCommerce, and custom e-commerce platforms looking to reduce response times and improve customer satisfaction.

📝 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

⚡ UPDATE on May 2025 – added section with all n8n instance webhooks Using n8n a lot? Soar above the limitations of the default n8n dashboard! This template gives you an overview of your workflows, nodes, and tags – all in one place. 💪 Built using XML stylesheets and the Bootstrap 5 library, this workflow is self-contained and does not depend on any third-party software. 🙌 It generates a comprehensive overview JSON that can be easily integrated with other BI tools for further analysis and visualization. 📊 Reach out to Eduard if you need help adapting this workflow to your specific use-case! 🚀 Benefits: Workflow Summary** 📈: Instant overview of your workflows, active counts, and triggers. Left-Side Panel** 📋: Quick access to all your workflows, nodes, and tags for seamless navigation. Workflow Details** 🔬: Deep dive into each workflow's nodes, timestamps, and tags. Node Analysis** 🧩: Identify the most frequently used nodes across your workflows. Tag Organization** 🗂️: Workflows are grouped according to their tags. Webhooks** ⚡: List of all webhook endpoints with the links to workflows. Visually Stunning** 🎨: Clean, intuitive, and easy-to-navigate dashboard design. XML & Bootstrap 5** 🛠️: Built using XML stylesheets and Bootstrap 5, ensuring a self-contained and responsive dashboard. No Dependencies** 🔒: The workflow does not rely on any third-party software. Bootstrap 5 files are loaded via CDN but can be delivered directly from your server. ⚠️ Important note for cloud users Since the cloud version doesn't support environmental variables, please make the following changes: get-nodes-via-jmespath node. Update the instance_url variable: enter your n8n URL instead of {{$env["N8N_PROTOCOL"]}}://{{$env["N8N_HOST"]}} Create HTML node. Please provide the n8n instance URL instead of {{ $env.WEBHOOK_URL }} 🌟Example: Follow me on LinkedIn for more tips on AI automation and n8n workflows!