Code workflows
1,006 results — all source-linked n8n references
Govern enterprise marketplace support actions with OSuite approvals
Quick overview This workflow runs on demand to preflight a high-value marketplace support action and send it to OSuite for governance review, then blocks, waits for approval, or proceeds to draft a safe internal refund-risk recommendation and records the final outcome in OSuite. How it works Starts manually to create a structured enterprise support action request with risk, data classification, systems touched, and expected side effects. Runs a local preflight that validates required fields, normalizes the risk score, and computes exposure level, blast radius, and a recommended control. Stops with an intake-fix status if the request is incomplete, including the blockers and warnings to address. Retrieves an OSuite runtime exposure snapshot and submits the planned work to OSuite for policy review with the preflight and decision context. Builds an operator approval packet from OSuite’s response and stops immediately if OSuite blocks the action. Checks OSuite to confirm whether the specific action ID has been approved, and stops in a waiting state until approval is granted. After approval, drafts an internal-only refund-risk recommendation (no refunds or external messages) and records
WCreate human-reviewed personalized PDFs from Stripe payments using OpenAI
Quick overview This workflow receives Stripe payment webhooks, looks up the customer’s order in Google Sheets, generates personalized HTML content with OpenAI, converts it to a PDF using PDFShift, then queues the request for human approval and delivers the final document via Gmail with Slack notifications. How it works Receives a Stripe payment notification via a webhook endpoint. Extracts payment details (event type, payment ID, customer email, amount, currency) and stops the main flow if the email is missing. Pulls order rows from Google Sheets and matches the order to the payer’s email. Sends the combined payment and order data to the OpenAI Chat Completions API to generate structured personalized content, then renders it into an HTML document. Converts the HTML to a PDF with PDFShift and sends the customer an acknowledgement email via Gmail. Appends the request to a Google Sheets “ReviewQueue” and notifies staff in Slack with instructions to approve via a separate webhook. When an approval webhook is received and marked approved, emails the final message to the customer via Gmail and updates the “ReviewQueue” status in Google Sheets. Setup Create and configure two webhook URLs
Route urgent Gmail support emails and WhatsApp digests with Groq and Supabase
Quick overview This workflow monitors a Gmail inbox, uses Groq LLM classification to label each support email as urgent, routine, or spam, logs the result to Supabase, sends immediate WhatsApp alerts for urgent messages, and delivers a daily WhatsApp digest summarizing routine emails. How it works Triggers every minute when a new email arrives in Gmail. Uses Groq (via an LLM prompt) to classify the email as urgent, routine, or spam and generate a one-sentence summary and reason. Inserts the email metadata, category, and summary into a Supabase table for tracking. Sends an immediate WhatsApp message to the support owner when the email is classified as urgent and updates the Supabase record to reflect it was notified. Runs on a daily schedule to fetch all routine emails in Supabase that have not yet been included in a digest. Aggregates those routine emails into a single WhatsApp digest message, sends it to the support owner, and marks the included Supabase records as digested. Setup Connect Gmail OAuth2 credentials and ensure the trigger watches the support inbox/labels you want monitored. Add Groq API credentials for the chat model used to classify and summarize emails. Add Supabas
Generate weekly student progress reports with Gemini, Supabase, and WhatsApp
Quick overview This workflow runs weekly to pull student attendance and score data from Supabase, uses Google Gemini to generate per-student performance summaries and attention flags, sends immediate WhatsApp alerts for flagged students, then compiles all summaries into a PDF report, uploads it, and shares it with the coach via WhatsApp. How it works Runs weekly on a schedule. Fetches all student weekly metrics (attendance and scores) from Supabase. Uses Google Gemini to write a short performance summary per student and determine whether the student should be flagged for attention based on attendance and score-drop rules. If a student is flagged, sends a WhatsApp message to the coach and inserts a flag record into Supabase. Aggregates all students’ summaries into a single HTML weekly report. Converts the HTML report to a PDF via an HTTP-based HTML-to-PDF API, uploads the PDF to a file-hosting API, and sends the PDF link/document to the coach via WhatsApp. Logs the report URL to Supabase for recordkeeping. Setup Add Supabase credentials and create the required tables/columns (weekly_student_data, attention_flags, and weekly_reports) referenced by the workflow. Add a Google Gemini (P
Send CRM lead outreach emails with Notion, Gmail, Google Drive and OpenAI
Quick Overview This workflow watches a Notion CRM for leads ready to contact, checks Gmail to avoid duplicate outreach, then sends or drafts an email with Google Drive PDF attachments and updates the lead status in Notion, with bounce detection that marks invalid emails (using OpenAI to extract addresses). How it works Triggers when a lead page is updated in a selected Notion CRM database. Validates that the lead’s Email field looks like an email address and searches Gmail Sent for recent messages to that recipient to detect prior outreach. If the lead was already emailed and the current status is safe to overwrite, it updates the Notion lead status to “Emailed.” If the lead was not previously emailed, it downloads two PDF attachments from Google Drive, converts them to Gmail attachments, and either creates a Gmail draft for specific domains (optionally sending a Twilio SMS to a rep) or sends a generic vs personalized Gmail email based on whether a contact name exists. After sending, it waits briefly, searches Gmail for bounce messages mentioning “Address not found,” and updates the Notion record to “INVALID EMAIL” (or sets “Emailed” when the status indicates the lead is in an acti
Sync SAP sales project fields between Microsoft SQL and Asana
Quick overview This workflow runs hourly to sync project records from a Microsoft SQL Server staging table into matching Asana projects, updating Asana custom fields and writing back sync status, errors, and the Asana project ID to the database. How it works Runs every hour and queries Microsoft SQL Server for up to 100 project records that are not yet synced (or previously failed) and have fewer than three sync attempts. Marks each selected record as “Processing” in SQL Server to prevent duplicate handling during the sync. Calls the Asana API to list projects in a specific portfolio and matches the SQL ProjectName to an Asana project name. If no Asana project matches, updates the SQL record to a “Waiting for Project ID” state with a message for manual project creation. If a match is found, retrieves the Asana project’s custom fields and builds an update payload mapping SQL values (manager, margin, revenue, costs, and dates) to Asana custom fields. Updates the Asana project via the Asana API and then marks the SQL record as “Completed” with the Asana project ID, or logs the error and marks the record as “Failed” while incrementing the attempt counter. Setup Create Microsoft SQL Ser
Save starred Gmail emails as Markdown notes to an Obsidian Google Drive folder
Quick overview This workflow runs daily, finds starred Gmail emails that are not yet labeled as saved, converts each email into a Markdown note with YAML frontmatter, uploads the note to a Google Drive folder synced with your Obsidian vault, and then labels the email to prevent duplicates. How it works Runs every day at 7am on a schedule trigger. Searches Gmail for emails matching your query (default: starred) while excluding messages already labeled obsidian-saved. Converts each matching email into a Markdown file with YAML frontmatter (title, from, date, tags) and the email body, using a date-prefixed, filesystem-safe filename. Processes emails one at a time to avoid rate limits and ensure reliable saves. Creates a .md file in the selected Google Drive folder using the generated filename and Markdown content. Adds the obsidian-saved label to the original Gmail message so it is skipped in future runs. Setup Add Gmail OAuth credentials and ensure your account has access to read messages and apply labels. Add Google Drive OAuth credentials and select the destination Drive and folder ID where your Obsidian vault syncs (for example, a folder inside your vault). Create a Gmail label na
Track weekly Google keyword rankings with SearchApi and Slack
Quick Overview This workflow runs weekly to track your Google rankings for multiple keywords using SearchApi, compares current positions to the previous run stored in an n8n Data table, and posts a formatted movement report to Slack. How it works Runs every week on a schedule. Loads your target domain, comma-separated keyword list, and Google location, then fetches previously saved ranks from an n8n Data table. Splits the keyword list into individual keywords and queries Google via SearchApi for the first 5 pages of results per keyword. Scans the organic results to find your domain’s best position per keyword and calculates week-over-week movement (up, down, new, dropped out, or not ranking in the top 50). Formats the results into a Slack Block Kit message with a plain-text fallback. Posts the report to a Slack channel and upserts currently ranking keywords back into the Data table for the next comparison. Setup Add a SearchApi.io credential in the SearchApi node. Create or select an n8n Data table (for example, “Rank History”) with columns for keyword, position, url, and last_checked, and select it in both the read and upsert Data table nodes. Add a Slack OAuth2 credential, choose
Draft personalized cold emails from Google Sheets using Gemini and HubSpot
Quick overview This workflow batch-processes leads from Google Sheets, researches each person and company using Tavily plus Google Gemini, drafts a personalized cold email, then creates/updates the contact in HubSpot with a research note and a saved email draft before marking the lead as Done in the sheet. How it works Runs manually and sets a batch size that controls how many leads to process per run. Reads leads from Google Sheets, skips rows already marked as Done, and normalizes the selected batch into clean lead fields. Processes the batch one lead at a time and uses Tavily search (last 60 days) with Google Gemini to extract the most recent public activity, pain points, and a personalization hook. Cleans and parses the research JSON so it can be reused reliably downstream. Uses Google Gemini to draft a 90–120 word cold outreach email (subject and body) that incorporates the research and offers a free “Automated LinkedIn Post Creator” n8n workflow. Creates or reuses the HubSpot contact, logs a HubSpot note with the research and drafted email, and saves the email as a HubSpot engagement in DRAFT status. Updates the matching row in Google Sheets (by Email) to set Status to “Done
Create Zoho Books invoices from email attachments using OpenAI OCR
Quick overview This workflow monitors an IMAP inbox for emails with invoice attachments, uses OpenAI to OCR and extract structured invoice data, looks up customers and tax/currency settings in Zoho Books, and then creates a new Zoho Books invoice with the original attachment included. How it works Triggers when a new email arrives via IMAP. Filters for emails that contain attachments, then splits each attachment into its own item for processing. Normalizes each attachment’s binary data and routes it to OpenAI for OCR based on whether it is a PDF or an image. Fetches taxes, currencies, and active customer contacts from Zoho Books and prepares the data for matching and invoice creation. Sends the OCR text plus Zoho Books tax metadata to OpenAI to validate that the document is a sales invoice and to return invoice and customer details as JSON. Filters out non-invoice attachments, matches the extracted customer to an existing Zoho Books contact (with a configurable fallback), and posts a new invoice to Zoho Books using multipart upload to attach the original file. Setup Add IMAP credentials for the mailbox that receives invoice emails. Add Zoho Books OAuth2 credentials and ensure the c
WRecover Shopify abandoned carts and send weekly reports via Gmail and Sheets
Quick overview This template automates Shopify abandoned cart recovery with a 3-email Gmail sequence, tracks recoveries in Google Sheets via Shopify “order paid” webhooks, and sends a weekly HTML performance report every Monday using data aggregated from the same spreadsheet. How it works Receives a Shopify “checkout created” webhook, verifies the checkout includes an email address, and skips customers who already have an active recovery sequence logged in Google Sheets. Logs the abandoned checkout details to Google Sheets and waits one hour before checking Shopify Orders for a paid purchase by the same email. If no paid order exists, sends the first recovery email via Gmail and updates the Google Sheets row to mark Email 1 as sent. After another 23 hours, checks Shopify Orders again and, if still unpaid, sends the second recovery email via Gmail and updates Google Sheets. After another 48 hours, checks Shopify Orders again and, if still unpaid, creates a unique one-time Shopify discount (price rule + discount code) and sends the third email via Gmail, then stores the discount code and Email 3 status in Google Sheets. Receives a Shopify “order paid” webhook, looks up the customer i
Audit Meta pixel deduplication risks with Graph API and Claude
Quick overview This workflow audits Meta (Facebook) Pixels for potential duplicate conversion counting by comparing browser Pixel vs Conversions API (server) activity and highlighting events active campaigns optimize for, then uses Anthropic Claude to generate pixel-by-pixel verification next steps and prints a prioritized audit report. How it works Runs manually to start the audit. Calls the Meta Graph API to list ad account pixels and fetch ad sets to identify the optimization events used by ACTIVE campaigns. Selects which pixels to audit (prioritizing pixels tied to optimization events, optionally overridden by a dataset ID list) and limits the scope to reduce API calls. For each selected pixel, queries the Meta Graph API for browser-vs-server event source totals and per-event counts. Classifies each pixel’s tracking setup (browser-only, server-only, or dual-source) and prioritizes pixels where optimization events may need deduplication verification. Sends the flagged pixel stats to Anthropic Claude to produce a concise JSON summary and a concrete “verify dedup” action per pixel focused on the optimization events. Prints a formatted audit report showing source split, key convers
Review HeyReach campaign performance and tune Twain agents from Slack
Quick overview This workflow runs daily, pulls campaign stats and reply conversations from HeyReach, sends them to Twain for performance analysis, and posts a digest to Slack with optional one-click approval to apply Twain’s suggested agent updates. How it works Scheduled run Iterates through the configured pairs of Twain campaign IDs and HeyReach campaign IDs. Fetches the HeyReach campaign details, overall performance stats, and recent inbox conversations for each campaign. Packages key metrics and recent message threads and sends them to Twain’s /v2/Campaign/Analyze endpoint for analysis and optimization suggestions. Builds a Slack digest with health signals, reply themes, step diagnostics, and proposed agent changes (plus a link to the campaign in Twain when available). If there are actionable agent changes, posts the digest to Slack with Approve/Skip buttons and applies the approved changes via Twain’s /v2/Agent/Update, then confirms success or errors in Slack. If there are no changes, posts the digest only when the analysis is meaningful (for example, analyzed results or alerts), then moves on to the next campaign. Setup Add HeyReach API access using HTTP Header Auth credentia
Draft personalized LinkedIn outreach from buying signals with Twain and Slack
Quick overview This workflow captures buying-signal leads via a webhook (or optionally polls a HubSpot list), generates a personalized LinkedIn intro and follow-up sequence with Twain, and posts the ready-to-send draft to Slack, with an optional step to stage the lead in a HeyReach campaign. How it works Receives a lead signal via a POST webhook (or, if enabled, runs every 15 minutes to pull contacts from a HubSpot list). Sets the Twain LinkedIn campaign and optional HeyReach campaign IDs, then normalizes the incoming lead fields (name, email, company, LinkedIn URL, and signal context). Deduplicates leads using a stable unique identifier so previously processed contacts are skipped on future runs. If the lead has no LinkedIn profile URL but has an email, optionally looks up the LinkedIn URL using Findymail (or an alternative provider you enable) and merges it back into the lead. If a LinkedIn URL is available, calls the Twain Generate Sequence API to research the lead and generate an intro message plus follow-ups, or posts an error to Slack if generation fails. Formats the generated messages into a review-friendly summary and posts the draft to a Slack channel for manual sending, w
Send and track Slack invoice requests with Gemini, Google Sheets and Gmail
Quick overview Youtube Video: https://youtu.be/42-oHh9w9Eo This workflow listens for Slack @mentions, uses Google Gemini to classify the request and extract invoice details, then reads and updates Google Sheets, generates invoice PDFs with PdfBro, sends invoices or reminders via Gmail, and posts confirmations or errors back to Slack. How it works Triggers when the workflow’s Slack app is mentioned in a specified Slack channel. Uses Google Gemini to classify the message intent (send invoice, remind invoice, or check status) and extract the recipient email and invoice due date. Routes the request based on the extracted intent and stops if the intent cannot be determined. For SEND_INVOICE, looks up the client in a Google Sheets “Client Bill” spreadsheet and posts a Slack error if no matching email is found. If a client is found, generates an invoice PDF with PdfBro, emails it to the client via Gmail, appends/updates the invoice record in a Google Sheets “Client Invoices” spreadsheet, and posts a Slack confirmation. For REMIND_INVOICE, finds an UNPAID invoice for the email in the “Client Invoices” Google Sheet, regenerates the invoice PDF with PdfBro, emails a reminder via Gmail, and p
WSend hashed backend conversions to Meta Conversions API and Google Ads
Quick overview This workflow reads backend conversion events, normalizes and SHA-256-hashes required identifiers, and then sends each conversion to Meta Conversions API, Google Ads Enhanced Conversions, or both using HTTP requests with environment-based access tokens. How it works Runs manually to start the conversion upload. Sets the Meta Pixel ID, Meta/Google API versions, and Google Ads customer and conversion action IDs used to build requests. Loads backend conversion records (example rows) that include a destination flag (meta, google, or both) plus identifiers and conversion value data. Normalizes the identifier fields and hashes the required PII fields (email, phone, name, city/state/zip/country) with SHA-256. Regroups hashed identifiers with the original non-hashed fields (such as external_id, fbc/fbp, IP address, and user agent) into a per-conversion payload structure. Routes each conversion to Meta and/or Google based on the destination flag. Sends conversions to the Meta Conversions API and uploads conversions to the Google Ads API using authenticated HTTP requests. Setup Replace the example conversion source with your own data source (for example Supabase, Postgres, or
Send WhatsApp booking links for Facebook leads with Sheets, Redis, and Cal.com
Quick overview Youtube Video: https://youtu.be/2yB1Imaa6AY?si=FAY4YCeSqqnxCdgW This workflow captures new Facebook Lead Ads leads, stores or updates them in Google Sheets, generates a personalized Cal.com booking link, and sends it via WhatsApp, while also logging the outreach session to Redis and marking the lead as contacted. How it works Triggers when a new lead is submitted through Facebook Lead Ads. Looks up the lead in Google Sheets by phone number to see if an existing row is present. Appends or updates the lead record in Google Sheets when the row does not exist, otherwise checks whether the lead is already marked as contacted or set to do-not-disturb. Prepares a Cal.com base booking link for the selected property and builds an autofilled booking URL using the lead’s name, email, and phone. Sends the lead a WhatsApp message containing the personalized Cal.com booking link. Stores the outbound message as a session entry in Redis and updates Google Sheets to mark the lead as contacted. Setup Connect your Facebook Lead Ads OAuth credentials and select the target Facebook Page and Lead Form in the trigger. Add Google Sheets credentials (service account or OAuth) and update the
Export Google Sheets to CSV or Excel and email files with Gmail
Quick Overview This workflow collects a Google Sheet ID and export preferences via an n8n Form, reads the selected tab from Google Sheets, converts the rows to CSV or Excel (XLSX), and sends the generated file as a Gmail attachment to the requester. How it works Receives a request through an n8n Form that asks for an email address, Google Sheet ID, optional tab name, export format (CSV or XLSX), and an optional file name. Reads the rows from the specified Google Sheets document and tab. Validates the email and Sheet ID, checks that the sheet contains data, and attaches export metadata (format, filename, MIME type, row count) to the items. Routes the run based on the selected format to generate either an XLSX file or a CSV file. Sends an email via Gmail to the provided address with the exported file attached. Setup Connect a Google Sheets OAuth2 credential with access to the spreadsheets you want to export. Connect a Gmail OAuth2 credential for the account that sends the export emails. Activate the workflow and share the form URL, then ensure requesters provide the correct Sheet ID and (if used) the exact tab name.
Export Google Sheets data to CSV or Excel and send via Gmail
Quick Overview This workflow collects a Google Sheet export request via an n8n Form, reads the requested tab from Google Sheets, converts the data to CSV or Excel, and emails the generated file to the requester using Gmail. How it works Receives a sheet export request through an n8n Form that captures the Google Sheet ID, optional tab name, desired format (CSV or XLSX), output file name, and recipient email address. Reads the rows from the specified Google Sheets document and tab. Validates the inputs, stops with an error if the email or Sheet ID is invalid, and aborts if the sheet is empty or the tab name is incorrect. Routes the data to either a CSV or XLSX conversion based on the selected export format. Generates the file (CSV or Excel) from the sheet rows and attaches it to an email. Sends the exported file to the user via Gmail, including basic details like file name, format, row count, and the source Sheet ID. Setup Connect a Google Sheets OAuth2 credential with access to the spreadsheets you want to export. Connect a Gmail OAuth2 credential for sending emails and confirm the sender name and email settings. Activate the workflow and share the source Google Sheets with the con
WGenerate and email invoice PDFs from Google Sheets with PDFMunk and Gmail
Quick overview This workflow watches a Google Sheets order sheet for new invoice rows, generates a unique invoice number, appends the normalized record to another sheet, converts an HTML invoice into a PDF via PDFMunk, and emails the PDF to the client using Gmail. How it works Triggers when a new row is added to a specified Google Sheets worksheet. Maps the incoming columns (client details, item, quantity, price, due date, and status) into a standardized structure and generates an invoice number. Appends the invoice data, including the generated invoice number, into a second worksheet in Google Sheets. Builds an HTML invoice template and calculates totals from quantity and unit price. Sends the HTML to the PDFMunk API to generate a PDF link, then downloads the PDF file. Sends the invoice to the client via Gmail with the PDF attached. Setup Connect your Google Sheets OAuth credentials and select the correct spreadsheet and source/target worksheets for the trigger and append actions. Create a PDFMunk API key (or equivalent header auth) and add it as HTTP Header Auth credentials for the PDF generation request. Connect your Gmail OAuth2 credentials and confirm the email subject/body an
Switch Gainium DCA bot risk mode with the fear and greed index and Telegram
Quick overview This workflow runs daily, fetches the Crypto Fear & Greed Index from alternative.me, and uses it to start or stop a Gainium Crypto Trading DCA bot as a simple risk-on/risk-off switch, sending the current regime and any errors to Telegram. How it works Runs every day at 08:00 on a schedule. Loads your bot settings, Fear/Greed thresholds, and Telegram chat ID from a single configuration step. Fetches the latest Crypto Fear & Greed Index value from the public alternative.me API. Classifies the 0–100 index value into risk-off, risk-on, or neutral based on your thresholds. Stops the Gainium bot when the value is at or below the fear threshold, starts the Gainium bot when it is at or above the greed threshold, and makes no change in the neutral band. Sends a Telegram message describing the index value, regime, and action taken, and posts Telegram alerts if the index fetch, bot action, or any workflow step fails. Setup Install the n8n-nodes-gainium community node and add a Gainium API credential with permission to start/stop the target bot. Add Telegram credentials (bot token) and set your Telegram chat ID in the Config step, and also update the chat ID in the three alert s
Create voiceover MP3s and karaoke subtitles using Edge TTS and FFmpeg
Quick overview This self-hosted workflow takes text and a selected language from an n8n form, generates an MP3 voiceover using the Edge TTS CLI, analyzes the audio with FFmpeg/FFprobe to detect real pauses, and outputs a matching .ass karaoke subtitle file with word-by-word timing. How it works Receives text and a language selection from an n8n form submission. Maps the selected language to a specific Microsoft Edge TTS voice name. Writes the submitted text to a temporary file and uses the edge-tts CLI to generate an MP3 voiceover. Runs FFprobe to read the audio duration and FFmpeg silencedetect to find silence start/end markers. Calculates word-level timestamps that allocate timing to speech segments (excluding detected silences) and aligns sentences to pause-separated speech groups when possible. Builds an Advanced SubStation Alpha (.ass) subtitle file with \k karaoke tags and line wrapping based on character width. Saves the .ass subtitle file to disk alongside the generated MP3 for download or use in a video editor. Setup Use a self-hosted n8n instance with the Execute Command node enabled and file access configured to allow writing under /tmp. Install edge-tts on the n8n host
CWReport workflow errors to Asana tasks with Google Chat and Grok 4.5 analysis
Quick overview When a monitored workflow fails, this reads its Description field to find the owning client and assignee, looks them up in Asana, analyses the error with Grok 4.5, and creates an assigned task with a severity-based due date. Repeat failures comment on the existing task. How it works Any workflow that names this one as its error workflow triggers it on failure. There is no production trigger by design. The error payload only carries a workflow ID, so an HTTP Request calls the n8n API to read that workflow's own Description field, which holds a small JSON object naming the client and the assignee. Asana projects and users are fetched live and matched by name, so no GID is ever hardcoded. A failed match raises a warning that travels downstream instead of failing silently. Asana is searched for an open task covering the same workflow and node. If one exists, a comment carrying the new execution ID is added rather than a duplicate task. For a new error, Grok 4.5 via OpenRouter returns a root cause, a solution, concrete steps, a severity, and a category, held to a fixed shape by a structured output parser. Severity sets the due date: Critical today, High tomorrow, Medium i
Create Instagram carousels and TikTok slideshows with OpenAI and PostFast
Quick overview This workflow runs on a Mon/Wed/Fri schedule to generate an Instagram carousel or TikTok slideshow using OpenAI (GPT-4o-mini and gpt-image-1), sends the slides to Telegram for approval, and only then uploads the images and schedules the post via PostFast. How it works Runs every Monday, Wednesday, and Friday at 8am and loads your brand, topics, slide count, platform filter, and Telegram chat ID. Retrieves your connected social accounts from PostFast and keeps only accounts that are connected and match the selected platforms. Uses OpenAI (gpt-4o-mini) to write a carousel as strict JSON containing a caption and slide-by-slide headings, body text, and visual descriptions. Builds per-slide image prompts and uses OpenAI (gpt-image-1) to generate a 1024×1536 portrait image for each slide. Sends the generated slide images to Telegram and waits for you to approve or decline posting. If approved, requests per-account upload URLs from PostFast, uploads each slide image to the provided storage URLs, and schedules one PostFast social post per account with the slides in order and the generated caption. Setup Install and enable the PostFast community node (n8n-nodes-postfast) and