Slack Workflows
1.961 Ergebnisse — 383 herunterladbare Workflow-Dateien, 1.578 quellenverknüpfte n8n-Referenzen
Generate SEO Articles from Search Queries to WordPress with Browseract
On manual run, scrapes search queries with BrowserAct, an OpenRouter agent writes SEO articles, publishing them to WordPress and notifying Slack.
Auto Post Curated Remote Jobs to Slack with Browseract and OpenRouter
On a schedule, scrapes remote job listings with BrowserAct, an OpenRouter agent curates them, and posts selections to Slack.
Monitor Clutch Categories for New Agencies to Slack with Browseract and Gemini
On a schedule, scrapes Clutch categories with BrowserAct, an OpenRouter agent identifies new agencies, logging them to Google Sheets and notifying Slack.
Track competitor pricing and features from BrowserAct to Google Sheets
On a schedule, scrapes competitor pricing and features with BrowserAct, an OpenRouter agent structures the data into Google Sheets, and alerts Slack.
Track Brand Visibility on Perplexity and ChatGPT with Browseract & OpenRouter
On a schedule, queries Perplexity and ChatGPT via BrowserAct, an OpenRouter agent assesses brand visibility, and posts findings to Slack.
Repurpose White Papers from Urls to LinkedIn PDFs and Blog Posts with Browseract
On manual run, reads white-paper URLs from Google Sheets, scrapes them with BrowserAct, and an OpenRouter agent generates blog posts and LinkedIn PDFs via APITemplate.io, sharing via Slack.
Scrape industry growth signals from BrowserAct to Slack reports
On a schedule, scrapes industry growth signals with BrowserAct, an OpenRouter agent summarizes them, and posts reports to Slack.
Pull New Ranked Keywords to Google Sheets with Dataforseo & Get a Slack Message
On a schedule, pulls newly ranked keywords from DataForSEO into Google Sheets and posts a summary to Slack.
AI-powered supply chain monitoring and disruption management system
On a schedule, fetches supply chain data and an OpenAI agent detects disruptions, routing alerts via Slack and email.
Notify on server restarts with Discord, Telegram, and Slack alerts
Quick overview This workflow triggers when the n8n instance starts, checks recent executions via the n8n API for unfinished runs, summarizes which workflows are affected, and posts a restart and incident summary to Discord and Telegram (with an optional Slack message). How it works Triggers when the n8n instance initializes (server restart/startup). Sets runtime variables (restart timestamp, lookback window, and maximum executions to fetch) and retrieves recent executions from the n8n API. Filters executions to those that are still unfinished and started within the configured lookback window. Groups the filtered executions by workflow ID, counts how many are affected per workflow, and sorts them by highest count. Builds formatted Discord, Slack, and Telegram messages that include the restart time, an estimated downtime/gap, and links to the affected workflows’ execution pages. Sends the message to a Discord channel via a Discord webhook and to a Telegram chat via the Telegram Bot API (Slack posting is present but disabled). Setup Create and add an n8n API credential with permission to read executions. Create a Discord incoming webhook for your target channel and add it as a Discord
Route human-in-the-loop approval requests with Slack and Postgres
Quick overview This workflow exposes a single webhook that either accepts new approval requests or handles Slack button callbacks, posting interactive Slack Block Kit messages and recording decisions in a PostgreSQL table. How it works Receives a POST request on a webhook endpoint that serves as both the intake API and the Slack interactivity callback URL. Validates the Slack request signature and timestamp when the request includes Slack signature headers. Routes the request by detecting whether it contains a URL-encoded Slack payload (callback) or a custom intake body (new request). For intake requests, builds a Slack Block Kit approval message with Approve/Reject/Flag buttons and posts it to Slack. Stores the request context, Slack channel ID, and message timestamp in PostgreSQL and returns a 200 response with the generated requestId. For Slack button callbacks, immediately returns a 200 response to Slack, looks up the request context in PostgreSQL, and merges it with the callback details. Updates the original Slack message to replace buttons with a static decision status and writes the decision (approved/rejected/flagged) back to PostgreSQL. Setup Create the approval_requests t
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
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
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
Qualify inbound leads with OpenAI, Slack, and Google Sheets
Quick overview This workflow receives inbound leads via a webhook, normalizes common form fields, and uses OpenAI to score and tier each lead as HOT, WARM, or NURTURE. It logs the result to Google Sheets, sends a tier-specific email auto-reply, and alerts a Slack channel for HOT leads. How it works Receives an inbound lead submission via a POST webhook. Normalizes incoming fields (name, email, company, website, message, budget, timeline, and source) into a consistent structure. Sends the normalized lead details to OpenAI to generate JSON scores (fit, budget, urgency, overall), a tier, reasoning, next action, and red flags. Merges the AI qualification results back into the lead record and routes the lead based on the tier. For HOT leads, posts an alert to Slack, appends the lead to the “Hot Leads” tab in Google Sheets, and sends a HOT auto-reply email. For WARM and NURTURE leads, appends the lead to the matching Google Sheets tab and sends the corresponding tier-specific auto-reply email. Returns a JSON response to the webhook caller confirming success and the assigned tier. Setup Add an OpenAI credential and customize the system prompt ICP/scoring rules in the OpenAI step. Add Goog
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
Triage telehealth appointments with GPT-4o-mini, Telegram, Google Calendar
Quick overview This workflow collects telehealth appointment details via an n8n Form, uses OpenAI (GPT-4o-mini) to score no-show risk, then sends Telegram reminders and confirmations and updates Google Calendar based on the patient’s response, with Slack alerts on workflow errors. How it works Receives a new appointment submission from an n8n Form with patient, appointment, and Telegram chat details. Sends the appointment data to OpenAI (GPT-4o-mini) to generate a 0–100 no-show risk score and explanation. Routes the flow based on the risk score, sending a single friendly Telegram reminder for low-risk patients. For high-risk patients, sends escalating Telegram reminders and a final message that waits for a confirmation or cancellation reply. If the patient cancels, creates a new “rescheduled” time slot in Google Calendar and sends the patient a Telegram reschedule acknowledgement. If the patient confirms, updates the existing Google Calendar event to note the confirmation and sends a Telegram confirmation message. If any step fails, posts an error notification to a Slack channel. Setup Add credentials for OpenAI (Chat), Telegram Bot, Google Calendar OAuth2, and Slack OAuth2 used fo
Triage chronic care vitals with Google Sheets, Gmail, Telegram and Slack
Quick overview This workflow runs daily to read chronic care vitals from Google Sheets, merge them into a per-patient record, score risk using AHA/ADA threshold rules, and notify clinicians via Telegram and Gmail when escalation is needed, while logging all results back to Google Sheets. How it works Runs every 24 hours on a schedule trigger. Reads blood pressure, glucose, activity/sleep, and patient master data from Google Sheets. Merges the sheets into a single structured record per patient for the current day. Calculates a risk score and risk level (LOW–CRITICAL) by evaluating vitals against AHA/ADA guideline thresholds and detecting anomalies. If escalation is required, generates a clinical intervention plan, sends a Telegram alert to the doctor, sends an HTML escalation email via Gmail, and appends/updates the escalated result in the Google Sheets DailyLog. If escalation is not required, writes the routine result to the Google Sheets DailyLog and sends a routine status email via Gmail. If any workflow error occurs, posts an error alert to a designated Slack channel. Setup Add Google Sheets OAuth2 credentials and update each Google Sheets node with your spreadsheet document ID
Score mortgage loan risk from Google Drive PDFs with OpenAI and Gmail
Quick overview This workflow monitors a Google Drive folder for new loan application PDFs, extracts text, and uses OpenAI (GPT-4o-mini) to structure applicant data, score risk, generate a lending summary, and produce an underwriting recommendation, then emails the final report via Gmail and posts Slack alerts on failures. How it works Triggers when a new PDF is created in a specified Google Drive folder. Downloads the PDF from Google Drive and extracts its text content. Uses OpenAI (GPT-4o-mini) to extract key applicant and loan fields into a validated JSON structure. Uses OpenAI (GPT-4o-mini) to calculate a risk score, risk level, approval confidence, and key findings in JSON. Uses OpenAI (GPT-4o-mini) to write a plain-text lending summary and then generate a final underwriting decision (approve/conditional approval/further review/decline) with reasoning and conditions. Assembles a single report from the extracted data, risk analysis, summary, and decision, and sends it to the loan officer via Gmail. If extraction or risk scoring fails, sends a Slack alert and retries by re-downloading the application PDF. Setup Connect Google Drive OAuth2 credentials and replace YOUR_GOOGLE_DRIVE
Recover overdue invoices with GPT-4o-mini, Gmail, Google Sheets and Slack
Quick overview This workflow runs every 24 hours to read overdue invoices from Google Sheets, uses OpenAI (GPT-4o-mini) to draft personalized recovery emails and determine escalation, sends emails via Gmail, logs outcomes back to Google Sheets, and posts status and error alerts to Slack. How it works Runs every 24 hours on a schedule trigger. Reads invoice rows from a Google Sheets “invoices” tab and checks whether there are any valid invoice entries to process. If no invoices are found, posts a “no overdue invoices” message to a Slack channel. For each invoice found, uses OpenAI (GPT-4o-mini) to assign an escalation level, draft a personalized HTML email (including payment plans when applicable), and recommend an escalation action. Parses the AI output into structured fields and sends the recovery email to the client via Gmail. If the AI recommends escalation, sends an internal escalation alert email to the legal team via Gmail. Updates the invoice row in Google Sheets with the new escalation level and AI summary, then appends a full audit log row to a “Recovery sheet” tab. If AI processing fails, posts an error alert to Slack and continues with the next invoice. Setup Add Google
Detect maverick spend and alert reviewers via Slack, Gmail, Sheets and Gemini
Quick Overview This workflow runs daily to compare procurement transactions in Google Sheets against an approved supplier list, flags unapproved (maverick) spend, uses Google Gemini to generate compliant alternatives, alerts reviewers via Slack and Gmail, logs violations back to Google Sheets, and escalates unresolved cases after two hours. How it works Runs every day at 11:00 AM on a schedule. Loads the approved supplier list and the latest transactions from Google Sheets and normalizes supplier names for consistent matching. Compares each transaction’s supplier against the approved list and flags transactions from unapproved suppliers as maverick spend. For approved suppliers, marks the transaction as processed in Google Sheets and ends. For maverick spend, sends the transaction details and the approved supplier list to Google Gemini to generate corrective recommendations and alternative suppliers. Formats the AI output with a timestamp, posts a Slack alert, and sends a detailed violation email through Gmail. Appends the violation details to a Google Sheets log, marks the transaction as processed, waits two hours, and then posts an escalation message to Slack. Setup Connect Googl
Monitor budget variance with Google Sheets, Gemini, Slack, and Gmail
Quick overview This workflow runs daily to compare department budgets and actual spend from Google Sheets, calculates variance, uses Google Gemini to generate root-cause insights, sends Slack alerts when variance breaches a threshold, logs results back to Google Sheets, and emails a daily report via Gmail. How it works Runs every day at 9:00 AM on a schedule. Reads budget and actual spend data from two Google Sheets tabs and matches records by Department. Calculates spend variance and variance percentage, then assigns a status label (Healthy/Warning/Critical) and run context like date and summary. Sends the variance details to Google Gemini to generate a JSON response with root cause, risk level, and recommendations. Checks whether the variance percentage is greater than 10% and sends a Slack alert with the AI insights when the threshold is exceeded. Appends the final analysis (including whether an alert was sent) to a Google Sheets log and sends the same report via Gmail. Setup Connect Google Sheets OAuth credentials and set the correct spreadsheet and sheet tabs for Budget Data, Actual spend, and the Final report log. Add a Google Gemini (PaLM) API credential for the Gemini model
Transcribe and analyze sales meetings with Deepgram, Gemini, GHL, Slack & Gmail
Quick overview Youtube Video: https://youtu.be/GNAplBWdCDE?si=TjojVTZX7ViiRUiG This workflow receives meeting voice recording via webhook, transcribes it with Deepgram, and uses Gemini to extract client details and next-step tasks. It then updates GoHighLevel, posts a task summary to Slack, emails the client their action items via Gmail, and logs the meeting to Sheets. How it works Receives a POST webhook request containing a meeting ID, attendee email, meeting date/time, and an audio file. Looks up the contact in GoHighLevel by email and creates/updates the contact if it does not already exist. Checks Google Sheets for the meeting ID and only continues if no existing row is found. Sends the audio binary to Deepgram to transcribe the recording with speaker diarization and utterances enabled. Formats the transcript and sends it to a Google Gemini–powered agent that returns structured JSON with client identification and task lists. Creates a GoHighLevel task with the extracted service-provider tasks, posts the task summary to Slack, and emails the client their tasks via Gmail. Appends the meeting details, extracted company name, and action items to Google Sheets and returns a webhook
Notify and manage podcast edit status with WizCut and Slack
Quick overview This workflow listens for WizCut job status webhooks and routes updates to Slack, prompting a speaker-to-camera mapping review, automatically starting the final render when cuts are ready, and notifying your team with the finished episode download link when rendering completes. How it works Receives a webhook event from WizCut whenever a job status changes. Checks the incoming payload status and routes it to the matching handling path. When the status is "mapping", posts a Slack message listing detected speakers and a link to review and map speakers to cameras in WizCut. When the status is "ready", calls the WizCut API to start rendering the final episode output for the job. When the status is "complete", posts a Slack message with the rendered episode download link. Setup Add your WizCut API credentials in n8n (get an API key from wizcut.com). Add your Slack credentials and set the target channel (for example, #podcast-production) in the two Slack message steps. Copy the WizCut Trigger webhook URL from n8n and pass it as the callbackUrl when you create WizCut jobs so status updates are sent to this workflow. Requirements A WizCut account with an API key (from wizcut