Browse 12,955 Workflows

By Accelyte.AI

Quick overview This workflow listens for new HubSpot deal webhooks, verifies the request, then creates an Asana project from a template and a Google Drive folder structure for the deal, writes the links back to HubSpot, and emails the deal owner. How it works Receives a HubSpot deal-creation webhook and verifies the request using the HubSpot signature header and your HubSpot app client secret. Loads the new deal details from HubSpot and retrieves the deal owner’s information. Checks whether the deal has an associated HubSpot company, and emails the owner a notice if no company is linked. Fetches the associated company from HubSpot and checks whether it already has a saved Google Drive folder ID. If no company folder exists, creates a company folder and then a deal folder in Google Drive; otherwise, creates only the deal folder under the existing company folder. Creates a new Asana project by instantiating your Asana project template and retrieves the project permalink. Saves the Asana project and Google Drive folder links/IDs back onto the HubSpot deal (and the company folder link/ID onto the company when newly created), then emails the deal owner the workspace links. Setup Create and connect credentials for HubSpot OAuth2, Google Drive OAuth2, Asana OAuth2, and Gmail OAuth2. In the configuration values, set your HubSpot app client secret, Google Shared Drive ID, the parent folder ID where company folders should be created, and your Asana project template GID. In HubSpot, create the custom properties this workflow updates (for example: asana_project, asana_project_id, google_drive_folder, and google_drive_folder_id on deals, plus google_drive_folder and google_drive_folder_id on companies). Add the workflow’s production webhook URL to a HubSpot deal-creation webhook subscription so HubSpot sends deal events to this workflow. An n8n automation workflow template by Accelyte.AI.

By Javed Iqbal

Quick overview This workflow receives a webhook request with a topic and context, generates platform-specific copy for LinkedIn, X, Facebook, and Instagram using Anthropic Claude, Google Gemini, or OpenAI, optionally creates a matching image via OpenAI Images or Gemini Flash Image, and returns the results as JSON. How it works Receives a POST request on the /webhook/social-content webhook containing the topic, context, provider selection, and optional tone/audience/brand/CTA/language and image settings. Normalizes and validates the payload (including provider, content length limits, and image options) and returns a 400 response if required fields are missing or invalid. Routes the request to Anthropic Claude, Google Gemini, or OpenAI to generate structured social posts for LinkedIn, X (single post and thread), Facebook, and Instagram. If image generation is enabled and requested, routes to OpenAI Images (gpt-image-1) or the Gemini image generation API to create an image prompt based on the Instagram image idea and requested style/size. Merges the generated text and optional image (or an image error) into a single JSON payload. Responds to the webhook caller with a 200 success JSON payload, or a 500 error payload if text generation fails. Setup Add credentials for at least one text provider you plan to use: Anthropic API (Claude), Google Gemini / PaLM API, and/or OpenAI API. If you want image generation, also configure the required credential for the chosen image provider (OpenAI API for gpt-image-1 and/or Google Gemini / PaLM API for Gemini image generation). Set your preferred default behavior in the workflow settings payload (for example, toggle the image_generation_enabled master switch) and adjust the prompts/models/temperatures in the respective provider nodes as needed. Activate the workflow and copy the production webhook URL into your calling app or script that will send POST requests to /webhook/social-content. An n8n automation workflow template by Javed Iqbal.

By Stanislaw Chalupczak

Quick overview This workflow runs on a manual or daily schedule to sync WooCommerce products into Pinecone by fetching changed items, enriching them with variations and reviews, generating OpenAI embeddings, and tracking indexed products in an n8n Data Table for deduplication and deletion handling. How it works Runs on a manual trigger or every day at 03:00 to start a WooCommerce-to-Pinecone sync. Fetches a paginated list of all published WooCommerce products (ID and modified date) and loads previously indexed entries from an n8n Data Table. Compares WooCommerce products to the Data Table to select a limited batch of new or changed products, then retrieves full product details for that batch in one WooCommerce API request. Processes each product one by one, fetching variations for variable products and retrieving up to 10 WooCommerce reviews per product. Builds a clean text representation of the product (details, variants, and selected reviews) and deletes any existing Pinecone vectors for the same product fileId to prevent duplicates. Splits the text into chunks, generates OpenAI embeddings, and inserts the vectors into a Pinecone index under the configured namespace. Upserts the product’s latest modified date into the n8n Data Table and also removes Pinecone vectors and table entries for products that no longer exist in WooCommerce. Setup Add WooCommerce API credentials with access to the REST API and set your store base URL in the workflow’s settings values. Add a Pinecone API credential, create or choose a Pinecone index, and fill in the index name, index host, and namespace used for storage. Add an OpenAI API credential for the embeddings step. Create an n8n Data Table named indexed_wc_products_v8 (or update the workflow to your table name) to store productId and dateModified for deduplication. Review and adjust the schedule (cron) and the productBatchSize setting to control how many products each run processes. An n8n automation workflow template by Stanislaw Chalupczak.

By CRMOZ

Quick overview This workflow polls Zoho Community (help.zoho.com) for new announcement topics in selected categories and posts them to a Zoho Cliq channel via a bot, using n8n Data Tables to store subscription preferences and the last-seen timestamp per category. How it works Runs on a schedule to start the announcement polling cycle. Loads the Zoho Cliq channel endpoint and bot API name, then fetches the Zoho Community portalId from help.zoho.com. Reads subscribed Zoho Community categories from an n8n Data Table and loops through each category that has announcements enabled. For each category, reads the last check time from an n8n Data Table and requests the latest announcement topics from the Zoho Community API. Splits the returned topics into individual items and filters to only those created after the stored last check time (or the last 24 hours if none exists). Posts each new announcement to Zoho Cliq via an authenticated HTTP request (including subject, link, content snippet, and author) and updates the stored last check time for that category. Setup Run the manual “initial database setup” once to create the two n8n Data Tables used for subscription preferences and last-view tracking. Create Zoho OAuth2 credentials with the ZohoCliq.Webhooks.CREATE scope and select them in the Zoho Cliq message request so n8n can authenticate to the Cliq API. In Zoho Cliq, create (or choose) a target channel and update the workflow’s configuration with the channel API endpoint and the bot_unique_name (bot API name), then invite the bot to the channel. Set your desired polling frequency in the schedule trigger. (Optional) Enable the admin panel webhooks, open the admin panel URL to choose subscribed categories, and then disable the admin webhooks again if you want to prevent others from changing subscriptions. An n8n automation workflow template by CRMOZ.

By yaho

Quick overview Verify a phone number or email lead before updating your CRM. This Zelnum realtime workflow checks current products, previews pricing without a charge, and requires explicit billing approval before returning per-product verdicts and spending details. How it works Runs manually to start a verification request for one phone number or email address. Fetches Zelnum’s current realtime product catalog to ensure the selected product IDs exist and match the chosen series (phone or email). Validates the input identifier, country (for phone), product selection, and billing controls, then requests a non-billable quote from the Zelnum realtime quote endpoint. Checks the quote total and expiry and branches based on whether billing is explicitly enabled. If billing is not enabled, returns a quote-only preview (no charge) so you can review pricing. If billing is enabled and within the max USDT limit, submits the billable realtime check to Zelnum using an idempotency key and the quote token. Parses the Zelnum response into CRM-friendly output including overall verification_state and per-product results with valid/invalid/unknown verdicts and billing status. Setup Register with Zelnum, open API Center, and create an API key. Add an n8n HTTP Header Auth credential with header name X-API-Key and your private key, then select it on the quote and billable check HTTP Request nodes. Never publish the key or real contact data. In the configuration step, set series (phone or email), the identifier, and (for phone) a two-letter country code when using a national number. Run once to inspect the product catalog output, then set 1–10 matching Zelnum realtime product_ids for the chosen series. To run paid checks, set a stable idempotency_key, set max_total_usdt, and change execute_billable to true after reviewing the quote preview. Add your downstream CRM/database nodes after the final output to store or route the verdicts (for example, flag manual_review items for follow-up). Requirements A Zelnum account with API access, sufficient balance for paid checks, and compatible built-in n8n nodes. Run quote previews first; keep execute_billable=false until you approve the price. Customization After private testing, connect your CRM or an authenticated form trigger. Route inconclusive results to manual review rather than treating them as invalid. Additional info Read the Zelnum API documentation for product coverage, billing, and error codes. Visit Zelnum for the platform overview. Product verdicts do not establish contact consent or guarantee email deliverability. An n8n automation workflow template by yaho.

By Daniel Secareanu

Quick overview This workflow runs every Monday and scans a HubSpot deal pipeline for hygiene issues and expansion opportunities, optionally using TypeSafe Jev to recommend fixes. It emails a Gmail approval form, then applies only the reviewer-approved updates back to HubSpot and sends a results summary. How it works Runs every Monday at 08:00 and loads the configured HubSpot pipeline, portal details, and deal owners. Searches HubSpot for all deals in the selected pipeline and gathers Closed Won deal-to-company associations to identify existing clients. Applies rules to flag open deals with issues (for example past/missing close dates, staleness, stuck stages, missing amount/owner/contact) and to find companies eligible for an expansion conversation. For each flagged item, fetches the latest associated HubSpot note and (if enabled) sends the deal/client context to TypeSafe Jev to choose a recommended action with a confidence score, falling back to deterministic rules when Jev is disabled or unavailable. Sends a Gmail message containing a review form with one checkbox per proposed fix, preselecting higher-confidence recommendations, and waits up to the configured review window for a response. Matches the reviewer’s selections to the proposed fixes and applies only the approved changes in HubSpot (updating deals, creating tasks, or creating expansion deals), then emails a results summary (or a “no changes” message if nothing is approved). Setup Create a HubSpot private app (or service key) with the required scopes and add it to n8n as a HubSpot App Token credential. Connect a Gmail OAuth2 account to send the review email, wait for the form response, and send result/failure notifications. (Optional) Add a TypeSafe Jev API key as an HTTP Header Auth credential (Authorization: Bearer ) or set useJev to false to use the built-in rules only. Update the Settings values for pipelineId and reviewerEmail, and adjust thresholds like staleDays, stuckDays, expansionAfterDays, and reviewWindowDays as needed. Set the recipient address in the failure-alert email so workflow errors are reported to the right inbox. An n8n automation workflow template by Daniel Secareanu.

By Rahul Joshi

Quick Overview This workflow runs every two hours and syncs accounts receivable data between Tally Prime, GoHighLevel, and Google Sheets, calculating balances and aging, updating GoHighLevel fields and tags from Tally, and queuing GoHighLevel-driven ledger changes and receipts for accountant approval before writing back to Tally. How it works Runs on a schedule every two hours during business hours (Mon–Sat, 9:00–19:00). Reads the Customers, Bills, and Tally Change Queue tabs from Google Sheets and posts any queue rows marked Approved to Tally Prime as import XML. Exports debtor ledgers and the Bills Receivable report from Tally Prime over its XML/HTTP interface and parses them into customer balances and open bills. Fetches GoHighLevel contacts and recent payment transactions (with pagination) via the GoHighLevel API. Matches Tally ledgers to GoHighLevel contacts, computes overdue/aging and credit status, resolves email/phone changes with conflict detection, and generates actions for updates, new records, and approval-required changes. Updates GoHighLevel contacts by writing AR custom fields, syncing contact email/phone when safe, and adding/removing AR tags based on the latest Tally receivables. Writes mirror tables back to Google Sheets (Customers, Bills, Conflicts) and appends any Tally changes (new ledgers, contact edits, receipt vouchers) to the Tally Change Queue for approval. Sends a Slack message to an accounts channel only when attention is needed (writes applied/failed, queued approvals, conflicts, unlinked payments, or new credit holds). Setup Enable Tally Prime’s HTTP connectivity (Client/Server mode) and set the workflow’s Tally URL and company name so n8n can reach the Tally machine securely (LAN/VPN/tunnel, not public internet). Create a Google Sheet with tabs named Customers, Bills, Tally Change Queue, and Conflicts (with matching headers), add Google Sheets credentials in n8n, and replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes. Add a GoHighLevel OAuth2 credential in n8n, set your GoHighLevel location ID, and create the required GoHighLevel custom fields and tags, then paste their field IDs and tag names into the sync rules. Add Slack credentials in n8n and set the target Slack channel (for example, #accounts-sync) used for notifications. Review and adjust sync rules such as debtor group name, receipt clearing bank ledger, payment lookback days, and whether to auto-approve Tally writes before activating the workflow. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Quick overview This workflow runs daily to reconcile Razorpay payments and settlements against invoice and bank-credit records in Google Sheets, logs exceptions, sends receipt emails via Gmail, creates and cancels Razorpay payment links for failed-payment recovery, uses OpenAI for match suggestions and reminder drafts, and posts a Slack digest. How it works Runs every day at 7:30 AM on a schedule. Loads invoices, bank credits, the payments ledger, and existing exceptions from Google Sheets. Fetches recent Razorpay payments, the settlement reconciliation report, and settlement records via the Razorpay API with pagination. Matches captured payments to invoices (using stored manual overrides, invoice references, or Razorpay order IDs), checks settlement and bank-credit status, calculates fees, and writes updated ledger, settlement, invoice, and exception records back to Google Sheets. Sends unmatched payments with plausible invoice candidates to OpenAI to generate a suggested invoice match, then logs the suggestion as an exception in Google Sheets without applying it automatically. Emails payment receipts via Gmail for newly paid invoices and cancels any existing Razorpay payment links for paid or replaced invoices. For eligible failed payments, creates a new Razorpay payment link, uses OpenAI to draft a recovery email, sends it via Gmail, updates chase fields in Google Sheets, and escalates high-value or final-attempt cases to a Slack channel. Builds an HTML reconciliation report and emails it to finance via Gmail, then posts a summary digest to Slack. Setup Create a Google Sheet with tabs named Invoices, Payments Ledger, Settlements, Exceptions, and Bank Credits, then replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes. Add a Razorpay HTTP Basic Auth credential (Key ID as username and Key Secret as password) and select it in the Razorpay HTTP Request nodes. Connect Google Sheets OAuth2, a Gmail account for sending receipts and reminders, a Slack OAuth connection for posting to your recon channel, and an OpenAI API key for match suggestions and email drafting. Update the reconciliation parameters in Set Recon Rules (finance email, support contact, lookback windows, tolerances, SLA days, fee percentages, and chase limits) and set the Slack channel (for example #finance-recon) in the Slack nodes. Ensure your upstream order/link creation process writes the invoice ID into Razorpay order receipt or payment notes (for example notes.invoice_id) to enable exact matching. An n8n automation workflow template by Rahul Joshi.

By Dominik

Quick overview This workflow runs daily to scan Microsoft Entra ID (Azure AD) app registrations and enterprise apps via Microsoft Graph for expiring or recently expired client secrets and certificates, then sends an HTML summary alert through Microsoft Outlook and optionally notifies each app’s owners. How it works Runs every day at 07:00 on a schedule. Fetches all app registrations and enterprise apps from Microsoft Graph, including password credentials and key credentials, using pagination. Identifies client secrets, certificates, and SAML signing certificates that expire within the configured threshold (or expired within the lookback window) and optionally hides credentials that already have a newer rotated successor. Looks up the owners for each affected application or service principal in Microsoft Graph and keeps the item even if the owner lookup fails. Builds an HTML summary report with credential status, expiry date, owners, and direct links to the Entra admin center. Sends the summary email to the configured IT/security recipients via Microsoft Outlook, and if enabled, sends a separate notification email to each app’s owners. Setup Create a Microsoft Entra ID app registration/service principal with Microsoft Graph application permissions Application.Read.All, User.Read.All, and Mail.Send, and grant admin consent. In n8n, add a Microsoft Entra Service Principal credential (tenant ID, client ID, and client secret or certificate) and use it for the Microsoft Graph HTTP requests and Microsoft Outlook send actions. Ensure the sender mailbox exists and is allowed to send mail with the configured permissions (for example by restricting Mail.Send to that mailbox via an Exchange Online application access policy). Update the configuration values for thresholdDays, expiredLookbackDays, senderMailbox, adminRecipients, and (optionally) enable notifyOwners before activating the workflow. Requirements A recent n8n version with the Microsoft Entra Service Principal credential An Entra app registration with the application permissions Application.Read.All, User.Read.All and Mail.Send (admin consent required) A mailbox to send the notifications from Customization Raise expiredLookbackDays (for example to 36500) to include all expired credentials. Set hideRotated to false to also list old credentials that already have a valid successor, which is useful for a cleanup. Set showAttribution to false to remove the template credit from the mail footer. Swap the Outlook nodes for Microsoft Teams, Slack or your service desk, for example one ticket per app. An n8n automation workflow template by Dominik.

By Anna Cole

Quick overview This workflow exposes a webhook for Retell AI phone-agent functions to check availability, book, cancel, and reschedule auto repair appointments using Google Calendar, and it notifies the shop owner via Gmail when bookings change. How it works Receives a POST webhook request from Retell AI that includes a function name and call details. Validates the request contains a Retell call ID, then routes it to check availability, book, cancel, or reschedule based on the function name. For availability checks, reads that day’s Google Calendar events and returns open morning or afternoon time slots while respecting closed days and appointment length. For new bookings, parses the caller details and requested time, confirms the slot is still free in Google Calendar, creates the calendar event, and emails the owner via Gmail. For cancellations, searches Google Calendar events on the given date for an event whose title matches the caller name, deletes the event, and emails the owner via Gmail. For reschedules, finds the original event by caller name and date, checks the new time for conflicts, creates a new Google Calendar event, deletes the original event, and emails the owner via Gmail. Setup Create and connect credentials for Google Calendar and Gmail in n8n. Update the shop settings (shop name, owner email, calendar ID, timezone, opening hours, closed days, and appointment length) to match your business. Activate the workflow, copy the production webhook URL, and configure Retell AI custom functions (check_availability, book_appointment, cancel_appointment, reschedule_appointment) to POST to that URL with the expected date/time formats. Requirements Retell AI account with a phone number and a voice agent Google Calendar account for the shop's appointments Gmail account for owner notifications Customization Change slot hours, appointment length and closed days in the Set Shop Configuration node Restyle the owner emails in the Notify Owner and Inform Owner nodes Swap Gmail for Slack or SMS to notify the owner Additional info Retell function arguments (dates as YYYY-MM-DD, times like 9:00 AM): check_availability: date, time_of_day (morning or afternoon) book_appointment: caller_name, caller_phone, vehicle, service_needed, appointment_date, appointment_time cancel_appointment: caller_name, appointment_date reschedule_appointment: caller_name, old_date, new_date, new_time Add "Today is {{current_time}}" at the top of your Retell prompt so the agent can turn "tomorrow" into a real date. An n8n automation workflow template by Anna Cole.

By Jamie Twinney

Quick overview This workflow listens for Telegram messages (text or voice), transcribes voice notes with OpenAI, computes an entropy-based yes/no verdict via sub-workflows, then replies with an OpenAI TTS audio message, sends an HTML “certificate,” logs to Google Sheets, runs compliance log, and triggers a Tapo light flash via HTTP. How it works Triggers when a new Telegram message is received by your bot. Detects whether the incoming message is text or a voice note, rejecting unsupported message types. If the message is a voice note, downloads the audio from Telegram and transcribes it with OpenAI; otherwise it uses the text as-is. Validates and normalizes the question, sends an acknowledgement back to Telegram, and waits briefly before processing. Calls two sub-workflows to analyze the question’s “spiritual weight” and to gather multiple external entropy signals, then combines them into a final entropy score and decision index. Calls a formatting sub-workflow to generate the final oracle verdict and TTS script, then fans out to parallel outputs. Generates an OpenAI TTS audio reply and sends it to Telegram, creates an HTML certificate and sends it as a Telegram document, appends a log row to Google Sheets, calls an EU AI Act compliance-logging sub-workflow, and posts an HTTP request to trigger a Tapo light flash. Setup Create a Telegram bot with BotFather and add a Telegram API credential in n8n, then start a chat with the bot so it can receive messages. Add an OpenAI API credential for Whisper transcription and TTS, and ensure the workflow has access to the configured OpenAI models. Configure the referenced sub-workflows (Spiritual Weight Analyser, Chaos Engine, Oracle Output Formatter, and EU AI Act Compliance Logger) or replace their workflow IDs with your own. Add a Google Sheets OAuth2 credential, replace the Google Sheet document ID, and ensure the target sheet tab (for example, “OracleLog”) exists with compatible columns. Set the HTTP endpoint used for the Tapo light controller (for example, your Cloudflare Tunnel URL) so the POST request can reach your local Tapo automation. Additional info This is the main workflow submission for the Flow for Gold 2026 competition. There are several other workflows that link to this. An n8n automation workflow template by Jamie Twinney.

By Oneclick AI Squad

Quick overview This workflow accepts a procurement request via webhook or manual trigger, uses Anthropic Claude agents to plan, negotiate, validate, and decide on supplier offers, escalates approvals to Slack when needed, and stores the full offer and decision audit trail in Postgres. How it works Receives a purchase request from a manual trigger or a POST webhook request. Applies procurement policy settings, normalizes the incoming payload with defaults, and uses Anthropic Claude (Planner Agent) to generate a structured sourcing plan. Iterates through each supplier and uses Anthropic Claude (Negotiator Agent) to propose counter-offers across multiple rounds while simulating supplier responses until an agreement, walk-away, or max rounds is reached. Uses Anthropic Claude (Validator Agent) plus deterministic policy checks (budget, lead time, minimum supplier rating) to validate each negotiated outcome and upserts each offer into Postgres. Scores and ranks eligible offers, then uses Anthropic Claude (Approval Agent) to recommend auto-approve, escalate, or reject while enforcing hard guardrails in code. If escalation is required, posts an approval request to Slack with Approve/Reject links and waits for a human decision via a resume webhook. Writes the final decision to Postgres and posts the approved/rejected outcome to Slack. Setup Add an Anthropic API key using HTTP Header Auth (x-api-key) and ensure the workflow can reach the Anthropic Messages API. Configure Postgres credentials and create the required tables (procurement_offers and procurement_decisions) in your database. Add Slack credentials, ensure the target channel exists, and set the channel name in the procurement config. If using webhook intake, copy the webhook URL from the “procurement-request” endpoint and configure your source system to POST the procurement JSON payload to it. Review and adjust policy values in the procurement config (auto-approve limit, max negotiation rounds, minimum supplier rating, max risk score) to match your organization’s rules. An n8n automation workflow template by Oneclick AI Squad.