[ HubSpot / Lead routing ]

HubSpot lead routing that reads the lead

engini checks HubSpot for new contacts as often as every 15 minutes. An AI agent matches each one to an existing company and owner, scores it against your ideal customer with data you already hold, sets the owner and lifecycle stage, and alerts the rep in Slack or Teams with a drafted first email. Leads nobody touched get reassigned on a schedule.

HubSpotSlackSnowflakeOutlook or Gmail
Read the HubSpot guide →
A demo request comes in
  1. HubSpot logo
    Contact createdchecked every 15 min
  2. Agent matches and scoresexisting company found; fits your ICP
  3. HubSpot logo
    Owner and stage setcompany owner keeps the relationship
  4. Slack logo
    Rep alertedcontext and a drafted first email
Illustration of the flow on this page, not a product screen.
What it does
Match, score and assign new HubSpot contacts; alert the rep
Systems
HubSpot, your warehouse or database, Slack or Teams
Built with
A workflow on a HubSpot trigger with an AI agent step
Your control
Your scoring rules, territories and SLA
[ 01 / The problem ]

Slow follow-up is usually a routing problem

Blurred landscape photo with the words Lead routing and the labels Trigger, Match, Assign, Alert

A lead fills a form and waits while someone works out who should get it: is the company already a customer, which territory is it in, is it worth a call today. LeanData describes response time as mostly routing, matching and enrichment rather than rep speed. HubSpot’s own rotation tools assign by turn, not by what you know about the account.

Where routing goes wrong

  • A contact from an existing company goes to a new rep.
  • Scoring uses form fields, not what you know about the company.
  • The rep gets a notification and no context.
  • Nobody notices a lead that was never worked.

Routing with judgment

engini checks HubSpot for new contacts as often as every 15 minutes, so a lead is routed within that window. An AI agent step uses associations to find the company and its owner, pulls what you already know from your warehouse or database, scores the lead with your rules in plain language, and sets owner and lifecycle stage. The owner gets a Slack or Teams message with context and a drafted first email. A scheduled workflow reassigns leads still untouched after your SLA.

[ 02 / How it works ]

Every lead, routed in one pass

01 / Trigger

Contact created

An engini trigger on created contacts, checked as often as every 15 minutes, starts the workflow.

02 / Match

Company and context

An AI agent step finds the company and its owner and enriches the lead from your warehouse or database.

03 / Assign

Score and owner

It scores the lead against your rules and sets owner and lifecycle stage.

04 / Alert

Rep and SLA

The owner gets a Slack or Teams message with a drafted first email; a scheduled check reassigns untouched leads.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
HubSpotContacts, companies, owners (associations)Read
HubSpotContact owner, lifecycle stage, routing notesUpdate
Snowflake, Databricks or a databaseFirmographics and product usage you already holdRead
Slack or TeamsAlerts and drafted first emails to the ownerWrite

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the HubSpot logo, the engini mark and a thin line, labeled every 15 min: contact, match + score, owner alerted

Editorial image: one lead, the right route.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when a contact is created in HubSpot, look for the associated company; if it has an owner, set the contact owner to the company owner, otherwise assign by country (US and Canada to Dana, everyone else to Lior). Then send the owner a Slack message with the contact's name, company and a drafted first email.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect HubSpot, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

How fast is HubSpot lead routing with engini?

engini checks HubSpot for new contacts as often as every 15 minutes, so each lead is routed within that window.

Can the agent match a lead to an existing company and owner?

Yes. It uses HubSpot associations and the email domain to find the company and keeps the lead with the company owner.

Where does enrichment data come from?

From data you already hold: your warehouse, a database or a sheet engini can read. engini does not supply third-party data.

What happens when a lead is not worked in time?

A scheduled workflow finds leads untouched after your SLA, reassigns them by your rule and tells the manager.