## Introduction
In fast-paced startups and growing companies, timely communication between marketing and sales teams is critical. One recurrent challenge is ensuring that sales representatives are immediately notified as soon as a marketing lead reaches the Sales Qualified Lead (SQL) status. This prompt notification enables sales reps to quickly follow up and increase conversion rates.
This article provides a detailed, step-by-step guide to building an automated workflow using n8n, an open-source automation tool, to notify sales reps via Slack and Email when a lead hits SQL status in HubSpot. The workflow integrates multiple tools including HubSpot (CRM), Slack (communication), and Gmail (email), making it a versatile solution for marketing departments aiming for seamless collaboration with sales.
### Who Benefits?
– **Marketing Teams**: Automates lead status tracking and fosters alignment with sales.
– **Sales Reps**: Receive real-time notifications for prompt follow-ups.
– **Operations Engineers/Automation Specialists**: Manage and scale an effective, maintainable workflow.
—
## Tools and Services Integrated
– **HubSpot CRM**: To track and identify leads as they transition to SQL.
– **n8n**: The automation engine orchestrating the workflow triggers and actions.
– **Slack**: For instant messaging notifications to sales reps or sales channels.
– **Gmail** (or any email provider supported by n8n): For sending email alerts.
—
## Understanding the Workflow
### What this Automation Does:
1. Listens continuously for lead status changes in HubSpot.
2. Checks when a lead’s lifecycle stage updates to ‘SQL.’
3. Sends a Slack notification to the assigned sales rep or sales channel.
4. Sends an email alert to the sales rep and/or marketing manager.
### Workflow Trigger to Output Summary:
– **Trigger**: Webhook or polling for lead updates in HubSpot.
– **Condition Check**: Verify if the lifecycle stage is SQL.
– **Branch 1**: Format and send a Slack message.
– **Branch 2**: Format and send an Email notification.
—
## Step-by-Step Technical Tutorial
### Prerequisites
– An n8n instance running (cloud or self-hosted).
– HubSpot account with API access (ensure API key or OAuth is configured).
– Slack workspace with webhook or Bot token for sending messages.
– Gmail account connected to n8n (via OAuth).
### Step 1: Set Up HubSpot Trigger
#### Option A (Recommended): HubSpot Webhook
1. In HubSpot, create a webhook subscription under app settings to notify your n8n endpoint when a contact’s lifecycle stage is updated.
2. In n8n, add a **Webhook** node.
3. Configure it to accept POST requests.
#### Option B: Poll Lead Updates (if webhook not feasible)
1. Use a **HubSpot Trigger** node set to check contacts periodically.
### Step 2: Parse Incoming Lead Data
– Add a **Set** or **Function** node to extract and normalize relevant fields:
– Contact ID
– Email
– Lifecycle stage
– Assigned sales rep info (name, email, Slack ID if available)
### Step 3: Filter Lifecycle Stage for SQL
– Insert an **If** node.
– Condition: `lifecycle_stage` equals `salesqualifiedlead` (check exact HubSpot field value).
– Proceed only if true.
### Step 4: Retrieve Assigned Sales Rep Details (optional enhancement)
– Use a **HubSpot API** node to fetch the assigned owner’s contact info if not included.
– Useful for personalized notifications.
### Step 5: Format Slack Notification
– Add a **Slack** node for sending message.
– Configure it to:
– Identify the channel or user (e.g., sales rep’s Slack ID).
– Compose a message template:
“`
:mega: *New SQL Lead Alert!*
*Name:* {{$json[“contact_name”]}}
*Email:* {{$json[“email”]}}
*Notes:* Lead has just reached SQL status. Please follow up immediately.
“`
### Step 6: Format Email Notification
– Add an **Email** node.
– Use Gmail or SMTP mode.
– To: Sales rep’s email and/or marketing manager.
– Subject: `New Sales Qualified Lead: {{$json[“contact_name”]}}`
– Body:
“`
Hello {{$json[“owner_name”]}},
The lead {{$json[“contact_name”]}} (Email: {{$json[“email”]}}) has just been marked as SQL in HubSpot.
Please review and follow up as soon as possible.
Thanks,
Marketing Automation Bot
“`
### Step 7: Error Handling & Logging
– Add a **Catch** node connected to Slack and Email nodes.
– On failure, log errors in a Google Sheet or send an alert to admins.
– Optionally, retry sending notifications in case of transient errors.
### Step 8: Testing
– Simulate or manually update a contact in HubSpot to SQL status.
– Verify that Slack and Email notifications are received.
– Check logs for errors.
—
## Common Errors and Tips for Robustness
– **Webhook Security**: Validate HubSpot webhook payload with a secret token to avoid unauthorized calls.
– **Rate Limits**: HubSpot and Slack APIs have rate limits; implement exponential backoff and retries.
– **Data Completeness**: Ensure sales rep Slack IDs or emails exist; add fallbacks if missing.
– **Fault Tolerance**: Branch workflow to continue with partial notifications if one service is down.
– **Logging**: Maintain detailed logs and alerts for failed notifications.
—
## How to Adapt or Scale this Workflow
– **Multi-Channel Notifications**: Extend by adding SMS (Twilio) or Microsoft Teams notifications.
– **Multiple Reps or Teams**: Route notifications dynamically based on lead region or product line.
– **CRM Expansion**: Support other CRMs by adding respective API integrations (e.g., Salesforce).
– **Analytics**: Log notifications to a dashboard for tracking response times and conversion impact.
– **Automation Governance**: Use environment variables and credentials management to handle multiple workspaces or environments.
—
## Summary
By implementing this n8n-based workflow, marketing teams ensure rapid communication with sales reps when leads transition to SQL status. The integration of HubSpot, Slack, and email notifications streamlines follow-up processes, reduces manual errors, and aligns cross-functional teams.
Automation specialists can build upon this foundation by adding robustness, scaling capabilities, and multi-channel alerts to fit evolving organizational needs. This practical example demonstrates how orchestration tools like n8n empower teams to create tailored, actionable workflows for real business challenges.
—
## Bonus Tip: Using Dynamic Slack Mentions and Escalation
To improve responsiveness, configure the Slack node to mention the assigned rep dynamically using their Slack user ID. If the rep does not acknowledge within a set time, escalate the notification to a manager or team channel using n8n’s wait and conditional nodes.
This ensures that the lead never slips through the cracks and enables a culture of accountability.