Skip to main content
When visitor identification recognizes someone on your website, the best time to say hello is while they’re still interested. A workflow can tell your team the moment it happens. This guide makes a workflow that emails Northwind’s sales team when a visitor to its website is identified, and tests it with a real visitor.

​
Start with the trigger

1

Make a new workflow

Click Workflows in the left rail, then New Workflow. Give it a Name, such as “Tell me when a company visits”, and click Create Blank Workflow. A new workflow starts switched off.
2

Add the Website Visitor Trigger

Click the gear at the top right, then Browse All Nodes. Search for “visitor” and click Website Visitor Trigger.
Add Node, searched for visitor, 11 results. Triggers: Website Visitor Event, and Website Visitor Trigger, outlined; both read: Starts when Hiveku learns who a visitor to your website is (their email or company)

The visitor triggers

3

Pick the website

Under Website, choose your site. The line under it says whether tracking is active there. Trigger event is Visitor identified.
Website Visitor Trigger, Visitor identified on Northwind Coffee Roasters. Website: Northwind Coffee Roasters, outlined, Tracking is active. Trigger event: Visitor identified, outlined, Runs when Hiveku first learns who a visitor is: their email from a form, or their company from visitor identification. Once per visitor

Visitor identified on Northwind's website

The workflow starts the first time Hiveku learns who a visitor is: their company from visitor identification, or their email from a form they filled in. It starts once per visitor, never twice. The trigger’s Output tab lists what it passes on: the visitor’s name, email, company, company size, industry, job title, city and more. A detail Hiveku doesn’t know comes through blank.
Website Visitor Trigger, Output tab: 46 fields. Visitor: Visitor ID, Name, outlined, Email, Work email, Company, outlined, Company domain, Industry, Company size, Job title

What the trigger passes on

​
Email your team

1

Add Send Email and connect it

Add Send Email the same way: gear, Browse All Nodes. A new step isn’t connected to anything, so drag from the small dot on the right of the trigger to the dot on the left of Send Email. A line joins them.
Website Visitor Trigger, Visitor identified on Northwind Coffee Roasters, joined by a line, outlined, to Send Email, To sales-team@example.com

The trigger connected to the email

2

Write the email

Click Send Email and fill in:
  • To: your team’s address. Separate several addresses with commas.
  • Subject and Body (plain text): what the email says. To put in a detail about the visitor, click the trigger, open its Output tab and click the field, such as Name or Company, to copy it. Then click Send Email again and paste it where it should go.
Put each detail on its own line, so the email still reads well when one of them is blank.
Send Email: To, sales-team@example.com, outlined; Subject, Someone we know is on our website, followed by the visitor's name, outlined; Body, Hiveku just learned who is visiting the website, then Name, Company and Job title lines, each followed by that detail, outlined

Who gets it, and what it says

Click Save Workflow.

​
Test it with a real visitor

1

Pick a visitor

Click the trigger and open its Input tab. Under Test sample, click a visitor Hiveku has identified, shown by name. Visitors shown as Anonymous visitor haven’t been identified, so they wouldn’t start the workflow.
Test sample: Test run uses Priya Shah as the visitor, outlined, with Clear sample; the list of visitors, with Priya Shah, last seen 10/22/2026, ticked and outlined among several Anonymous visitor rows

An identified visitor as the test sample

2

Click Test Run

A test never sends anything. Click Send Email, then its Output tab: Test run: not sent, and Merge values (dry run) shows what each detail became.
Test completed, 2/2 steps, outlined. Send Email, Done, To sales-team@example.com: Someone we know is on our website. Merge values: visitor.name resolved Priya Shah in Subject and in Body, outlined; visitor.company and visitor.job_title resolved to blank in Body, outlined; visitor.email resolved in Body

What the email would have said

Priya Shah filled in a form on Northwind’s website, so Hiveku knows her name and email but not her company. A visitor recognized by visitor identification comes with the company too.

​
Switch it on

When the test looks right, click the switch at the top so it reads Enabled. From then on, every newly identified visitor on that site emails your team. Northwind deleted its test workflow instead: Manage on the Workflows page, … on its row, Delete, then Delete workflow.

​
Good to know