CRM Automation Workflows · Lesson 2 of 10
20% complete
← Course Home
CRM Automation Workflows
1CRM Integration Basics 2Your First Automation 3Lead Routing Logic 4Sequence Enrollment Triggers 5HubSpot Deep Dive 6Salesforce Configuration 7Slack Alert Architecture 8Return Visit Automation 9Data Quality Automation 10Measuring Automation Impact
Lesson 2 of 10

Your First Automation

Your first automation should be simple, high-value, and testable in under an hour. This lesson walks through building the single most impactful visitor intelligence automation: company identified → contact created → rep notified.

The Automation Logic

When Kopimore identifies an ICP-fit company visiting your site, the automation should: (1) Check if the company already exists in your CRM, (2) If not, create a company record with enriched firmographic data, (3) Look up and create 1–2 decision-maker contacts via enrichment, (4) Notify the assigned rep via Slack DM with company details and visit context.

Building It in HubSpot

In HubSpot Workflows, create a Company-based workflow. Trigger: "Company is enrolled via Kopimore integration." Action sequence: Set company owner (via round-robin or territory rule) → Create contact associated to company → Send Slack notification to company owner → Create task: "Follow up with [Company] — visited pricing page."

Building It in Salesforce

In Salesforce Flows, create a Record-Triggered Flow on Account creation (when created by Kopimore integration). Add decision elements to check territory, then create a Lead or Contact, create a Task for the assigned rep, and send an Apex-triggered Slack message.

Testing Your First Automation

After building, test by visiting your own website from a new IP (mobile hotspot) using a company domain that doesn't already exist in your CRM. Within 5 minutes, you should see: a new company record in your CRM, an associated contact, and a Slack notification to the assigned rep. If any step is missing, check the Kopimore integration logs and CRM workflow error logs.

Key Takeaways
  • Start with one automation: company identified → contact created → rep notified
  • Test with a mobile hotspot visit from a domain not in your CRM — validate all three outcomes
  • Check both Kopimore integration logs and CRM workflow logs when debugging
  • This single automation is the highest-ROI starting point — build complexity from here
← CRM Integration BasicsLead Routing Logic →