Leadfeeder identifies companies visiting your website and converts them into high-value leads.
Leadfeeder identifies companies visiting your website and converts them into high-value leads. On Nagent, Leadfeeder is exposed as a fully-configurable analytics integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Leadfeeder into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Leadfeeder to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Leadfeeder into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Leadfeeder, with input parameters and output schema. Drop these into any step of an agent built in Helix.
LEADFEEDER_GET_ACCOUNTTool to retrieve the details of a specific account by ID. Use when you need to get information about a particular Leadfeeder account.
Input parameters
The unique identifier of the account to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEADFEEDER_GET_ACCOUNTSTool to retrieve a list of accounts the user has access to. Use when you need to discover all available Leadfeeder accounts after authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEADFEEDER_GET_ALL_VISITSTool to retrieve all visits for a specific lead. Use when you need detailed visit history for a lead, optionally filtered by date range.
Input parameters
The ID of the lead to retrieve visits for
Filter visits on or before this date (YYYY-MM-DD)
Number of visits to return per page (max 100, default 100)
The ID of the account to retrieve visits for
Filter visits on or after this date (YYYY-MM-DD)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEADFEEDER_GET_COMPANY_INFO_BY_IPTool to retrieve company information based on an IP address. Use when you need to enrich an IP and obtain its company profile. Returns 404 if no match is found.
Input parameters
A valid IPv4 or IPv6 address to enrich, e.g. '185.70.216.139' or '2620:0:862:ed1a::1'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEADFEEDER_GET_CUSTOM_FEEDSRetrieve all custom feeds configured for a Leadfeeder account. Custom feeds are saved filter configurations that help organize and segment company visits. Returns an empty list for accounts without premium features (402), non-existent accounts (404), or accounts with no custom feeds. Use LEADFEEDER_GET_ACCOUNTS first to obtain valid account IDs.
Input parameters
Unique identifier of the Leadfeeder account. Use LEADFEEDER_GET_ACCOUNTS to retrieve available account IDs
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEADFEEDER_GET_TRACKING_SCRIPTTool to retrieve the website tracking script for a given account. Use when you need to obtain the JavaScript tracking code to be inserted on webpages for visitor tracking.
Input parameters
ID of the Account to retrieve the tracking script for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 53 agents privately built on Nagent that already use Leadfeeder.
Build on Nagent
Connect Leadfeeder to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Leadfeeder, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Leadfeeder is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Leadfeeder is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Leadfeeder steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Leadfeeder event fires, the agent kicks off automatically.
Every Leadfeeder action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Leadfeeder ships with 6 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Leadfeeder together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Leadfeeder-based workflows tailored to your business.