Happierleads
Sales IntelligenceIdentify B2B website visitors with Happierleads, reading identified leads, enriching domains, and managing tracking. Agents route a warm account to sales while the visit is still recent.
What This Integration Enables
Happierleads answers one question about your website: which companies were here. Not which people, which companies. That distinction is the whole design, and it is worth stating plainly rather than blurring, because it determines what a workflow built on top is allowed to do. List Identified Leads returns the organization behind a visit with domain, name, industry, employee count, revenue band, location, visit count, lead score and tags. The filters cover visitor and company type, geography of the visitor or of the headquarters, industry, technology, pages visited, UTM parameters, CRM sync status, intent topic and numeric ranges. Enrich Company will build the same firmographic picture from nothing but a domain, which is useful well outside visitor work.
The second half of the connector is administration, and it matters more than administration usually does. Happierleads is metered per website, Get Website is the credit balance endpoint, and a newly created site starts with unlimited credit access. An agency provisioning a tracked site per client through Create Website and forgetting to follow with Set Website Limits can drain the account quota very quickly. That is exactly the kind of unattended spend an Orchestration as a Service platform exists to keep supervised. FlowRunner agents read the balance on a cadence, cap new sites at creation time, and raise the ceiling as a decision rather than a default. Intent Topics extend the surface in a different direction: subscribing to a topic surfaces in-market companies researching that subject, which is a genuinely useful list and, importantly, not a list of people who visited your site.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Yesterday's visitors, routed while they are still warm
Each morning an agent calls List Identified Leads for the previous day, filtered to the industries and employee bands the team actually sells to. It calls Enrich Company on each new domain, checks the results against HubSpot to separate existing accounts from new ones, and assembles a digest. Existing accounts with an open opportunity go to the deal owner with the pages read attached, because a prospect rereading the pricing page mid-cycle is a different message than a cold one. New accounts go to a review queue. Nothing enters a sequence on the strength of a visit alone.
Provisioning a tracked site without handing over the account quota
An agency onboards a client. The agent calls Create Website for the new domain, then immediately calls Set Website Limits to cap the credits and email accounts that site may consume, because an unbounded site can take the whole account allowance. It calls Update Website Settings to configure the identification level, the digest schedule and recipients, and the HTTPS webhook that will receive each newly captured lead. It then calls Get Website daily and posts to Slack when remaining credits fall below the threshold for that client's plan. Provisioning becomes a flow with a ceiling on it rather than a checklist somebody half completed.
Validating the ideal customer profile against who actually shows up
Once a quarter an agent calls Get Website Analytics for the aggregate breakdowns of identified visitors by industry, company size, job title and country. It then calls Get Website Daily Stats for the per-day series covering leads identified and prospected, emails sent and scheduled, and average ICP score. It writes both into Google Sheets next to the segments the team says it targets. Where the traffic profile and the stated profile disagree, that is a finding for the humans who set the strategy, not a threshold for the agent to act on. The daily series also doubles as a health check, because a sudden drop usually means exhausted credits or a broken tracking script rather than a market shift.
Human-in-Loop Highlight
Happierleads tells you an organization was on your site. It cannot tell you why, and the API gives an agent no way to learn. There is no suppression list to manage from a flow. The filters on List Identified Leads are categorical, covering visitor and company type, industry, geography and technology, and the GDPR suppression control on Update Website Settings is a site-wide switch rather than a judgment about one account. So the same daily pull contains a buying committee doing genuine research, your own agency checking a page it built, a competitor's product marketer reading the comparison page, and an ISP whose network range resolved to something plausible. All four look identical: a domain, a headcount, a lead score, a list of pages. Sequencing the wrong one is not a silent mistake, it is an unsolicited email to a competitor or to a customer you already have, sent in your company's name.
So the agent routes rather than acts. Accounts that already match a CRM record go to their existing owner with the pages read attached. Everything else goes to a review queue in Slack, one message per account, carrying the domain, the firmographics from Enrich Company, the page path, the visit count and the recognition confidence, and asking the demand generation owner one question: is this a buyer, an existing relationship, or noise. Answers feed a suppression list held in FlowRunner, since the connector does not hold one. The agent keeps identifying visitors every night without being asked. It does not decide which of them deserves a message.
Agent Capabilities
15 actionsIdentified Visitors
2- List Identified Leads Returns the companies identified as visiting a tracked website within a date range, with domain, company name, industry, employee count, revenue band, location, visit count, lead score and tags. Filters cover visitor and company type, geography of the visitor and of the headquarters, industry, technology, pages visited, UTM parameters, CRM sync status, intent topic, and numeric ranges for visits, employees, revenue and score. Dates use MM/DD/YYYY. The response also lists the automations currently active on the site.
- Enrich Company Returns firmographics for a company domain, including legal name, founding year, company type, sector, industry, country, estimated annual revenue band, employee range, Alexa rank, LinkedIn page and a short summary. Useful anywhere a workflow has a domain and needs an account record, not only on visitor traffic.
Website Administration
5- List Websites Lists the websites on the account with their identifiers, names, domains, client IDs, validation URLs and verification status, searchable by name and filterable to verified, unverified or removed sites. This is how a flow discovers the website ID that most other actions require.
- Get Website Returns the configuration and remaining quota for one tracked website, including credit and email-account limits alongside what is still available, plus GDPR suppression, digest settings and the tracking script. This is the credit balance endpoint, so it is what a flow reads to gate a run or raise an alert.
- Create Website Creates a new tracked website and returns its identifier. A newly created site has unlimited credit access by default, so this action should never be the last one in a provisioning flow.
- Set Website Limits Sets the credit and email-account ceilings for a tracked website. Setting credits to zero disables tracking for that site entirely. Called immediately after Create Website, because an unbounded site can exhaust the account quota quickly.
- Update Website Settings Updates a tracked website's configuration, including site URL and domain, GDPR suppression, identification level, email tracking, digest frequency and recipients, and the HTTPS webhook that receives a POST for each newly captured lead. Only supplied fields change. Setting the webhook resets its failure counter and stamps a new activation date, and only HTTPS endpoints are accepted.
Measurement
2- Get Website Analytics Returns aggregate breakdowns of identified visitors over a rolling window, grouped by industry, company size, job title and country with counts for each. Used to profile who is actually arriving and to test a stated ideal customer profile against real traffic.
- Get Website Daily Stats Returns a per-day series covering leads identified, leads prospected, emails sent and scheduled, the average ICP score and how many leads carried one. Used to chart volume over time and to catch a drop caused by exhausted credits or a broken tracking script.
Export
2- Start CSV Export Queues a CSV export of identified leads for a date range and returns an acknowledgement. The finished file is emailed rather than returned in the response. Dates here use YYYY-MM-DD, unlike List Identified Leads. The export can be restricted to leads carrying contacts or extended to include LinkedIn data.
- Get CSV Export Status Returns the progress of an export job as it moves through gathering_data, formatting, compressing, uploading and generating_url before reaching complete or ready, or error on failure. A finished job carries a download URL. Because the start call returns only an acknowledgement, the export ID has to come from elsewhere in the workflow.
Intent Topics
4- List Intent Topics Lists the third-party intent topics a website is subscribed to, with slugs, daily limits and paused state, plus a count of active subscriptions. It also reports whether the Intent Signals feature is enabled, returning successfully with a false flag rather than erroring when it is not.
- Get Intent Topic Catalog Returns the catalogue of topics available to subscribe to, with the slug each subscription requires. Called before subscribing, since an unrecognised slug is rejected.
- Subscribe To Intent Topic Subscribes a website to an intent topic so in-market companies researching that subject appear in the leads table. The operation is idempotent: re-subscribing an existing topic unpauses it and updates its daily limit.
- Unsubscribe From Intent Topic Permanently removes a topic subscription from a website. Leads already delivered keep the topic on their record. To stop delivery temporarily without losing the subscription, pause it rather than unsubscribing.
Frequently Asked Questions
What can FlowRunner do with Happierleads?
FlowRunner agents can run List Identified Leads, Enrich Company, and Get Website in Happierleads, plus 12 more actions.
Does connecting Happierleads to FlowRunner require OAuth?
No. Happierleads connects to FlowRunner with an API key, no OAuth flow required.
Can Happierleads trigger a FlowRunner workflow automatically?
Happierleads doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Happierleads
$100 in credits. No card required. Connect in minutes.