Replicate Line Items on New Deal in HubSpot Workflow Use Case This workflow solves the problem of manually copying line items from one deal to another in HubSpot, reducing manual work and minimizing errors. What this workflow does Triggers** upon receiving a webhook with deal IDs. Retrieves** the IDs of the won and created deals. Fetches** line items associated with the won deal. Extracts** product SKUs from the retrieved line items. Fetches** product details based on SKUs. Creates** new line items for the created deal and associates them. Sends** a Slack notification with success details. Step up steps Create a HubSpot Deal Workflow 1.1 Set up your trigger (ex: when deal stage = Won) 1.2 Add step : Create Record (deal) 1.3 Add Step : Send webhook. The webhook should be a Get to your n8n first trigger. Set two query parameter : deal_id_won as the Record ID of the deal triggering the HubSpot Workflow deal_id_create as the Record ID of the deal created above. Click Insert Data -> The created object Set up your HubSpot App token in HubSpot -> Settings -> Integration -> Private Apps Set up your HubSpot Token integration using the predefined model.
Tags
Related workflows
See all Slack→Manage Slack channel and users automatically
Explore this workflow on its official n8n template page.
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 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