Marketplace
3,557 ready-made workflow files you can download, plus 10,661 source-linked n8n references.
Create AI product video ad Shorts from Telegram photos with OpenAI and AtlasCloud
Quick overview This workflow takes a product photo sent via Telegram, uses OpenAI Vision to describe it and OpenAI to write a short-form video ad prompt, generates a vertical video via AtlasCloud, then (after two approvals in Telegram) publishes the Short to YouTube via Blotato. How it works Triggers when a user sends a product photo (optionally with a caption/campaign) to a Telegram bot. Downloads the image from Telegram and uses OpenAI Vision to extract an advertising-focused product description. Uses OpenAI to generate a single cinematic text-to-video prompt plus a YouTube Shorts title and description. Sends the proposed prompt to Telegram and waits for your approval before proceeding. If approved, requests video generation from AtlasCloud and polls the render status until the video is completed. Sends the generated video back to Telegram for preview and waits for a second approval to publish. If approved, publishes the video to YouTube as an unlisted Short via Blotato and notifies you in Telegram (otherwise it stops and sends a decline message). Setup Create and connect a Telegram bot credential, then start a chat with the bot so it can receive photos and send approval prompts.
Publish AI social posts from Telegram to LinkedIn, Instagram, Facebook and Threads with OpenAI and Blotato
Quick overview This workflow listens for a Telegram message or voice note, uses OpenAI to turn it into a cross-platform social caption and matching AI image, publishes the post via Blotato to LinkedIn, Instagram, Facebook, and Threads, then sends a confirmation back to Telegram. How it works Triggers when a new Telegram message is received by your bot. Routes the input as voice or text, downloading voice notes from Telegram and transcribing them with OpenAI. Sends the resulting text to an OpenAI chat model to generate a single ready-to-publish caption plus an image prompt. Generates an image with OpenAI (gpt-image-1) using the returned image prompt. Uploads the generated image to Blotato to get a hosted media URL. Publishes the caption and image to LinkedIn, Instagram, Facebook Pages, and Threads through Blotato. Sends a Telegram message confirming publication and includes the posted caption. Setup Create a Telegram bot in @BotFather, add the bot token as a Telegram credential in n8n, and activate the Telegram Trigger. Add an OpenAI API credential for audio transcription, caption generation, and image generation, and (optionally) adjust the model, language, image size, and quality
Upload email invoice attachments to Lexware and notify via Pushover
Quick overview This workflow watches an IMAP inbox for new emails, extracts each attachment, uploads the files to the Lexware Files API as vouchers, and sends a Pushover notification once the upload completes. How it works Triggers when a new email is received. The connection is established via IMAP. Extracts all email attachments and splits them into individual file items. Uploads each attachment to the Lexware API endpoint for file uploads, setting the file type to "voucher". Sends a Pushover notification confirming that the invoice file(s) were uploaded. Setup Configure IMAP credentials for the mailbox you want to monitor. Add an HTTP Bearer token credential for the Lexware API and ensure the token has access to upload files. Add Pushover API credentials, set your Pushover user key, and adjust the notification message if needed. The priority should be at least ‘normal’ in order to receive an active notification. Customization Use Gmail as optional trigger
WSend weekly blended ad performance reports with Meta, Google Ads, GA4 and OpenAI
Quick overview This workflow runs every Monday at 8am to pull the last 7 days of performance from Meta Ads, Google Ads, and GA4, calculate blended KPIs, generate an OpenAI-powered narrative summary, email an HTML report via Gmail, and post an internal update (and errors) to Slack. How it works Runs every Monday at 8am on a scheduled trigger. Fetches the last 7 days of spend and engagement metrics from the Meta Ads Insights API, campaign cost and conversion metrics from the Google Ads API, and conversions and revenue by channel from the GA4 Reporting API. Combines the three datasets and calculates blended KPIs including total spend, total conversions, total revenue, and ROAS. Sends the computed metrics to an OpenAI chat model to generate a 3–4 sentence client-friendly performance summary with one risk and one recommendation. Builds a simple HTML report containing the KPIs and AI summary. Emails the HTML report to the client via Gmail and posts a brief confirmation with spend and ROAS to a Slack channel. If the workflow fails, posts an error alert message to an ops Slack channel. Setup Configure authentication for the HTTP requests to Meta Ads (access token), Google Ads (OAuth/access
Manage Google and Trustpilot reviews with OpenAI and Slack
Quick overview This workflow runs hourly to fetch new Google Business Profile and Trustpilot reviews, deduplicates them, uses OpenAI via a LangChain agent to draft sentiment-aware replies, escalates negative reviews in Slack, and routes positive replies to Slack for approval before posting the reply back to Trustpilot. How it works Runs every hour on a schedule. Fetches the latest reviews from the Google Business Profile API and the Trustpilot API and combines the results. Deduplicates reviews by tracking previously seen review IDs in workflow static data and stops if there are no new reviews. Processes each new review and uses OpenAI (via a LangChain agent) to generate structured JSON containing sentiment, a draft reply, and an optional suggested resolution. Sends negative reviews to a Slack channel for the owner along with the suggested resolution. Sends positive draft replies to Slack for one-tap approval (with a 24-hour timeout) and, if approved, publishes the reply to the Trustpilot API. Sends a Slack alert to the ops channel if the workflow errors. Setup Configure authentication and replace placeholders for the Google Business Profile reviews endpoint (account and location) i
W
Recover abandoned Shopify carts with Gmail, WhatsApp, and Slack alerts
Quick overview This workflow listens for Shopify checkout creations, waits 15 minutes, checks whether the checkout converted into an order, and if not sends a recovery message via Gmail and WhatsApp, while reporting any workflow errors to a Slack channel. How it works Triggers in Shopify when a checkout is created. Waits 15 minutes to give the customer time to complete the purchase. Calls the Shopify Admin Orders API to check whether an order exists for the checkout token. Stops if an order is found, indicating the cart converted. If no order is found, compiles the customer email, phone, cart item summary, discount code, and recovery URL from the Shopify checkout data. Sends a personalized recovery email through Gmail and a recovery message through WhatsApp using the same discount code and checkout link. If the workflow errors at any point, posts the error details to Slack for operational alerting. Setup Connect your Shopify Admin credentials for the Shopify trigger and ensure it can receive the checkouts/create topic. Configure the HTTP request to your store by replacing YOUR_STORE (or ensuring the checkout payload provides domain) and add Shopify Admin API authentication for /adm
Register credential overwrites on startup with the n8n API
Quick Overview This workflow helps you set and maintain n8n credential overwrites by fetching credential schemas via the n8n REST API and registering overwrite values on every n8n startup using the credential overwrite endpoint. How it works Runs manually to collect your target credential type and n8n base URL for testing. Calls the n8n REST API to fetch the schema for the specified credential type so you can see which fields are available to overwrite. Triggers when n8n starts and sends a POST request to the credential overwrite endpoint to register the overwrite payload. Stores the overwrite JSON securely inside an HTTP custom auth credential and uses it as the request body to apply defaults that users cannot change in the UI. Setup Self-host n8n and set CREDENTIALS_OVERWRITE_ENDPOINT=creds-overwrite (and CREDENTIALS_OVERWRITE_PERSISTENCE=true if you run queue mode). Create an n8n API key with at least read permissions, add it as an n8n API credential, and set the correct base URL in the schema request. Enter the credential type name you want to overwrite (for example googleOAuth2Api) in the input fields used by the manual test. Create an HTTP Custom Auth credential that contains
WGenerate and score Google Maps leads with Gemini, Apify, and Google Sheets
Quick overview Youtube Video:https://youtu.be/NGruDecKxAg?si=ot9pj6IN4IoLstow This workflow takes a chat-based search request, scrapes matching businesses from Google Maps using Apify, scores and ranks them with Google Gemini, deduplicates against an existing Google Sheet by placeId, saves new leads to the sheet, and returns a formatted results message to the chat. How it works Receives a message from an n8n chat trigger containing the user’s Google Maps lead search request. Sends the request to Google Gemini to extract structured search parameters (business type, location, max results, and output mode). Calls an Apify Google Maps scraping actor with the extracted parameters and selects a clean set of lead fields from the results. Removes duplicate businesses based on Google Maps placeId and batches the remaining leads into a single list. Sends the lead list to Google Gemini to add a 0–100 score and short reason to each lead and returns them sorted by score. Checks the scored leads against existing rows in Google Sheets and filters out any placeId values that are already saved. Appends or updates the new leads in Google Sheets and returns a formatted ranked lead list back to the ch
Track data deletion requests from Gmail with Jira, BigQuery, and Slack
Quick Overview This workflow monitors a Gmail inbox for potential privacy/data deletion requests, classifies each email, creates the appropriate Jira issue, logs a minimal audit record to BigQuery, and alerts the team in Slack, with an optional Gmail confirmation draft for human review. How it works Triggers when a new email matching deletion-related keywords arrives in Gmail (or runs manually for testing). Loads shared configuration values like Jira project details, BigQuery destination, SLA window, Slack channel, and confidence threshold. Cleans the email text, extracts the requester address, classifies the request type (deletion/access/correction), and calculates an SLA due date with a confidence score. Creates a Jira task for the privacy team when the classification is confident, or creates a separate Jira task labeled for manual review when it is not. Inserts an audit row into Google BigQuery with metadata such as request type, confidence, received time, due date, and whether a Jira issue was created. Posts a Slack message to the configured channel about the routed request or the need for manual review. Creates a draft confirmation email in Gmail for the requester after a rout
Monitor Hostinger email DNS records weekly and send alert emails via SMTP
Quick Overview This workflow runs every Monday at 8am to check email-related DNS records (MX, SPF, DMARC, and DKIM) for all domains in your Hostinger account and sends an HTML alert email when it detects missing records, tracking prior results to highlight new breakage. How it works Runs every Monday at 8am and sets the notification email address used for alerts. Fetches the full domain list from Hostinger and processes each domain one by one. Retrieves the DNS zone for each domain from Hostinger and checks for active MX records plus valid SPF, DMARC, and DKIM TXT records. Compares the current results to the previous run stored in workflow static data to mark problems as new or ongoing. Builds an HTML email describing the missing records for any affected domain and sends the alert via SMTP/email credentials to the configured recipient. Setup Add your Hostinger API credentials for the steps that list domains and retrieve DNS zones. Configure your SMTP/email-sending credentials for the email node used to send alerts. Update the notification email address (and, if needed, the from/to fields) so alerts go to the right recipient. Review and adjust the DNS validation rules in the code st
Back up Hostinger Reach contacts and segments to Google Sheets daily
Quick Overview This workflow runs daily at 7am to back up Hostinger Reach contacts and segments into Google Sheets, upserting records into separate Contacts and Segments tabs and adding a last_synced_at timestamp for tracking. How it works Runs every day at 7am and sets the target Google Sheets URL plus the tab names for contacts and segments. Requests the first page of Hostinger Reach contacts and continues fetching additional pages until the last page is reached. Splits the returned contacts into individual records, maps key fields (including uuid and email), and adds a last_synced_at timestamp. Upserts the contact records into Google Sheets using uuid as the matching key. Fetches all Hostinger Reach segments, splits them into individual records, and adds a last_synced_at timestamp. Upserts the segment records into a separate Google Sheets tab using uuid as the matching key. Setup Add a Hostinger API credential for the Hostinger Reach nodes that list contacts and segments. Add a Google Sheets credential and ensure the Google Sheet is accessible to that account. Update the Google Sheets URL and the Contacts/Segments tab names in the configuration step. Ensure your Contacts and Seg
WHandle WhatsApp support chats with OpenRouter, Pinecone, and Gemini
Quick overview This template implements a WhatsApp support suite that logs inbound events to a dashboard API, routes conversations through an OpenRouter-powered AI agent with Pinecone RAG and memory, exposes a webhook for human outbound replies, and provides a webhook to summarize recent chats for handoff. How it works Triggers on WhatsApp Cloud API events and routes status updates (sent/delivered/read) to a dashboard API endpoint for storage. For inbound messages, looks up the contact in the dashboard API and normalizes the message into a consistent schema (sender, type, timestamp, and best-effort content). If the message contains media (image/video/audio/document), fetches the WhatsApp media URL, downloads the file, uploads it to the dashboard’s media endpoint, and attaches the resulting media URL and MIME type. Stores inbound messages and reactions in the dashboard API, then checks via the cases endpoint whether the sender already has an open case. If the inbound message is text and no open case is found, queries Pinecone as a tool (using Google Gemini embeddings), uses an OpenRouter chat model with conversation memory to draft a reply or create a new case via the dashboard API,
WCalculate court deadlines with Google Calendar, Outlook, and Clio
Quick overview This workflow receives a webhook with a trigger date and deadline rules, calculates court deadlines (skipping weekends and US federal holidays for business-day rules), then creates matching events in Google Calendar or Microsoft Outlook, creates high-priority tasks in Clio, logs each deadline to a Google Sheets audit sheet. How it works Receives a POST webhook request containing a matter ID, trigger date, optional rule set, and the target calendar platform. Validates the payload and stops early if the matter ID is missing or the trigger date is not in YYYY-MM-DD format. Calculates one deadline per rule using calendar-day or business-day offsets that skip weekends and US federal holidays. Creates a calendar entry for each deadline in Google Calendar (all-day) or Microsoft Outlook via Microsoft Graph (timed), depending on the requested platform. Creates a high-priority pending task in Clio for each deadline and links it to the provided Clio matter ID. Appends one audit row per deadline to the “Audit Log” tab in the OPS1 Compliance Log Google Sheet. Setup Configure the webhook URL in the system that triggers deadline creation and ensure it sends at least matter_id and t
Confirm and log WhatsApp restaurant orders with Groq and Google Sheets
Quick Overview This workflow triggers on incoming WhatsApp orders, uses Groq to extract items and quantities, validates them against a live Google Sheets menu, logs the result to an orders sheet, and replies to the customer with either a clarification request or a priced confirmation (with optional VIP owner alerts). How it works Triggers when a new WhatsApp message is received on your WhatsApp Business Cloud number. Sends the message text to Groq (Llama 3.3) to extract a structured list of ordered items and quantities. Reads the latest menu (item name, price, availability) from a Google Sheets “Menu” tab. Matches extracted items to the menu, checks availability, calculates line subtotals and the total price, and compiles any validation issues. If there are issues, replies to the customer on WhatsApp asking for a corrected order and appends a “needs_clarification” entry to the Google Sheets “Orders” tab. If the order is valid, appends a “confirmed” entry to the Google Sheets “Orders” tab and sends a WhatsApp confirmation with the item summary and total. If the confirmed total meets or exceeds the VIP threshold, sends a separate WhatsApp notification to the owner number. Setup Conne
Predict Salesforce deal escalation risk with Gemini and Slack alerts
Quick overview This workflow pulls open Salesforce opportunities and their last-30-days activities, uses Google Gemini to predict escalation risk per deal, then flags high-risk opportunities in Salesforce and notifies a Slack user. How it works Starts manually and fetches open opportunities and recent Salesforce Task activities from the last 30 days. Merges opportunities with their related activities and builds a per-deal context including amount, probability, type, activity list, and whether all activities are completed. Batches the deals and skips ones that have 100% probability and active/completed engagement, then waits briefly between remaining items to reduce API load. Sends each deal context to Google Gemini to classify risk (high/medium/low), identify specific risk flags, and return a one-line summary as JSON. Cleans and validates the Gemini response by stripping formatting, parsing JSON safely, and normalizing invalid risk levels to “unknown.” For deals marked as high risk, updates the Salesforce opportunity description with the risk details and sends a formatted alert message to a specified Slack user. Setup Add Salesforce OAuth2 credentials and ensure the workflow has ac
Detect revenue leakage with Salesforce, Google Sheets, Gemini, and Slack
Quick overview This workflow manually audits Closed Won Salesforce opportunities against billed amounts in Google Sheets, uses Google Gemini to analyze any revenue gap, then alerts a Slack user and writes an audit note back to the Salesforce opportunity. How it works Starts when you run the workflow manually. Fetches up to 20 Salesforce opportunities where the stage is "Closed Won" and processes them in batches with a short delay to reduce API pressure. Looks up matching billing rows in Google Sheets and totals the billed amount for the same Deal ID, then calculates the missing revenue versus the Salesforce Amount. For deals with a positive revenue gap, sends the discrepancy details to Google Gemini to classify severity and generate a root cause, recommendation, and Salesforce-ready audit note. Parses the Gemini JSON response and builds a formatted Slack message containing the deal, gap, severity, and recommended action. Sends the Slack alert and updates the Salesforce opportunity description with the audit note and the expected, billed, and missing amounts. Setup Add credentials for Salesforce OAuth2, Google Sheets OAuth2, Google Gemini (PaLM) API, and Slack OAuth2. In Salesforce,
Monitor ride surge events and analyze ride errors with Sheets, Slack and Gemini
Quick overview This workflow pulls ride events and error records from Google Sheets, detects surge pricing and long waits, and notifies via Slack. For error records, it uses Google Gemini with real-time traffic and weather API lookups to diagnose the issue and send recommended actions to Slack. How it works Runs manually and reads ride records from a Google Sheets spreadsheet. Processes the rows one by one with a short delay and routes each record based on whether its type is an event or an error. For event records, checks if the ride price is more than 1.5× the normal price and the wait time is over 10 minutes. If surge conditions are met, sends a surge and delay notification to Slack and records a surge-alert log entry. If surge conditions are not met, records a normal “no alert needed” log entry. For error records, structures the ride and error context and asks Google Gemini to generate an incident summary, probable cause, and recommended actions, calling traffic and weather APIs as needed. Parses the Gemini response into JSON and posts the formatted error report to Slack. Setup Connect Google Sheets OAuth credentials and set the correct spreadsheet and sheet tab in the Google S
WSend gold-silver ratio opportunity alerts with GoldAPI and Gmail
Quick overview This workflow fetches live gold (XAU) and silver (XAG) prices from GoldAPI.io, calculates the gold-silver ratio, evaluates it against buy/hold thresholds, and sends a formatted opportunity alert email via Gmail. How it works Starts manually and loads configuration values such as the GoldAPI.io key, currency, alert email, and ratio thresholds. Requests the latest gold and silver prices from GoldAPI.io and extracts the numeric price values. Combines both price results and calculates the gold-silver ratio. Compares the ratio to the configured thresholds to decide whether to signal “buy silver”, “buy gold”, or “hold”. Generates a timestamped alert message with an insight and interpretation for the selected signal. Sends the full report (prices, ratio, signal, and explanation) to the configured recipient using Gmail. Setup Create a GoldAPI.io account, copy your API key, and paste it into the workflow configuration value used by the GoldAPI.io requests. Connect a Gmail OAuth2 credential in n8n and ensure the workflow can send email from your Gmail account. Set the recipient email address, currency code (for example, INR), and your buy-silver and buy-gold ratio thresholds i
Classify documents and extract invoice data with LDXhub AnalyzeDoc and Google Sheets
Quick overview This workflow collects uploaded PDFs or images, classifies each document type using LDXhub AnalyzeDoc, and routes it accordingly; invoices get high-detail field extraction and are appended as a new row in Google Sheets. How it works Receives a file upload through an n8n form for a PDF, JPG, or PNG business document. Sends the file to LDXhub AnalyzeDoc (low-detail) to classify it as invoice, receipt, business_card, contract, blank, or other. Parses the returned JSON and routes the execution based on the detected document_type. For invoices, reattaches the original uploaded file and runs LDXhub AnalyzeDoc (high-detail) to extract key invoice fields in structured JSON. Flattens the extracted fields and appends them as a new row in a selected Google Sheets worksheet. For receipts, business cards, and other types, sends the item to placeholder routes where you can add your own processing. Setup Create an LDXhub account, generate an API key, and configure an LDXhub API credential in n8n for both AnalyzeDoc steps. Connect a Google Sheets OAuth2 credential and select the target spreadsheet and worksheet in the append step. Ensure the first row of your sheet contains headers
Generate executive decision briefings from APIs with OpenAI and Google Sheets
Quick overview This workflow runs daily or via an on-demand webhook to pull financial metrics, operational KPIs, and market quotes via HTTP APIs, then uses OpenAI to detect anomalies and generate an executive briefing that is POSTed to a dashboard endpoint and logged to Google Sheets. How it works Runs on a daily schedule or receives a POST request via a webhook to start an executive briefing run with a configurable lookback period. Fetches financial metrics, operational KPIs, and market data in parallel from three HTTP API endpoints and continues even if one source fails. Merges and normalizes the three datasets into a single snapshot, marking missing sources as unavailable so downstream steps keep a consistent structure. Uses OpenAI to analyze the snapshot for anomalies, unusual trends, and data gaps, returning a severity-scored findings JSON. Uses OpenAI again to turn the anomaly findings and raw metrics into a structured executive briefing with a health score, risks, opportunities, and recommended actions. Formats a final JSON payload and delivers it by POSTing to your dashboard endpoint and appending a summary row to a Google Sheets tracker. If the run was triggered by the web
Migrate visible product categories from Lightspeed to Shopify via GraphQL
Quick Overview This workflow runs manually to migrate visible category data from Lightspeed to Shopify by creating Shopify collections via the Admin GraphQL API, adding URL redirects from old category paths, and publishing the new collections to all Shopify publication channels. How it works Starts when you manually execute the workflow in n8n. Fetches all publication channels from your Shopify store using the Shopify Admin GraphQL API. Retrieves up to 250 categories from the Lightspeed API and splits the response into one item per category. Filters the list to only categories marked as visible in Lightspeed. For each visible category, creates a Shopify collection with title, handle, description, SEO fields, and an optional image. Creates a Shopify URL redirect from the original Lightspeed category URL path to the new Shopify /collections/{handle} URL. Publishes the created collection to all fetched Shopify publication channels and stops with an error if any Shopify mutation returns userErrors. Setup Add a Shopify Admin API access token as an HTTP Header Auth credential (header name X-Shopify-Access-Token) and assign it to the Shopify GraphQL requests. Add your Lightspeed API key a
Generate and email Stripe invoice PDFs with PDFBolt and Gmail
Quick overview This workflow triggers on successful Stripe invoice payments, formats the invoice data for a PDFBolt template, generates a PDF invoice, and emails it to the customer through Gmail. How it works Triggers when Stripe emits an invoice.payment_succeeded event for a paid invoice. Extracts the Stripe invoice object, formats amounts, and maps customer and line-item fields into templateData for PDFBolt. Generates a PDF from a published PDFBolt template using the Direct endpoint and returns the file as binary data. Sends the generated PDF as an attachment in a Gmail email to the customer’s email address from the Stripe invoice. Setup Connect your Stripe account and ensure the trigger can receive invoice.payment_succeeded events. Add your PDFBolt API key from https://app.pdfbolt.com/api-keys, publish an invoice template in PDFBolt, and paste its Template ID into the PDFBolt node. Connect your Gmail account and adjust the email subject or body text if you want different wording or branding. Requirements Stripe account connected in n8n PDFBolt account and API key Published PDFBolt invoice template Gmail account connected in n8n Customization Use your own PDFBolt Template ID Matc
Ping IndexNow when new blog posts are published from your RSS feed
Quick overview This workflow polls your blog’s RSS feed for newly published posts and sends each new URL to the IndexNow API, helping Bing and other IndexNow-enabled search engines pick up updates quickly. How it works Polls the specified RSS feed every 15 minutes to detect new blog posts. Sets your site host and IndexNow key for the request payload. Sends a POST request to the IndexNow API with the new post URL, your key, and the key file location on your domain. Checks the HTTP response status code to determine whether the ping succeeded. Routes successful runs to a “Pinged OK” endpoint and failures to a “Ping Failed” endpoint for optional downstream notifications. Setup Obtain an IndexNow key and host it as a text file at https:///.txt containing the key. Update the RSS feed URL in the RSS trigger (for example, https://your-domain.com/feed/). Activate the workflow, publish a test post, and check the execution log — a 200 or 202 response from IndexNow confirms the ping was received successfully.
WDraft personalized pre-demo messages from demo bookings with Twain, Gmail, and Slack
Quick overview This workflow triggers on new demo bookings (webhooks or Google Calendar), uses Twain to research the prospect and generate a personalized pre-demo sequence plus an AE brief, drafts the email in Gmail, optionally queues LinkedIn steps in HeyReach, and posts everything to Slack for review. How it works Triggers when a demo booking is received via a webhook (generic, Chili Piper, or HubSpot) or when a new Google Calendar event is created. Normalizes the incoming booking payload into a consistent format, filters to demo meetings only, and de-duplicates repeat bookings across executions. If no LinkedIn URL is provided but an email exists, looks up a LinkedIn profile URL using Findymail and merges it back into the contact. If a usable work email or LinkedIn URL is available, calls the Twain API to generate contact research, an AE pre-demo brief, and a multi-step outbound sequence; otherwise it posts a “skipped” notice to Slack. Builds an email-ready draft (subject and HTML body) plus previews for email and LinkedIn steps from the Twain output. If a work email exists, creates a Gmail draft and posts the brief and draft preview to Slack (or posts a “no draft created” messag