Code workflows
1,006 results — all source-linked n8n references
Route rental payment and receipt messages with Telegram and OpenAI GPT-4.1
Quick overview This demo workflow listens for Telegram rental messages, routes receipt-related commands, uses OpenAI to classify payments, costs, and booking summaries, then replies with parsed details and a sample receipt flow. How it works Triggers when a new Telegram message is received. Routes the message into one of four paths: full /receipt command, receipt request, receipt date reply, or general rental tracking. If a full /receipt command is provided, it parses client, property, stay dates, amount, and transaction details and replies in Telegram with the extracted fields. If the user sends a receipt request, it looks up the last saved payment for that Telegram chat and either prompts the user for stay dates or returns an error if no payment is stored. If the user replies with stay dates during a pending receipt flow, it combines those dates with the stored payment to build receipt details and replies with either a “ready to generate” summary or an error message. For all other messages, it sends the text to OpenAI to classify it as payment, cost, or booking summary, normalizes the JSON result, and replies in Telegram with the parsed output. When a payment is detected, it extr
Review workflow JSON for risks and best practices with Groq (Llama 3.3)
Quick overview This workflow exposes a webhook that accepts an exported n8n workflow JSON, runs static validation and risk checks, then uses Groq (Llama 3.3 70B) via an AI agent to return a structured JSON review with metrics, risks, and best-practice recommendations. How it works Receives a POST request via a webhook containing a workflow object with exported n8n workflow JSON. Validates the payload structure and analyzes the workflow to generate metrics and findings such as orphan nodes, dead ends, missing error handling, placeholder credentials, deprecated nodes, and documentation gaps. Routes valid analyses to a Groq-powered AI agent that explains each finding (why it matters, risk, business impact, and best-practice fix) and formats the response as structured JSON. Routes invalid or malformed inputs to a formatter that returns a consistent { success: false, error } JSON response. Responds to the original webhook request with the final JSON analysis. Setup Add a Groq API credential in the Groq Chat Model node. You can generate a free API key at console.groq.com if you don't have one yet. Activate the workflow and copy the webhook URL from the Webhook trigger. This is the endpoi
WReply to Instagram comments with Groq, Telegram approval, and Google Sheets logging
Quick Overview This workflow monitors new Instagram comments, generates a draft reply with Groq (OpenAI-compatible chat completions), sends it to Telegram for YES/NO approval, and logs the decision in Google Sheets before optionally posting the approved reply back to Instagram. How it works Runs every 10 minutes, reads existing comment IDs from Google Sheets, then fetches your 10 most recent Instagram media items and their comments via the Instagram Graph API. Filters out comments made by your own Instagram account and limits processing to recent comments. Skips any comment already logged in Google Sheets, and sends new comments (with the post caption as context) to Groq to generate a short draft reply. Sends the draft reply to a Telegram chat for approval and appends a “pending_review” row to Google Sheets with the Telegram message ID for tracking. Runs every 3 minutes, polls the Telegram Bot API for new updates, and keeps an offset so only new messages are processed. For Telegram messages that are replies to an approval request, matches the replied-to message ID to the pending row in Google Sheets and routes the decision. If the reviewer replies YES, posts the draft as an Instagr
Generate workflow audit docs from JSON with Claude Sonnet and Notion
Quick overview This workflow collects an exported n8n workflow JSON via an n8n Form, audits it for common reliability and security issues, uses Anthropic Claude to draft a business summary and technical report, and then creates a formatted documentation page in Notion. How it works Receives a form submission with a workflow JSON file, client name, and a Notion parent page ID. Parses and validates the uploaded JSON to confirm it contains nodes and connections and extracts the workflow metadata. Analyzes the workflow graph to determine execution order, detect cycles and unreachable nodes, and generate a scored list of audit findings. Sends the audit context to Anthropic Claude (Sonnet) to generate a business-facing workflow summary and a developer-facing audit report. Converts the generated text into Notion blocks, including an audit score callout and optional warnings for cycles or unreachable nodes. Creates a new Notion page under the provided parent page and appends the blocks in batches with a short wait to avoid Notion rate limits. Setup Import the workflow and connect your Anthropic account credential to the Claude Sonnet node. No additional configuration is needed on the Anthr
Sync Etsy customers with Meta custom audiences using hashed emails
Quick overview This workflow runs daily to fetch recent Etsy receipt emails via an Etsy Shop Operations sub-workflow, normalizes and SHA-256 hashes the emails, and either previews the hashed payload or uploads it to a Meta Custom Audience using the Meta Graph API. How it works Runs every day on a schedule. Sets sync parameters (lookback window, maximum receipts, dry-run mode, Meta audience ID, and API version). Requests recent Etsy receipt records from a connected Etsy Shop Operations workflow and extracts buyer/payment email addresses. Normalizes, deduplicates, and SHA-256 hashes the email addresses to build a Meta Custom Audience upload payload. If dry-run is enabled, returns counts and a small sample of hashes for verification. If dry-run is disabled, sends the hashed EMAIL payload to the Meta Graph API endpoint for the specified Custom Audience. Setup Configure and connect the “Get Etsy customer receipts” execute-workflow step to an Etsy Shop Operations (PRO) workflow that returns receipt records including buyer/payment emails. Create or choose a Meta Custom Audience and paste its ID into the configuration values. Add a Meta access token to the HTTP header auth for the upload r
Generate daily Etsy sales and ledger reports via Shop Operations API
Quick overview This workflow runs daily to pull recent Etsy receipts and payment-account ledger entries via a linked sub-workflow, then aggregates sales metrics by currency and fee totals by ledger type and outputs a consolidated report object for downstream accounting or BI tools. How it works Runs every day on a schedule. Sets the reporting window and maximum record count used for all Etsy queries. Calls a separate Etsy Shop Operations workflow to fetch receipts for the configured date range. Calls the same Etsy Shop Operations workflow to fetch payment-account ledger entries for the same date range. Aggregates receipts into per-currency totals (orders, revenue, shipping, tax, discounts, and average order value) and groups ledger amounts by ledger type. Outputs the final report payload (including summaries plus the raw receipts and ledger entries) for use in other steps like saving to a database or sending by email. Setup Set up Etsy OAuth credentials in the workflow that performs the Etsy API calls (the Etsy Shop Operations sub-workflow). In both Execute Workflow steps, select the Etsy Shop Operations workflow to run by filling in the referenced workflow ID. Update the reporting
Manage Etsy OAuth 2.0 tokens and API headers between workflows
Quick Overview This workflow manages Etsy OAuth 2.0 (PKCE) authorization in n8n, stores access and refresh tokens in workflow static data, refreshes tokens when needed, and returns ready-to-use Etsy API request headers to other workflows via an Execute Workflow call. How it works Runs either manually to start authorization, via a webhook callback from Etsy after consent, or when another workflow requests a token. Loads the Etsy app configuration (client ID, shared secret, redirect URI, scopes) and routes the run to start authorization, handle the callback, or return an access token. When starting authorization, generates a PKCE verifier/challenge and returns an Etsy authorization URL while storing the pending state for validation. When Etsy redirects to the callback webhook, validates the returned state and authorization code and then exchanges the code for tokens using the Etsy OAuth token endpoint. Stores the authorized access and refresh tokens (with expiry timestamps) in n8n workflow static data and returns a confirmation response to the callback request. When another workflow requests a token, loads the stored refresh token, refreshes the access token with Etsy if it is missin
WCapture and log email trade instructions with Gmail, OpenAI, and Google Sheets
Quick overview This workflow polls Gmail for emails with the subject “Trade Instruction”, uses OpenAI Chat Completions to extract trade fields from the email body, logs valid and failed extractions to separate tabs in Google Sheets, and sends confirmation and ops alert emails via Gmail. How it works Triggers every minute by polling Gmail for new messages matching the query subject:"Trade Instruction". Extracts the email body, sender address, subject, and message/thread IDs and generates a trade reference and timestamps. Sends the email body to OpenAI (Chat Completions) to return a JSON object containing asset, ticker, action, quantity, price, client, and notes. Parses the returned JSON, validates that asset is present and quantity is greater than zero, and marks the result as valid or failed with a reason. Appends valid trade instructions to the “Valid Trades” tab in Google Sheets, or appends failures (including a snippet and error reason) to the “Failed Trades” tab. For valid trades, replies to the original email in Gmail with a receipt confirmation and emails the ops team a capture notification, and for failed trades, emails the ops team a manual-review alert with the original em
Create SEO blog posts from YouTube videos with Gemini and Google Docs
Quick overview Submit a YouTube URL and get a publish-ready SEO blog post. Three Gemini agents research the video, write the article, and score it. Articles scoring 7+ auto-publish to Google Docs. Lower scores route to Telegram for review. How it works The workflow starts when a POST request hits the webhook with a YouTube URL, optional target keyword, and tone. A Code node extracts the video ID and validates the URL format, then an HTTP Request node calls YouTube Data API v3 to pull the video title, description, channel name, and tags. Three Basic LLM Chain nodes run in sequence, each powered by a Google Gemini Flash sub-node connected via the native ai_languageModel port. The first chain (Research Agent) receives the video context and returns a structured JSON brief containing an SEO title, four H2 headings, primary keyword, secondary keywords, key insights, target audience, and a content angle. A Code node parses this output with a JSON fallback in case Gemini adds unexpected formatting. The second chain (Writer Agent) takes the research brief and writes a complete 1,000–1,400 word blog post following strict rules: flowing paragraphs over bullet lists, primary keyword used 3–5 t
Send portfolio contact form notifications and confirmations with Gmail
Quick overview This workflow receives portfolio contact form submissions via a webhook, normalizes the fields, generates branded HTML emails, and uses Gmail to send an admin notification plus an automated confirmation to the visitor before returning a success JSON response to the website. How it works Receives a POST request from your website contact form via an n8n webhook. Normalizes the incoming payload into consistent fields (name, email, subject, message, timestamp). Builds two branded HTML emails and subjects: one for the admin notification and one for the visitor confirmation. Sends the admin notification email with the submitted details using Gmail. Sends the visitor a confirmation email using Gmail. Returns a 200 JSON response (success/message) to the website so the form can show a confirmation. Setup Connect a Gmail OAuth2 credential for the two Gmail send steps. Replace the hardcoded admin recipient address in the admin notification email step. Copy the Production Webhook URL generated by your automation platform and configure your website's contact form to send a POST request to this endpoint whenever a user submits the form. Ensure that the request includes all the req
Capture and deduplicate inbound leads with webhooks and Google Sheets
Quick overview Capture inbound leads via webhook, validate and sanitize the data, deduplicate against Google Sheets, and store only clean leads ready to feed an AI-powered email/SMS nurture sequence. How it works Webhook receives the lead POST request from any form builder or landing page. Validation Missing email or phone returns a 400 and stops execution. Sanitize & normalize Trims whitespace, lowercases email, normalizes phone to international format, sets lead stage to 1, fills defaults for optional fields. Dedupe check Looks up the email in Google Sheets; flags duplicates safely even when the sheet returns zero rows. Duplicate → 200 "Already Registered", execution ends. New lead → appended to Sheets, 200 "Lead Accepted" returned. Setup Import all 4 workflows they share one Google Sheet. Create a sheet with these exact headers: Name, Email, Phone, Stage, Next Followup At, Has Replied, Lead Source, Service of Interest, SMS Consent Connect Google Sheets OAuth2 in the Lookup and Append nodes; paste your Sheet ID/tab into the 🔧 CONFIG nodes. Copy the webhook URL into your form builder. Map fields to: name, email, phone, lead_source, service_of_interest, sms_consent Requirements Go
Classify workflow errors with Claude and deduplicate Jira and Slack alerts
Quick overview This global error-handling workflow classifies n8n execution failures with Anthropic Claude, deduplicates incidents in Jira using a hash label, and posts a detailed alert to Slack with links to the affected execution and Jira issue. How it works Triggers whenever any n8n workflow execution or trigger fails (when set as the instance Error Workflow). Normalizes the error event into a consistent payload that includes workflow details, error message, truncated stack trace, and an execution log URL. Sends the normalized payload to Anthropic Claude to return a structured JSON classification (category, severity, root cause, recommended action, and transient flag). Parses the classification, falls back to an UNKNOWN classification if the LLM response is invalid, and generates a deduplication hash used to group similar errors. Searches Jira for an open issue in the configured project that already has the matching deduplication label. If an open issue exists, appends a recurrence comment with the latest execution details; otherwise, creates a new Jira Bug with labels, priority, and a full incident description. Builds a Slack Block Kit message summarizing the incident and sends
WExtract and validate invoice PDFs with OpenAI, Google Sheets, and Gmail
Quick overview This workflow collects an invoice PDF via an n8n Form, extracts text from the PDF, uses OpenAI to convert it into structured invoice JSON, logs invoice headers and line items to Google Sheets, validates totals, and emails a formatted extraction report via Gmail. How it works Receives an invoice submission through an n8n Form that includes the uploader’s name, email address, currency, notes, and a PDF file. Extracts text content from the uploaded PDF. Sends the extracted text to OpenAI (Chat Completions) to return invoice fields and all line items as a strict JSON object. Parses and validates the returned JSON, enriching it with the form metadata and stopping the run if key fields (like invoice number or line items) are missing. Appends a single invoice “header” row to the Invoices tab in Google Sheets. Splits the extracted line items, adds per-line metadata and a unique key, and appends each line item as a row to the Line Items tab in Google Sheets. Aggregates all line items, verifies that their summed totals match the invoice total within a tolerance, builds an HTML report, and emails it to the submitter via Gmail. Setup Add an OpenAI API credential and ensure the O
Generate an FAQ MP3 library from form input with OpenAI TTS, Google Drive, Sheets and Gmail
Quick overview This workflow collects up to five FAQ questions and answers from an n8n Form, converts each entry to an MP3 using OpenAI text-to-speech, uploads the files to Google Drive, logs links in Google Sheets, and emails a summary with listen and download links via Gmail. How it works Receives an n8n Form submission containing the requester’s email, a FAQ category, and up to five question-and-answer pairs. Splits the submitted FAQ pairs into individual items, generating a TTS script and a safe MP3 filename for each valid question and answer. Calls the OpenAI Audio Speech API (tts-1) to generate an MP3 file for each FAQ script. Uploads each generated MP3 to a specified Google Drive folder. Builds Google Drive view and direct-download URLs for each uploaded file and appends the FAQ details and links to a Google Sheets tab. Aggregates all processed FAQs into a single HTML summary and sends it to the submitter via Gmail with listen and download links. Setup Add an OpenAI API credential for the HTTP request to the OpenAI Audio Speech endpoint. Create (or choose) a Google Drive folder for the audio files, connect Google Drive OAuth2, and replace YOUR_AUDIO_FOLDER_ID with the target
WLog Strava zone 2 and 5K test runs to Google Sheets
Quick overview This scheduled workflow pulls your latest running activities from Strava, classifies them as Zone 2 runs or 5K tests based on pace and distance, and writes the formatted results into specific cells in a Google Sheets training log while tracking processed activity IDs. How it works Runs on a daily schedule. Fetches recent activities from the Strava API for the authenticated athlete. Processes each activity to calculate pace (min/km) and routes it into “Zone 2” or “Test Run” based on sport type, duration, pace, and distance rules. Formats the selected activities into sheet-ready fields (date, pace string, moving time, and distance) and labels them as ZONA 2 or TEST 5KM. Reads the target Google Sheets range to find the next available slots and checks an “IDs Registrados” list to avoid reprocessing activities. Updates Google Sheets with the activity details in the appropriate cycle columns and appends new Strava activity IDs to the “IDs Registrados” cell. Setup Connect your Strava OAuth2 credentials and ensure the athlete has permission to read activities. Connect your Google Sheets OAuth2 credentials and update the spreadsheet URL/ID and sheet (tab) selection used for r
Enrich CRM contacts in Google Sheets with Tomba firmographic data
Quick overview This workflow watches a Google Sheets contacts list for new rows and enriches each contact using Tomba to find a likely email address, company firmographics, and a phone number, then writes the enriched fields back to the same spreadsheet. How it works Triggers when a new row is added to a specified Google Sheets worksheet (polled every minute). Processes new contacts one at a time to control throughput. Uses Tomba to find an email address for the contact based on the provided domain, company, and name. Uses Tomba to enrich the company with firmographic details such as industry, company size, revenue, and location. Uses Tomba to look up a company phone number from the contact’s domain. Combines the enrichment results into a single contact record and sets a status like “Enriched” or “Not Found.” Updates the matching row in Google Sheets with the enriched Email, Phone, Industry, Company Size, Revenue, Country, and Status fields. Setup Connect Google Sheets credentials and select the target spreadsheet and worksheet to monitor. Add Tomba API credentials to each Tomba step used for email, company, and phone enrichment. Ensure your Google Sheet includes the destination co
Track and notify lead callbacks with Tomba, Google Sheets, and Slack
Quick overview This workflow receives new lead details via a webhook, looks up a company phone number with Tomba using the lead’s domain, updates a Google Sheets lead tracker, and sends a formatted callback alert to a Slack channel. How it works Receives lead data in a POST webhook request. Processes incoming leads in batches to handle multiple items safely. Uses Tomba to find a phone number for each lead based on the provided company domain. Formats the lead details and enrichment results into tracker fields and a Slack-ready message. Updates the matching lead row in Google Sheets (matched by Domain) with the phone, status, and “Slack Notified” flag. Posts the callback alert message to a selected Slack channel and continues until all leads in the batch are handled. Setup Configure the source system to send lead payloads to the workflow’s webhook URL (path: /GHL) with fields like Full name, Email, Company name, and Company domain. Add your Tomba API credentials to enable phone lookup by domain. Connect your Google Sheets credentials and set the target spreadsheet and sheet, ensuring columns like Domain, Phone, Status, and Slack Notified exist. Connect your Slack credentials and cho
BCWScrape Hacker News hiring threads with OpenAI GPT-4o-mini and Airtable
Quick overview This workflow manually runs a scraper that finds the latest Hacker News “Ask HN: Who is hiring?” thread via the Algolia HN Search API, pulls each job comment from the Hacker News Firebase API, uses OpenAI to structure postings into fields, and saves the results to Airtable. How it works Starts when you manually execute the workflow. Queries the Algolia Hacker News Search API for recent “Ask HN: Who is hiring?” stories and keeps only the relevant thread metadata. Filters the results to the most recent thread (created within the last 30 days) and fetches the full thread from the Hacker News Firebase API. Iterates through the thread’s comment IDs, fetching each individual job comment from the Hacker News Firebase API. Extracts and cleans the job text to remove HTML/entities and normalize links and whitespace. Sends the cleaned text to OpenAI (GPT-4o-mini) to extract a structured JSON record (company, title, location, type, salary, description, and URLs). Creates a new record in Airtable for each structured job posting. Setup Add an Airtable credential and set the target base and table in the Airtable create step. Add an OpenAI credential for the GPT-4o-mini chat model.
WSend daily SEO digest from Google Search Console to Discord with heartbeat alerts
Quick overview This workflow runs daily to pull Google Search Console performance data, log it to Google Sheets, send a daily SEO digest to Discord with day-over-day deltas, and ping an external heartbeat endpoint; if any step errors, it immediately pings the heartbeat service’s /fail endpoint. How it works Runs every day at 08:00 on a schedule trigger. Queries the Google Search Console Search Analytics API for query-level data from two days ago. Aggregates the results into totals (clicks, impressions, average position) and the top queries. Appends the day’s metrics to Google Sheets and reads the sheet to fetch the previous day’s row for comparison. Calculates percentage changes vs yesterday and sends a formatted SEO digest to Discord, including a warning when clicks drop sharply. Posts a success ping with the key metrics to an external heartbeat service (for example, checkilo or Healthchecks.io) so missing runs can be detected. If any node throws an error, an error-triggered branch posts a /fail ping to the heartbeat service with the error message and failing step. Setup Add a Google OAuth2 credential with the https://www.googleapis.com/auth/webmasters.readonly scope and replace t
Send portfolio risk reports from Google Sheets with OpenAI and Gmail
Quick overview This workflow collects a portfolio request via an n8n Form, loads holdings from Google Sheets, calculates portfolio risk and concentration metrics, generates an HTML risk narrative with OpenAI, then emails the full report via Gmail and appends an audit record back to Google Sheets. How it works Receives a portfolio analysis request from an n8n Form containing the investor details, base currency, and a Google Sheet ID. Reads all holdings from the provided Google Sheets document (Portfolio tab) and bundles the rows into a single portfolio dataset. Calculates market value, allocations, sector and asset-class breakdowns, P&L, concentration flags, and a 0–100 risk score. Sends the computed portfolio summary, breakdowns, risk flags, and holdings to OpenAI to generate a structured risk report in HTML. Builds a branded HTML email that includes the AI narrative plus sector and top-holdings tables and a concentration alert banner. Sends the HTML risk report to the investor via Gmail and appends a summary row to a Google Sheets “Analysis Log” audit sheet. Setup Create a Google Sheet with a tab named “Portfolio” and headers: ticker, company, sector, asset_class, quantity, avg_bu
Build hospitality lead lists from Booking.com using Apify and Google Sheets
Quick Overview This workflow uses Apify and Google Sheets to find accommodation leads from Booking.com, enrich them with Google Maps contact details, discover official websites via Google Search, scrape additional contacts from those sites, and then append the finalized partner list to a Google Sheets spreadsheet. How it works Manually triggers and sets the destination, maximum number of results, and property type to search. Runs the Apify Booking Scraper actor for the configured destination and retrieves the Booking.com dataset results. Maps each Booking.com result into a normalized lead record, using Booking trader details (when available) for initial email and phone fields. Runs the Apify Google Maps with Contact Details actor for leads missing email and merges any найден emails, phones, websites, and social links into the lead records. For leads still missing both email and website, runs the Apify Google Search Scraper actor to find an “official website” candidate and assigns the best non-OTA domain. Scrapes those candidate websites with the Apify Contact Info Scraper actor to extract emails/phones/socials and merges the results into the final lead rows. Appends the finalized l
WSummarize unread Gmail into a daily Slack digest with Claude
Quick overview This workflow runs on a daily schedule, pulls your unread Gmail from the last 24 hours, and uses Anthropic Claude to sort and summarize it by Gmail category — then posts a clean, triage-ready digest to a Slack channel so you can scan your inbox at a glance. How it works Runs automatically on a daily schedule (default 8am). Fetches up to 50 unread emails from Gmail that arrived in the last 24 hours. A Code node combines them into a single prompt block, tagging each message with its Gmail category (Primary, Promotions, Social, Updates, Forums) and flagging multi-message threads. Anthropic Claude turns that into a concise, Slack-ready digest: active threads flagged at the top, Primary mail listed individually with a needs-reply note, and Promotions/Social condensed to a single count. A Code node extracts the summary text from Claude's API response. The digest is posted to your chosen Slack channel. Setup Connect a Gmail OAuth2 credential to the Gmail node, and adjust the search query (e.g. is:unread newer_than:1d) or 50-email limit if needed. Add your Anthropic API key as an HTTP Header Auth credential named x-api-key, used for requests to https://api.anthropic.com/v1/m
Send weekly narrative client reports with Google Sheets, Claude, and Gmail
Quick overview This workflow runs every Friday at 9:00 AM, pulls active client status data from Google Sheets, uses Anthropic Claude to generate a narrative weekly report with structured HTML and plain text output, and sends the finished report to each client via Gmail. How it works Runs every Friday at 9:00 AM on a schedule trigger. Reads all client rows from a specified Google Sheets document. Filters out paused/inactive or incomplete rows, extracts any “Metric:” columns, and builds a reporting week label for each client. Sends each client’s normalized data to Anthropic Claude to write a 3–4 paragraph narrative report and return JSON containing an email subject plus HTML and plain-text bodies. Emails the generated HTML report to each client’s email address using Gmail. Setup Create a Google Sheet with the required columns (at minimum “Client Name” and “Client Email”) and optional “Status” plus any “Metric:” columns you want included. Add Google Sheets OAuth2 credentials in n8n and replace the placeholder Sheet ID in the Google Sheets read step. Add an Anthropic credential for the Claude chat model used to generate the structured report. Add Gmail OAuth2 credentials and confirm th
CScore and route inbound leads with Claude, Airtable, Slack, and Gmail
Quick overview This workflow receives inbound form leads via a webhook, normalizes the submission, optionally scrapes the lead’s website with Jina AI Reader, and uses Anthropic Claude to score and summarize the lead. It logs results to Airtable, posts a Slack alert, and creates a Gmail draft for hot leads. How it works Receives a POST webhook when a new lead submission comes in and immediately returns a JSON receipt response. Normalizes the incoming payload (Typeform, Tally, JotForm, or custom JSON) into consistent lead fields like name, email, company, website, and message. If a website is provided, fetches up to 2,000 characters of page content using Jina AI Reader and attaches it to the lead. Sends the lead details and scraped content to Anthropic Claude to produce structured JSON including a score, tier (hot/warm/cold), red flags, an enriched summary, and a first-reply draft. Builds a formatted Slack message and prepares a complete lead record (including routing flags) from the AI output. Creates a new record in Airtable and posts the lead alert to a Slack channel. If the lead is classified as hot, creates a Gmail draft using the generated first-reply text. Setup Copy the webho