HTTP Request workflows
29 results — all source-linked n8n references
Post a daily Asana project status digest to Slack
Quick overview This workflow runs every weekday morning to fetch tasks from a specified Asana project, bucket them by due status and completion activity, and post a Slack Block Kit digest with counts, key task links, and per-assignee open workload. How it works Runs on a weekday-morning schedule. Pulls tasks from a chosen Asana project via the Asana REST API, including assignee, due date, completion status, and task links, and paginates through results as needed. Groups open tasks into overdue, due today, due this week, and unassigned buckets, and also collects tasks completed within the configured lookback window. Calculates summary counts and open-task load per assignee. Formats the results into a Slack Block Kit message with a short totals line and up to five linked tasks per bucket. Posts the digest to the specified Slack channel. Setup Add an Asana Personal Access Token (Asana API credentials) and select it for the HTTP request that fetches project tasks. Add a Slack OAuth credential and ensure the app/bot can post messages to your target channel. In the configuration step, set your Asana project GID, Slack channel ID, timezone, and the lookback window for recently completed t
Create social visuals from blog RSS with Canvora and Slack
Quick overview This workflow watches your blog RSS feed for new posts, sends each post URL to Canvora to generate branded social image formats (and an optional carousel), polls until generation completes, and posts the resulting image links to a Slack channel for review. How it works Triggers when a new item appears in the configured RSS feed on an hourly polling schedule. Builds a Canvora generation request using the blog post URL plus your selected output formats, optional carousel settings, language, and brand kit ID. Creates the generation in Canvora via its API. Polls Canvora every 30 seconds to fetch the generation status until it completes, fails, is cancelled, or times out after about 10 minutes. If the generation succeeds (completed or partial), sorts the returned assets and formats a Slack message containing the public file URLs and an edit link. Posts the message to the chosen Slack channel for human review, or sends a Slack alert if the generation fails or times out. Setup Create a Canvora account and add an API key as an HTTP Header Auth credential (header name X-API-Key). Update the RSS Feed Trigger with your blog’s RSS URL. Optionally set Canvora format IDs, carousel
Review HeyReach campaign performance and tune Twain agents from Slack
Quick overview This workflow runs daily, pulls campaign stats and reply conversations from HeyReach, sends them to Twain for performance analysis, and posts a digest to Slack with optional one-click approval to apply Twain’s suggested agent updates. How it works Scheduled run Iterates through the configured pairs of Twain campaign IDs and HeyReach campaign IDs. Fetches the HeyReach campaign details, overall performance stats, and recent inbox conversations for each campaign. Packages key metrics and recent message threads and sends them to Twain’s /v2/Campaign/Analyze endpoint for analysis and optimization suggestions. Builds a Slack digest with health signals, reply themes, step diagnostics, and proposed agent changes (plus a link to the campaign in Twain when available). If there are actionable agent changes, posts the digest to Slack with Approve/Skip buttons and applies the approved changes via Twain’s /v2/Agent/Update, then confirms success or errors in Slack. If there are no changes, posts the digest only when the analysis is meaningful (for example, analyzed results or alerts), then moves on to the next campaign. Setup Add HeyReach API access using HTTP Header Auth credentia
Draft personalized LinkedIn outreach from buying signals with Twain and Slack
Quick overview This workflow captures buying-signal leads via a webhook (or optionally polls a HubSpot list), generates a personalized LinkedIn intro and follow-up sequence with Twain, and posts the ready-to-send draft to Slack, with an optional step to stage the lead in a HeyReach campaign. How it works Receives a lead signal via a POST webhook (or, if enabled, runs every 15 minutes to pull contacts from a HubSpot list). Sets the Twain LinkedIn campaign and optional HeyReach campaign IDs, then normalizes the incoming lead fields (name, email, company, LinkedIn URL, and signal context). Deduplicates leads using a stable unique identifier so previously processed contacts are skipped on future runs. If the lead has no LinkedIn profile URL but has an email, optionally looks up the LinkedIn URL using Findymail (or an alternative provider you enable) and merges it back into the lead. If a LinkedIn URL is available, calls the Twain Generate Sequence API to research the lead and generate an intro message plus follow-ups, or posts an error to Slack if generation fails. Formats the generated messages into a review-friendly summary and posts the draft to a Slack channel for manual sending, w
Draft and stage LinkedIn re-engagements with HeyReach, Twain, and Slack
Quick overview This workflow runs weekly (or manually) to pull tagged “cold” HeyReach conversations, uses Twain to draft context-aware re-engagement messages, then stages leads in a HeyReach list and notifies Slack for review while tagging processed leads to avoid duplicates. How it works Runs on a weekly schedule or via a manual trigger. Fetches all conversations from the HeyReach Inbox API using pagination. Filters conversations by HeyReach lead tags (include tags like “Cold”/“Not interested” and exclude tags like “Re-engaged”) and extracts each lead’s LinkedIn URL, name, and prior message thread. Sends the conversation context to Twain to generate a re-engagement sequence draft and add the contact to the specified Twain campaign. Adds the lead to a HeyReach re-engagement list and stores the first Twain draft message in a custom user field. Posts the drafted re-engagement message to a Slack channel for review. Tags the lead as “Re-engaged” in HeyReach to prevent reprocessing. Setup Add HeyReach API credentials for HTTP Header Auth and ensure the header matches HeyReach requirements (for example, X-API-KEY). Add Twain API credentials for HTTP Header Auth and ensure the header matc
Score call audio and alert risky calls with Tyto and Slack
Quick overview This workflow receives a webhook when a call recording is ready, sends the audio URL to a self-hosted ai-coustics Tyto scoring API, and posts a Slack alert for risky calls before returning the scored JSON response. How it works Receives a POST webhook containing an audio_url and call_id for a completed call. Sends the audio URL and call ID to a self-hosted Tyto scoring endpoint via HTTP to retrieve a risk_score, band, and main degradation cause. Checks whether the returned band indicates a risky call (band equals "bad"). Posts a formatted alert to a selected Slack channel with the call ID, risk score, band, cause, and duration when the call is risky. Labels non-risky calls as OK. Returns the resulting JSON payload (including the Tyto scoring fields) as the webhook response for downstream storage or chaining. Setup Deploy and run a Tyto HTTP wrapper on a machine that has the ai-coustics Tyto SDK and a valid ai-coustics license key. Update the api_base_url value to point to your Tyto wrapper (for example, http://localhost:8000) and ensure the wrapper exposes a POST /score endpoint. Add a Slack credential in n8n and select the target channel for the alert message. Copy
Send monthly rent and sales market updates to Slack with Rentcast and Supabase
Quick overview Youtube Video: https://youtu.be/zJlncb1T074 This workflow runs monthly, checks Supabase for up-to-date real estate market records for a configured ZIP code, and either reports existing month-over-month rent and sale trends or fetches fresh market stats from the Rentcast API, upserts them into Supabase, and posts to Slack. How it works Runs on a monthly schedule and sets the target ZIP code to analyze. Queries Supabase for rental and sales market records for that ZIP code that are older than the start of the current month. If prior data exists, calculates the last 3 months of average rent and average sale price changes from Supabase history fields and posts a status summary to Slack (or alerts if comparisons are not possible). If no up-to-date data exists, requests the latest market statistics from the Rentcast markets API for the same ZIP code. Upserts the returned rental and sales metrics (including history) into Supabase tables for market_rentals and market_sales. Computes month-over-month changes from the newly fetched history and posts the formatted market update to Slack (or sends an error alert if insufficient data is returned). Setup Create/connect Supabase cr
Send monthly real estate market summaries to Slack with Supabase and Rentcast
Quick overview Youtube Video: https://youtu.be/zJlncb1T074?si=fnKE7SPh7I-JGdmx This workflow runs monthly for a configured ZIP code, checks Supabase for recent market rental and sales records, and either reports the existing stats or pulls fresh data from the Rentcast API, upserts it into Supabase, and posts a formatted market update to Slack. How it works Runs on a monthly schedule and sets the target ZIP code to analyze. Queries Supabase tables for rental and sales market records for that ZIP code that are older than the start of the current month. If existing data is found, calculates month-over-month changes from the stored history and posts a Slack update (or an admin error message if the history is insufficient). If no current data exists, fetches the latest rental and sales market statistics from the Rentcast Markets API. Upserts the fetched rental and sales statistics (including history and summary fields) into Supabase using the REST endpoint. Calculates month-over-month changes from the newly fetched history and posts a Slack market summary, or posts an error message if the data is incomplete. Setup Create a Supabase project with market_rentals and market_sales tables and
Notify Slack about new marketplace templates with the n8n Templates API
Quick overview This workflow runs every two hours to check the n8n public Templates API for the latest workflows in a chosen category, tracks which template IDs have already been seen using workflow static data, and posts a Slack digest when new templates appear. How it works Runs on a schedule every 2 hours. Loads configuration values such as the template category slug, the Slack channel, how many templates to check, and whether to report when none are new. Calls the n8n Templates search API to fetch the most recent templates for the configured category. Extracts key metadata (ID, title, description snippet, creator, date, and URL) from the API response. Compares the fetched template IDs against previously seen IDs stored in workflow static data and updates the cache with the latest IDs. If new templates are found, formats a Slack digest and posts it to the configured Slack channel. If no new templates are found and reporting is enabled, posts a “no new templates” all-clear message to Slack. Setup Add Slack credentials in n8n with permission to post messages to your target channel. Update the Configuration values for categorySlug and slackChannel (and optionally templatesToCheck a
Monitor target account funding, acquisitions, and exec moves with Datahyena and Slack
Quick overview This workflow runs every morning and checks Datahyena for funding events, acquisitions, and executive moves from the last 24 hours, then posts matching updates for your target account domains to a Slack channel. How it works Runs every day at 9:00 AM. Loads a list of target company domains to monitor. Fetches the last 24 hours of funding events from the Datahyena API, filters to events where the company domain matches your target list, and posts each match to Slack. Fetches the last 24 hours of acquisition events from the Datahyena API, filters to deals where either the acquirer or target domain matches your list, and posts each match to Slack. Fetches the last 24 hours of executive move events from the Datahyena API, filters to moves where the current or previous company domain matches your list, and posts each match to Slack. Setup Create a Datahyena API key and configure an HTTP Header Auth credential with header name X-API-Key for the three Datahyena HTTP requests. Update the target domain list in the workflow’s target accounts step (the domains array). Connect your Slack credential and select the channel for the three Slack message steps.
Alert on API contract drift using Data Tables and Slack
Quick overview This workflow runs on a schedule, polls a JSON API endpoint, derives and stores a snapshot of the response schema in an n8n Data Table, and posts a Slack alert only when the response structure or field types change. How it works Runs every 6 hours on a schedule. Loads the configured API endpoint URL, an endpoint key used for snapshotting, and the target Slack channel. Fetches the endpoint with retries and skips the run if the response is not a valid JSON object or array. Derives a normalized schema (field paths, types, required/optional, and nullability) and compares it to the previous schema stored in an n8n Data Table. Upserts the latest schema snapshot back into the n8n Data Table under the same endpoint key. Posts a formatted drift report to Slack only when a high- or medium-severity contract change is detected. Setup Create an n8n Data Table (for example, “API Contract Snapshots”) with text columns named endpointKey and schema_object, and select its ID in both the read and upsert steps. Add a Slack API credential in n8n. Update the Settings values for endpointUrl, endpointKey, and slackChannel (Slack channel ID) to match your API and destination channel. Run the
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
Track Pennylane invoice payment status with Slack notifications
Who is this for Teams using Pennylane (French accounting platform) who want automatic alerts when invoices are paid or become overdue, without checking Pennylane manually. What it does This workflow runs every 15 minutes, fetches all customer invoices from Pennylane, and classifies them as paid, overdue, or upcoming. If any invoices have been paid or are overdue, it sends a summary notification to Slack. If everything is normal, the workflow ends silently. How to set up Import this workflow into n8n Create a Header Auth credential with name Authorization and value Bearer <YOUR_PENNYLANE_TOKEN> Select your Slack channel in the SL Send Notification node Adjust the schedule interval in the Schedule Trigger node if needed Requirements Pennylane account with API access (Essentiel plan or higher) Pennylane API token with scope: customer_invoices:all (Optional) Slack workspace for notifications How to customize Change the polling interval in the Schedule Trigger node (default: every 15 minutes) Replace Slack with Telegram, Email, or any other notification channel Note: Pennylane API does not support filtering by status or paid fields, all classification is done client-side in a Code
SSL/TLS Certificate Expiry Monitor with Slack Alert
How It Works: The 5-Node Certificate Management Flow 🗓️ This workflow efficiently monitors your domains for certificate expiry. Scheduled Check (Cron Node): This is the workflow's trigger. It's configured to run on a regular schedule, such as every Monday morning, ensuring certificate checks are automated and consistent. List Domains to Monitor (Code Node): This node acts as a static database, storing a list of all the domains you need to track. Check Certificate Expiry (HTTP Request Node): For each domain in your list, this node makes a request to a certificate checking API. The API returns details about the certificate, including its expiry date. Is Certificate Expiring? (If Node): This is the core logic. It compares the expiry date from the API response with the current date. If the certificate is set to expire within a critical timeframe (e.g., less than 30 days), the workflow proceeds to the next step. Send Alert (Slack Node): If the If node determines a certificate is expiring, this node sends a high-priority alert to your team's Slack channel. The message includes the domain name and the exact expiry date, providing all the necessary information for a quick response. How to
Monitor Security Logs for Failed Login Attempts with Slack Alerts
How It Works: The 5-Node Anomaly Detection Flow This workflow efficiently processes logs to detect anomalies. Scheduled Check (Cron Node): This is the primary trigger. It schedules the workflow to run at a defined interval (e.g., every 15 minutes), ensuring logs are routinely scanned for suspicious activity. Fetch Logs (HTTP Request Node): This node is responsible for retrieving logs from an external source. It sends a request to your log API endpoint to get a batch of the most recent logs. Count Failed Logins (Code Node): This is the core of the detection logic. The JavaScript code filters the logs for a specific event ("login_failure"), counts the total, and identifies unique IPs involved. This information is then passed to the next node. Failed Logins > Threshold? (If Node): This node serves as the final filter. It checks if the number of failed logins exceeds a threshold you set (e.g., more than 5 attempts). If it does, the workflow is routed to the notification node; if not, the workflow ends safely. Send Anomaly Alert (Slack Node): This node sends an alert to your team if an anomaly is detected. The Slack message includes a summary of the anomaly, such as the number of fai
Monitor Email Data Breaches with HIBP API and Send Slack Alerts
How It Works: The 5-Node Security Flow This workflow efficiently performs a scheduled data breach scan. 1. Scheduled Check (Cron Node) This is the workflow's trigger. It schedules the workflow to run at a specific, regular interval. Function:** Continuously runs on a set schedule, for example, every Monday morning. Process:* The *Cron** node automatically initiates the workflow, ensuring routine data breach scans are performed without manual intervention. 2. List Emails to Check (Code Node) This node acts as your static database, defining which email addresses to monitor for breaches. Function:** Stores a list of email addresses from your team or customers in a single, easy-to-update array. Process:** It configures the list of emails that are then processed by the subsequent nodes. This makes it simple to add or remove addresses as needed. 3. Query HIBP API (HTTP Request Node) This node connects to the HaveIBeenPwned (HIBP) API to check for breaches. Function:** Queries the HIBP API for each email address on your list. Process:** It sends a request to the HIBP API. The API responds with a list of data breaches that the email was found in, if any. 4. Is Breached? (If Node) This is t
Monitor Domains & IPs on AbuseIPDB Blacklist with Slack Alerts
⚙ How It Works The automated blacklist monitor is designed to be a proactive, not reactive, tool. Here is the high-level process: Scheduled Checks: At regular intervals (e.g., every 30 minutes or every hour), a monitoring script or service sends a request to a list of predefined DNS blacklists (DNSBLs) and real-time blackhole lists (RBLs). Lookup Queries: For each check, the system performs a lookup query for our specified domains and IP addresses against the various blacklists. It essentially asks, "Is our-ip-address.com on your list?" Status Evaluation: The blacklist service responds with a status: either the asset is clean or it is listed. Alerting Mechanism: If a new listing is detected, the system immediately triggers a notification. This alert contains key information like the asset that was blacklisted (domain or IP), the specific blacklist it was found on (e.g., Spamhaus), and the time of detection. Status Logging: The status of each asset (clean or listed) is logged in a central dashboard. This allows us to track the history of an IP or domain, see when a listing occurred, and when it was resolved. Setup Steps Follow these steps to set up the automated blacklist monitor. S
Automated Real Estate Property Lead Scoring with BatchData
How It Works This workflow automates the real estate lead qualification process by leveraging property data from BatchData. The automation follows these steps: When a new lead is received through your CRM webhook, the workflow captures their address information It then makes an API call to BatchData to retrieve comprehensive property details A sophisticated scoring algorithm evaluates the lead based on property characteristics like: Property value (higher values earn more points) Square footage (larger properties score higher) Property age (newer constructions score higher) Investment status (non-owner occupied properties earn bonus points) Lot size (larger lots receive additional score) Leads are automatically classified into categories (high-value, qualified, potential, or unqualified) The workflow updates your CRM with enriched property data and qualification scores High-value leads trigger immediate follow-up tasks for your team Notifications are sent to your preferred channel (Slack in this example) The entire process happens within seconds of receiving a new lead, ensuring your sales team can prioritize the most valuable opportunities immediately.. Who It's For This workflow
National Weather Service 7-Day Forecast in Slack
Weather via Slack 🌦️💬 Overview This workflow provides real-time weather updates via Slack using a custom Slack command: /weather [cityname] Users can type this command in Slack (e.g., /weather New York), and the workflow will fetch and post the latest forecast, including temperature, wind conditions, and a short weather summary. While this workflow is designed for Slack, users can modify it to send weather updates via email, Discord, Microsoft Teams, or any other communication platform. How It Works Webhook Trigger – The workflow is triggered when a user runs /weather [cityname] in Slack. Geocoding with OpenStreetMap – The city name is converted into latitude and longitude coordinates. Weather Data from NOAA – The coordinates are used to retrieve detailed weather data from the National Weather Service (NWS) API. Formatted Weather Report – The workflow extracts relevant weather details, such as: Temperature (°F/°C) Wind speed and direction Short forecast summary Slack Notification – The weather forecast is posted back to the Slack channel in a structured format. Requirements A custom Slack app with: The ability to create a Slash Command (/weather) OAuth permissions to post message
New TheHive Case Slack Notification Bot
Streamline Case Management in TheHive via Slack! Our TheHive Slack Integration empowers SOC analysts by allowing them to efficiently manage and update case attributes directly within Slack, reducing the need to switch contexts and enhancing response time. Key Features: Direct Case Management**: Modify case details such as assignee, severity, status, and more through intuitive form inputs embedded within Slack messages. Seamless Integration**: Assumes matching email addresses between TheHive and Slack users for straightforward assignee updates. Note: Ensure email consistency to avoid assignment errors. Instant Case Actions**: Quickly close cases as false positives or adjust threat levels with minimal clicks, directly impacting case status in TheHive and reflecting updates immediately in Slack. Task Management**: Add tasks to cases through a user-friendly modal popup, fostering better task tracking and delegation within your team. Operational Benefits: Efficiency**: Enables analysts to perform multiple case actions without leaving Slack, streamlining workflows and saving valuable time. Accuracy**: Reduces the chances of human error by providing a controlled interface for case updates
Import Productboard Notes, Companies and Features into Snowflake
This workflow imports Productboard data into Snowflake, automating data extraction, mapping, and updates for features, companies, and notes. It supports scheduled weekly updates, data cleansing, and Slack notifications summarizing the latest insights. Features Fetches data from Productboard (features, companies, notes). Maps and processes data for Snowflake tables. Automates table creation, truncation, and updates. Summarizes new and unprocessed notes. Sends weekly Slack notifications with key insights. Setup Configure Productboard and Snowflake credentials in n8n. Update Snowflake table schemas to match your setup. Replace Slack channel ID and dashboard URL in the notification node. Activate the workflow and set the desired schedule.
Qualys Scan Slack Report Subworkflow
Introducing the Qualys Scan Slack Report Subworkflow—a robust solution designed to automate the generation and retrieval of security reports from the Qualys API. This workflow is a sub workflow of the Qualys Slack Shortcut Bot workflow. It is triggered when someone fills out the modal popup in slack generated by the Qualys Slack Shortcut Bot. When deploying this workflow, use the Demo Data node to simulate the data that is input via the Execute Workflow Trigger. That data flows into the Global Variables Node which is then referenced by the rest of the workflow. It includes nodes to Fetch the Report IDs and then Launch a report, and then check the report status periodically and download the completed report, which is then posted to Slack for easy access. For Security Operations Centers (SOCs), this workflow provides significant benefits by automating tedious tasks, ensuring timely updates, and facilitating efficient data handling. How It Works Fetch Report Templates:** The "Fetch Report IDs" node retrieves a list of available report templates from Qualys. This automated retrieval saves time and ensures that the latest templates are used, enhancing the accuracy and relevance of repor
Qualys Vulnerability Trigger Scan SubWorkflow
This workflow is triggered by a parent workflow initiated via a Slack shortcut. Upon activation, it collects input from a modal window in Slack and initiates a vulnerability scan using the Qualys API. Key Features Trigger:** Launched by a parent workflow through a Slack shortcut with modal input. API Integration:** Utilizes the Qualys API for vulnerability scanning. Data Conversion:** Converts XML scan results to JSON for further processing. Loop Mechanism:** Continuously checks the scan status until completion. Slack Notifications:** Posts scan summary and detailed results to a specified Slack channel. Workflow Nodes Start VM Scan in Qualys: Initiates the scan with specified parameters. Convert XML to JSON: Converts the scan results from XML format to JSON. Fetch Scan Results: Retrieves scan results from Qualys. Check if Scan Finished: Verifies whether the scan is complete. Loop Mechanism: Handles the repetitive checking of the scan status. Slack Notifications: Posts updates and results to Slack. Relevant Links Qualys API Documentation Qualys Platform Documentation Parent workflow link Link to Report Generator Subworkflow
Monitor Multiple Github Repos via Webhook
What this workflow does This workflow allows you to monitor multiple Github repos simultaneously without polling due to use of Webhooks. It programmatically allows for adding and deleting of repos to your watchlist to make management convenient. Description Can monitor multiple repos simultaneously. Programmatically register or unregister repos from a list. No need for manual work. Webhook notification means no constant polling necessary. Setup 1. Creating Credentials on Github Generate a personal access token on github by following these esteps; Right hand side of page -> Settings -> scroll to bottom -> Developer Settings > Personal Access Token > Tokens (classic) > Generate New Token Give scopes: admin:repo_hook repo (if you want to use it for your own private repo) if you need more help, see here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens 2. Setting Credentials in n8n In Register Github Webhook Authenticaion > Generic Credential Type Generic Auth Type > Header Auth Header Auth > Create New Credential with Name set to 'Authorization' and Value set to 'Bearer '. (You can reuse this for Delete Github Webhook