HTTP Request workflows
1,200 results — 3 downloadable workflow files, 1,197 source-linked n8n references
WEnrich Google Maps business leads with Apify and Google Sheets
Quick overview This workflow runs on demand to scrape Google Maps business leads with Apify, optionally fetches each business website to extract an email address, and appends the enriched lead data to a Google Sheets spreadsheet. How it works Starts manually and loads the Apify API key, Google Maps search query, max results, and target Google Sheets spreadsheet ID. Launches the Apify Google Places scraper run for the provided search query and stores the returned run ID and dataset ID. Polls Apify until the actor run status is SUCCEEDED, waiting and retrying until results are ready. Downloads the scraped business items from the Apify dataset and processes them one business at a time. If a business has a website, requests the site HTML and extracts the first valid email address found; otherwise it keeps the email blank. Appends each enriched lead (name, email, phone, rating, address, review count, and website) as a new row in Google Sheets. Setup Add your Apify API token and replace the placeholder value in the configuration step. Connect Google Sheets credentials in n8n and set the target spreadsheet ID (and sheet name if not Sheet1). Update the Google Maps search query and max resu
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
Generate personalized financial plans with Google Gemini, Sheets, Drive and Gmail
Quick overview This workflow receives income and financial-goal data via webhook, stores enriched metrics in Google Sheets, generates a tailored plan with Google Gemini, converts it to a PDF via PDFShift, uploads it to Google Drive, and emails the result using Gmail. How it works Receives a POST webhook request containing an Income value and a Goal string. Normalizes the incoming fields and validates that income is non-negative and the goal is not empty, returning a webhook error response if validation fails. Calculates a timestamp, a recommended monthly saving amount (20% of income), and an income category (Low/Mid/High), then appends the record to Google Sheets. Routes the request by income category and uses Google Gemini (PaLM) to generate a personalized financial plan with category-specific guidance. Builds an HTML report that includes the user’s inputs and the Gemini-generated plan, then converts the HTML to a PDF using the PDFShift API and fetches the generated file. If the PDF is created successfully, uploads it to Google Drive, emails the PDF and Drive link via Gmail, and returns the HTML report in the webhook response. If PDF generation fails, returns a JSON error response
Score job listings and generate tailored cover letters with Apify, OpenAI and Google Sheets
Quick overview This workflow runs on a schedule to scrape job listings via Apify (Google Jobs and Career Site API), scores each role against your base resume using OpenAI, generates tailored cover letter and optionally a tailored resume in Google Docs, and logs the results to Google Sheets with Gmail error alerts. How it works Runs on a schedule (with an optional manual test trigger) and loads your search query and Google IDs from the configured variables. Uses Apify actors to scrape jobs from Google Jobs and the Career Site API, then normalizes and merges both result sets into a single list. Processes jobs in batches and skips listings that already exist in Google Sheets (matched by Apply URL), have no apply link, have short descriptions, or don’t meet the seniority criteria. Fetches your base resume from Google Docs and sends the resume plus job details to OpenAI to score relevance from 1–10 with a one-sentence rationale. For jobs scoring 7+, uses OpenAI to generate a personalized cover letter from the job description and your resume. For jobs scoring 8+, uses OpenAI to tailor your resume, saves it as a new Google Doc in your Drive folder, and makes the document publicly readable
Draft and review SEO WordPress articles with multi-agent LLMs and Slack
Quick overview This workflow accepts an article brief via webhook, routes it through a three-stage LLM pipeline to research, draft, and review HTML content, optionally generates a featured image with Google Imagen, then creates a WordPress draft post with tags and Rank Math SEO metadata and sends an optional Slack notification. How it works Receives a POST webhook request with a required prompt (and optional category, tone, and style overrides) and optionally validates a Bearer token. A researcher agent calls the LLM sub-workflow to produce a structured JSON outline, including title, H2 sections, tags, focus keyword, and image subject. Optionally starts the generation of a 16:9 featured image in parallel using Imagen 4 and the outline's image subject. The default option for whether this is enabled (set in CONFIG), can be overridden per run in the request prompt. Optionally fetches recent published WordPress posts and selects up to five relevant URLs to use as internal links. A writer agent drafts the full HTML article body based on the outline (and internal links), tone guide, and style guide from CONFIG. A reviewer agent edits the draft for voice, accuracy, and structure, then ret
Proxy OpenAI-style chat completions to Gemini with async webhooks
Quick overview This workflow exposes an OpenAI-compatible /v1/chat/completions endpoint in n8n that forwards requests (including optional file attachments) to a configurable LLM HTTP provider, supporting both synchronous replies and asynchronous processing via a callback URL. How it works Receives a POST request on /v1/chat/completions via a webhook, accepting JSON or multipart form-data with optional binary file uploads. Converts any uploaded files into OpenAI-style message content (images as image_url data URLs and other files as text entries) and merges them into the last user message. Prepares a job ID, extracts optional callback and provider override settings (URL and headers), and keeps the original request body for later use. If a callback URL is provided, immediately returns HTTP 202 with the job ID, then sends the request (without callback/provider fields) to the configured LLM provider endpoint. Formats the provider response (or error) into a completion payload with a status code and posts the result to the callback URL with job metadata. If no callback URL is provided, sends the request to the LLM provider synchronously and returns the provider response (or error) to the
Send GitHub release audio newsletters with OpenAI, Google Drive, Gmail and Sheets
Quick overview This workflow triggers on a published GitHub Release, uses OpenAI to turn the release notes into a short spoken script and MP3, stores the audio on Google Drive, pulls subscribers from Google Sheets, and sends an HTML “listen” newsletter to them via Gmail. How it works Triggers when a GitHub Release is published for the configured repository. Parses and cleans the release changelog, extracting key items into features, fixes, improvements, and other notes. Uses an OpenAI chat model to rewrite the release details into a 60–90 second spoken script. Calls the OpenAI text-to-speech API to generate an MP3 audio file from the script. Uploads the MP3 to Google Drive and sets the file permissions to “anyone with the link can view.” Loads subscriber email addresses from Google Sheets, builds an HTML newsletter with the public audio link and release highlights, and sends it via Gmail using BCC. Setup Connect a GitHub credential with access to the target repo and replace YOUR_GITHUB_USERNAME and YOUR_REPO_NAME in the GitHub trigger. Add an OpenAI API credential for both the chat model step and the OpenAI TTS HTTP request. Connect Google Drive OAuth2 and replace YOUR_AUDIO_FOLDER
WDiscover and score engineering candidates with Groq, GitHub, LinkedIn, Stack Overflow, HN and Supabase
Quick Overview This workflow exposes a POST webhook that turns a job description into a structured hiring brief using Groq, searches candidates across GitHub, LinkedIn (via Apify), Stack Overflow, and Hacker News, scores and summarizes the shortlist, optionally saves results to Supabase, and returns a JSON response. How it works Receives a candidate search request via a POST webhook and normalizes the payload into a consistent schema. Validates that the request includes a job description or structured criteria, and returns a 400 JSON error if it is invalid. Uses Groq (via LangChain) to extract structured job requirements, then builds a search brief with queries and limits for each source. Searches GitHub, LinkedIn via Apify, Stack Overflow, and Hacker News in parallel and normalizes each source’s results into a common candidate format. Merges all candidates, sanitizes and deduplicates the pool, and returns an empty 200 response if no candidates remain. Scores candidates with a deterministic evidence formula, filters by the configured score threshold, and builds a recruiter-facing JSON report. Uses Groq (via LangChain) to generate an AI shortlist summary, attaches it to the report,
WProcess Jellyfin media requests with Google Sheets, Radarr, Sonarr, and Gmail
Quick overview This workflow monitors a Google Sheets-based media request form and automatically routes requests to Radarr (movies) or Sonarr (TV shows) via their APIs, then emails the requester through Gmail once the matching title is added for download. How it works Triggers every 5 minutes when a new row is added to a specified Google Sheets worksheet. Checks the “Request Type” field and routes the request to either the movie (Radarr) path or the TV show (Sonarr) path. Searches Radarr or Sonarr for the requested “Title of Media” using the lookup API endpoint. Filters the lookup results in JavaScript to pick the best matching title, prioritizing English originals and (for TV) allowing exact-title matches to support dubbed/anime requests. Submits the selected movie or series to Radarr or Sonarr with a defined quality profile, root folder path, and an automatic search for downloads. Sends a Gmail notification to the email address from the Google Form submission confirming the request is being downloaded. Setup Connect Google Sheets credentials and set the Spreadsheet (documentId) and worksheet (sheetName) used by your Google Form responses. Add HTTP Header Auth credentials for Rada
Send a weekly Plausible analytics digest to Telegram chat
Quick Overview This workflow runs every Monday (or manually) to query Plausible Analytics for top pages, new referrers, and potential content decay, then formats a weekly digest and sends it to a Telegram chat. How it works Runs every Monday at 8:00 AM or starts on demand via a manual trigger. Sets the Plausible site ID, Plausible base URL, and the target Telegram chat ID. Queries the Plausible API for the last 7 days’ top pages and prepares a top-5 list by visitors. Queries Plausible for referrers for the last 7 days and the previous week, then identifies referrers that appear this week but not last week. Queries Plausible for per-page visitors for the last 7 days and for a week 4 weeks ago, then flags pages with significant traffic drops. Combines the insights into a Markdown message and sends the digest to Telegram. Setup Add a Plausible API key as an HTTP Bearer Auth credential and ensure the workflow points to your Plausible instance URL. Update the workflow variables with your Plausible site_id, plausible_url, and the destination telegram_chat_id. Add Telegram credentials and ensure the bot can post to the target chat (start a chat with the bot or add it to the group). Adjust
Qualify Product Hunt leads with Google Gemini, Apify, and Google Sheets
Quick overview Youtube Video: https://youtu.be/h47YeiivZvs?si=V-S1X-ME5V24Tuch This workflow runs daily to pull the latest Product Hunt posts, qualifies them with Google Gemini, scrapes ICP-matching product websites with Apify to find emails, then writes the lead data to Google Sheets and creates contacts in GoHighLevel. How it works Runs every day on a schedule trigger. Queries the Product Hunt GraphQL API for the latest posts and iterates through each result. Resolves each product’s website redirect target, extracts a clean domain, and filters out blocked domains like app stores, social networks, and link aggregators. Sends the product name, tagline, and description to a Google Gemini–powered agent to score ICP fit and keeps only matches. Uses Apify to crawl each matched website and extract email addresses from the site content. Groups scraped results by domain, keeps only products with at least one email, and appends or updates a matching row in Google Sheets. Creates a GoHighLevel contact using the first email and stores any additional emails in a custom field. Setup Add Product Hunt OAuth2 credentials and ensure the GraphQL query in the Product Hunt request returns the fields
Extract meeting insights from transcripts with OpenAI, Google Sheets and ClickUp
Quick Overview This workflow collects a meeting transcript via an n8n Form, uses OpenAI (ChatGPT) to extract structured meeting intelligence, logs the results to Google Sheets, creates one ClickUp task per action item, and emails an HTML meeting brief via Gmail. How it works Receives a form submission containing the meeting title, date, participants, duration, and full transcript. Validates the input (including a minimum transcript length), calculates counts, and generates a unique meeting ID. Sends the meeting context and transcript to an OpenAI ChatGPT model to extract a strict JSON payload with summary, topics, decisions, action items, risks, follow-up date, and sentiment. Parses and normalizes the AI JSON output, then formats readable strings and metrics for reporting. Appends the full meeting record to a Google Sheets “Meetings” tab. Splits the extracted action items and creates a ClickUp task for each valid item, including owner, priority, and due date when provided. Sends a formatted HTML meeting brief to the configured team email address using Gmail. Setup Add an OpenAI credential in the OpenAI Chat Model node and select the model to use. Connect Google Sheets OAuth2, repla
Track Slack EOD updates and post executive summaries with Google Sheets and Gemini
Quick overview Youtube Video: https://youtu.be/AbkX2splTTg?si=LTHqLFIWQD4hAYsO This workflow collects end-of-day updates from team members in Slack, stores them in Google Sheets, and posts a concise executive summary back to Slack using Google Gemini. How it works Runs daily at 3pm, reads the team roster from Google Sheets, filters out people marked as on leave, and sends each active member an EOD update form in Slack. Receives Slack button/form submissions via a webhook, parses the interactive payload, and replaces the original message with a confirmation. Checks whether the submitted EOD date matches today’s date, and sends a private Slack alert to the owner if someone submits late. For on-time submissions, reads today’s entries from the EOD submissions Google Sheet, deduplicates by user and date, and appends the new submission to Google Sheets. Runs daily at 5pm, reads today’s submissions and yesterday’s “tomorrow plan” entries from Google Sheets and merges them per user. Aggregates the merged data, calculates attendance and expected submission counts from the team roster, and sends the dataset to Google Gemini to generate an executive summary. Posts the generated Slack-formatte
Generate and send personalized client proposals with OpenAI, SendGrid, Slack, and Google Sheets
Quick overview This workflow accepts proposal requests via webhook or an hourly schedule, normalizes and validates the client data, uses OpenAI to generate a tailored proposal with pricing, then sends it via SendGrid, logs the request to Google Sheets, notifies a Slack channel, and returns a webhook response. How it works Receives a proposal request from a webhook POST (or runs hourly on a schedule) and maps incoming fields into a consistent client schema. Validates required fields, converts the budget to a number, and assigns a budget tier for pricing. If required data is missing, sends a SendGrid email to the requester listing the validation errors. Routes valid requests by client type (startup, enterprise, agency, nonprofit, or default) and applies conditional pricing and discounts to build line items and totals. Uses OpenAI (GPT-4o-mini) to generate a seven-section, personalized proposal based on the client details, project scope, template context, and pricing. Formats the generated proposal into a branded HTML email with an investment breakdown table. Sends the proposal via SendGrid, appends a tracking row to Google Sheets, posts a Slack notification, and returns a JSON succes
Book, reschedule and confirm WhatsApp appointments with Claude and Sheets
Quick overview This workflow receives WhatsApp messages via a Meta webhook, uses Anthropic Claude to detect booking intents and extract appointment details, writes updates to Google Sheets, and sends a confirmation or error reply back to the customer on WhatsApp. How it works Receives incoming WhatsApp messages through a Meta webhook endpoint and normalizes key fields like sender phone number, display name, message text, and timestamps. Filters out empty messages and sends the text to Anthropic Claude to classify the intent (book, reschedule, confirm, or unknown) and extract structured appointment details. Validates the request based on intent, including required fields and simple rules like weekday-only appointments and business hours. Appends a new row to the Google Sheets Appointments tab for valid bookings, or updates the appointment status/date/time in Google Sheets for reschedules and confirmations. Builds a personalized WhatsApp reply message describing the result (success, required missing details, or supported actions). Sends the reply back to the customer via the WhatsApp Cloud API and appends the interaction details to the Google Sheets ActivityLog tab. Setup Create a Me
WPublish weekly SMB blog posts with Perplexity, Claude, Gemini, Supabase, and Gmail
Quick overview This workflow runs weekly to generate, research, write, illustrate, and publish a new blog post by combining Supabase (content + storage), Perplexity (topic + research), Anthropic Claude (writing), Google Gemini (cover image), and Gmail (notification). How it works Runs every Friday at 10:00 (cron: 0 0 10 * * 5). Fetches titles of already published posts from Supabase and builds a rotating topic focus that avoids repeating prior angles. Uses Perplexity to propose one fresh, SEO-relevant blog topic and then research it with trends, examples, and SMB-focused insights. Sends the topic and research notes to Anthropic Claude to write a complete post with title, excerpt, meta description, category, read time, and HTML body. Parses the generated text into structured fields, generates a slug, and prepares a published blog post record. Uses Google Gemini to generate a 16:9 cover image, uploads it to Supabase Storage, and attaches the public cover image URL to the post. Inserts the finished post into the Supabase blog_posts table with status set to published and emails the team via Gmail with the publication details. Setup Create a Supabase project with a blog_posts table and
WMonitor negative customer reviews with an HTTP API, Google Sheets and Slack
Quick Overview This workflow polls your review API every 6 hours, filters for reviews rated 3 stars or lower, and posts an alert to a Slack channel for each negative review. How it works Runs every 6 hours on a schedule. Fetches the latest reviews from a configured HTTP endpoint. Filters the returned items to keep only reviews with a rating of 3 or below. Checks whether any negative reviews were found and stops if none exist. Posts each negative review to a selected Slack channel with the rating, author, and review text. Setup Provide a reviews API endpoint (and any required authentication) in the HTTP Request node. Connect Slack using an OAuth2 credential. Select the target Slack channel and adjust the rating threshold in the filter logic if you want a stricter or looser definition of “negative”.
Create work4all incoming invoices from Microsoft Outlook supplier emails
Quick Overview This workflow polls a Microsoft Outlook folder for new supplier emails, sends each message to a companion n8n sub-workflow that creates an incoming invoice in work4all, and then categorizes the email (green/yellow/red) and emails errors via Outlook. How it works Runs every minute on a schedule. Fetches all emails from a specified Microsoft Outlook folder that are not already categorized as Red or Green, downloading any attachments. Sends each email to a companion sub-workflow that extracts invoice data from attachments and creates the incoming invoice in work4all. If the sub-workflow returns errors, sends an error notification email via Microsoft Outlook and categorizes the original message as Red. If no errors occur, categorizes the message as Green when booking is clean, or as Yellow + Green when a supplier was created or an account/tax key was set automatically. Setup Import and publish the companion workflow "Create a work4all incoming invoice from email attachments using AI" and select it in the Execute Workflow step. Add Microsoft Outlook credentials with permission to read the target mailbox and send emails. Update the Outlook folder ID to monitor and ensure t
WScrape business emails from Google Maps to Google Sheets
Quick overview This workflow takes a list of Google Maps search queries, extracts candidate business website URLs from the search results, visits each site, scrapes email addresses from the page content, and appends cleaned, deduplicated emails to Google Sheets fully automated, no manual research needed. How it works A manual trigger fires with a pinned list of Google Maps search queries, each representing a location and business type combination. A query loop iterates through each query, launching a sub-workflow execution per query and applying a configurable wait between executions to reduce request bursts. The sub-workflow sends an HTTP GET to the Google Maps search results URL for that query and reads the raw HTML response. A code node extracts all URLs from the HTML using a regex pattern, after which a filter node removes known system domains such as Google, gstatic, schema.org, and Wix internals, and a deduplication node removes repeated URLs before visiting. A URL loop processes each candidate business website one at a time, fetching the page HTML and passing it into the email processing flow. A code node applies a regex to the fetched page content to extract email-shaped st
WFetch and parse Amazon SP-API reports into structured TSV rows
Quick Overview This workflow manually requests an Amazon Selling Partner (SP-API) report, polls until it is ready, downloads the report document, optionally decompresses it if it is GZIP, and parses the TSV contents into one n8n item per row. How it works Starts when you run the workflow manually. Uses Login with Amazon (LWA) to exchange your refresh token, client ID, and client secret for an access token. Calls the Amazon SP-API Reports API to create a report for the configured report type and marketplace. Polls the Amazon SP-API until the report processing status is DONE (or errors if it fails or times out). Fetches the report document metadata and downloads the report file from the provided URL. If the document is GZIP-compressed, decompresses the file and then parses the TSV into structured JSON items, outputting one item per row. Setup Create and authorize Amazon SP-API (Login with Amazon) credentials, then fill in the refresh_token, client_id, and client_secret values in the Config step. Set the correct SP-API endpoint region (EU/NA/FE), report_type, and marketplace_ids values in the Config step. If you want to store or route results, add downstream nodes after the parsed row
Monitor website changes with PolyDoc screenshots and email alerts
Quick Overview This workflow checks a website URL every 6 hours, detects content changes by hashing the normalized HTML, and when a change is found it uses PolyDoc to capture a full-page screenshot and emails the PNG as an attachment. How it works Runs every 6 hours on a schedule. Sets the target URL to monitor and fetches the page HTML with an HTTP request. Normalizes the HTML (removing scripts/styles/comments), hashes it, and compares it with the previous run stored in workflow static data. If the hash changed, PolyDoc captures a full-page PNG screenshot of the URL. Sends an email with the screenshot attached and the monitored URL in the subject and body. Setup Update the monitored website URL in the Settings step. Add your PolyDoc API credentials to the PolyDoc screenshot step. Configure an SMTP email credential and set the to/from email addresses in the email step.
Extract ecommerce product data with Google Sheets, ScrapingBee and Gemini
Quick Overview This workflow manually runs to read a list of webpage URLs from Google Sheets, scrape each page with ScrapingBee, and use Google Gemini to extract structured product data from screenshots with an HTML fallback, then append the results back into a Google Sheets sheet. How it works Runs when you manually trigger the workflow. Reads the list of URLs to scrape from a Google Sheets spreadsheet. Fetches a full-page screenshot for each URL using the ScrapingBee API. Sends the screenshot (and the URL for context) to a Google Gemini model to extract product details into a structured JSON format, calling a ScrapingBee HTML fetch tool when screenshot extraction is incomplete. Converts any fetched HTML to Markdown and returns it to the Gemini agent to complete the extraction. Splits the extracted product array into individual items and appends them as new rows in the Google Sheets “Results” sheet. Setup Create a Google Sheets service account connection in n8n and set the target spreadsheet and the “List of URLs” and “Results” sheet selections. Add a Google Gemini (PaLM) API credential in n8n and ensure the selected model (gemini-1.5-pro-latest) is available for your account. Add
Sync Shopify customers with Cegid Y2 on create or update
Quick overview This workflow receives Shopify customer create/update webhooks and syncs the customer record to CEGID Y2 by creating the customer when missing or updating the existing customer when CEGID reports a duplicate. How it works Receives a POST webhook from Shopify when a customer is created or updated. Builds a CEGID Y2 customer payload with identifiers, tax/currency details, and the default store/workspace settings. Formats the customer address and chooses whether to send individual or company contact details based on whether a company name is present. Sends the assembled payload to CEGID Y2 to create the customer. If CEGID returns a “customer already exists” error, extracts the existing CEGID customer ID from the error message and sends a PATCH request to update that customer in CEGID. If the create request fails for any other reason, stops the workflow and surfaces the CEGID error. Setup In Shopify, create a customer webhook for create/update events and point it to this workflow’s webhook URL, matching the allowed shop domain. Add CEGID Y2 HTTP Basic Auth credentials and ensure the API user has permission to create and update customers. Update the CEGID API base URL, wo
WRoute real estate buyer and seller leads with Claude and Google Sheets
Quick Overview This workflow hosts an n8n lead-capture form, uses Anthropic Claude to score and classify real estate inquiries, then routes ready leads to Gmail and Google Sheets while logging early-stage leads to a separate Google Sheets tab. How it works Receives a new submission from an n8n Form trigger with contact details, intent, area, budget, timeline, financing status, and notes. Normalizes the submitted fields (for example trimming strings, lowercasing email, and adding a timestamp) for consistent downstream processing. Sends the normalized lead details to the Anthropic Messages API (Claude) to return a strict JSON classification, summary, timeline band, financing readiness, recommended agent role, and score. Parses the Claude JSON response, clamps the score to a 1–10 range, and calculates whether the lead is “ready” (score 7). If the lead is ready, sends a formatted Gmail alert to the agent and appends the lead to the “Active Leads” tab in Google Sheets. If the lead is not ready, appends the lead to the “Nurture Leads” tab in Google Sheets. Returns a confirmation message to the form submitter after the lead is routed. Setup Create an Anthropic HTTP Header Auth credential