Replicate line items on new deal in HubSpot and notify with Slack
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_wonas the Record ID of the deal triggering the HubSpot Workflowdeal_id_createas 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.
- Set up your Slack connection
- Add an error Workflow to monitor errors
Replicate Line Items on New Deal in HubSpot and Notify with Slack
This n8n workflow automates the process of replicating line items from an existing HubSpot deal to a newly created one, and then sends a notification to Slack. This is particularly useful for businesses that frequently create new deals based on previous ones, ensuring consistency and saving manual data entry time.
What it does
This workflow performs the following steps:
- Listens for a Webhook Trigger: The workflow is initiated by an incoming webhook, likely from HubSpot when a new deal is created or updated.
- Performs an HTTP Request: It makes an HTTP request to an external API (presumably HubSpot's API) to fetch data, which might include details of the existing deal or line items.
- Edits Fields (Set): The data received from the HTTP request is then processed and transformed. This step likely extracts and formats the necessary line item information to be used for the new deal.
- Sends Slack Notification: Finally, a message is posted to a specified Slack channel, informing stakeholders about the successful replication of line items for the new deal.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- HubSpot Account: Access to a HubSpot account with API access enabled.
- HubSpot API Key/Credentials: Credentials configured in n8n to interact with the HubSpot API.
- Slack Account: A Slack workspace where notifications will be sent.
- Slack API Token/Credentials: Credentials configured in n8n to post messages to Slack.
- Webhook Configuration: A webhook set up in HubSpot (or another system) to trigger this n8n workflow upon a relevant event (e.g., a new deal being created).
Setup/Usage
-
Import the Workflow:
- Download the provided JSON file for this workflow.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots menu (
...) in the top right and select "Import from JSON". - Paste the JSON content or upload the file.
-
Configure Credentials:
- HTTP Request Node: Configure the HTTP Request node (named "HTTP Request") with your HubSpot API credentials (e.g., API key, access token) and the correct endpoint URL to fetch deal or line item data.
- Slack Node: Configure the Slack node (named "Slack") with your Slack API token. You will also need to specify the channel where messages should be posted.
-
Configure Webhook Trigger:
- The "Webhook" node will provide a unique URL once the workflow is activated.
- Copy this URL and configure it in HubSpot (or your chosen system) as an outgoing webhook. This webhook should be triggered when a new deal is created or when the deal that needs line items replicated is identified.
-
Customize Data Transformation:
- Review and adjust the "Edit Fields (Set)" node to ensure it correctly extracts and formats the line item data from the HTTP Request node's output for your specific HubSpot setup. This might involve mapping fields or performing light data manipulation.
-
Activate the Workflow:
- Once all configurations are complete, activate the workflow in n8n. It will then be ready to listen for incoming webhooks and automate the process.
Related Templates
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.
AI-powered document search with Oracle and ONNX embeddings for recruiting
How it works Create a user for doing Hybrid Search. Clear Existing Data, if present. Add Documents into the table. Create a hybrid index. Run Semantic search on the Documents table for "prioritize teamwork and leadership experience". Run Hybrid search for the text input in the Chat interface on the Documents table. Setup Steps Download the ONNX model allMiniLML12v2augmented.zip Extract the ZIP file on the database server into a directory, for example /opt/oracle/onnx. After extraction, the folder contents should look like: bash bash-4.4$ pwd /opt/oracle/onnx bash-4.4$ ls allMiniLML12_v2.onnx Connect as SYSDBA and create the DBA user sql -- Create DBA user CREATE USER app_admin IDENTIFIED BY "StrongPassword123" DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users; -- Grant privileges GRANT DBA TO app_admin; GRANT CREATE TABLESPACE, ALTER TABLESPACE, DROP TABLESPACE TO app_admin; Create n8n Oracle DB credentials hybridsearchuser → for hybrid search operations dbadocuser → for DBA setup (user and tablespace creation) Run the workflow Click the manual Trigger It displays Pure semantic search results. Enter search text in Chat interface It displays results for vector and keyword search. Note The workflow currently creates the hybrid search user, docuser with the password visible in plain text inside the n8n Execute SQL node. For better security, consider performing the user creation manually outside n8n. Oracle 23ai or 26ai Database has to be used. Reference Hybrid Search End-End Example