Turn hiring signals into ready leads. The flow catches new job intent from a webhook, enriches the data, and routes it into your CRM. Sales teams get clean contacts and clear next steps fast.

An incoming webhook sends company and person details. The system looks up the company in HubSpot by domain, updates it if found, or creates a new account if not. It builds or updates the contact, then checks status and context. If the person has an email, it adds them to an email campaign in Lemlist and logs a LinkedIn outreach step in HubSpot. If the account is a customer, the Customer Success channel in Slack gets a message. If a deal is open, sales gets a Slack alert. If the lead status shows attempted to contact, a follow up task is created in HubSpot.

Setup needs HubSpot, Slack, Lemlist, and Dropcontact connected in n8n, plus a webhook source. Expect faster handoffs and less data entry. It fits teams that act on hiring news to start timely outreach and protect existing accounts.

• Webhook intake for new hiring intent events and lead details
• Company search in HubSpot by domain with create or update path
• Contact create or update and association with the right company
• Email enrichment via Dropcontact using name and domain
• Auto add the lead to a Lemlist campaign when an email exists
• Create a HubSpot follow up task when status is attempted to contact
• Slack alerts to Sales or Customer Success based on deal and customer checks
• Log LinkedIn outreach steps in HubSpot for social follow up

• Reduce manual research from 30 minutes per lead to 2 minutes
• Streamline lead routing across CRM and outreach tools by 80%
• Improve email accuracy by up to 60% with enrichment
• Notify the right team in real time for faster response
• Keep account and contact records current without manual updates
• Connect 4 systems seamlessly in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with HubSpot, Slack, Lemlist, Dropcontact and Webhook. See the Tools Required section above for links to create accounts with these services.
3. Open the Webhook node and copy the production URL. In your source app or service, send a POST request with company and person fields to this URL. Use a test tool if needed to send a sample event.
4. Connect HubSpot: double click any HubSpot node, choose Credential to connect with, click Create new credential, then follow the on screen steps to sign in with OAuth and approve access.
5. Connect Slack: double click each Slack node, create a new OAuth credential, pick your workspace, approve permissions, and save.
6. Connect Lemlist: double click the Lemlist node, create a new API Key credential, get your API key from your Lemlist account settings, paste it, and save. Set the campaign name or ID you want to use.
7. Connect Dropcontact: double click the Dropcontact node, create a new API Key credential, get the key from your Dropcontact account, paste it, and save. Make sure you have enough credits.
8. Verify field mappings: in the company search node, confirm the domain field points to the webhook payload. Adjust mappings if your payload uses different keys.
9. Review decision checks: open the If nodes for customer status, open deal, and attempted to contact. Update values to match your HubSpot picklists and fields.
10. Set Slack channels: in each Slack node, choose the target channels for Sales and Customer Success or paste the channel IDs.
11. Run a test: execute the workflow, send a sample webhook, and watch execution. Check that a company is created or updated, a contact is saved, Slack messages arrive, and a HubSpot task is created when the status condition matches. Confirm the lead appears in your Lemlist campaign.
12. Troubleshoot: if no email is found, confirm name and domain are sent and that Dropcontact credits are available. If Slack fails, recheck channel access and scopes. If HubSpot search fails, make sure the domain is included. When all checks pass, set the workflow to active.