Use Leadfeeder from Claude
Add the Leadfeeder connection to a Space that runs Claude, then use it from every channel in that Space.
ConnectorLeadfeeder
Leadfeeder integration for Claude and Codex
Connect Leadfeeder once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
CategoryAnalytics & Data
Use Leadfeeder from Codex
Add the Leadfeeder connection to a Space that runs Codex, then use it from every channel in that Space.
Use Leadfeeder from Sidekick
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Analytics & Data
What the Leadfeeder connector can do
Leadfeeder, now part of Dealfront, identifies the companies visiting your website and turns that traffic into leads. A type.com Space connected to Leadfeeder can have Claude enrich an IP address into a company profile, pull a lead's visit history, or check which custom feeds are configured.
One connection, many Spaces
Connect Leadfeeder once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Use Leadfeeder from Claude Code, Codex, and automations
Use Leadfeeder from Claude Code or Codex
Once Leadfeeder is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Automate Leadfeeder on a schedule or webhook
In a Space with Leadfeeder connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
What teams do with Leadfeeder in type.com
Identify who's behind a visit
Enrich an IP address into a company profile so an anonymous website visit becomes a named account to research.
Look up the company behind this IP address in Leadfeeder.
Review a lead's full visit history
Pull all recorded visits for a lead, optionally filtered by date, to see how engaged they have been before outreach.
Get the full visit history for this lead in Leadfeeder over the last 60 days.
Check which segments are already built
Retrieve the custom feeds configured for an account so the team reuses existing filters instead of rebuilding them.
List our Leadfeeder custom feeds so I know what segments we're already tracking.
Representative actions
- Get Account
Retrieves details for a specific Leadfeeder account by ID.
- Get Accounts
Retrieves the list of Leadfeeder accounts the user can access.
- Get All Visits
Retrieves detailed visit history for a specific lead, optionally filtered by date range.
- Get Company Info by IP
Retrieves a company profile for a given IP address, returning a 404 if no match is found.
- Get Custom Feeds
Retrieves saved filter configurations used to organize and segment company visits.
Connection
API and auth details
Leadfeeder, now part of Dealfront, provides API access to website visitor, company, contact, intent, and account workflow data. Integrations can retrieve visitors, search companies and contacts, enrich IPs, manage lists and tags, inspect account usage, and use the public OpenAPI specification for structured tooling.
- Source
- type.com catalog metadata
- Auth schemes
- API key
- Official site
- https://www.dealfront.com/
FAQ
Questions people ask before connecting Leadfeeder
What can Claude do with Leadfeeder in type.com?
With a Leadfeeder connection, Claude can enrich IPs into company profiles, pull visit history, and check configured feeds, all from a shared type.com thread.
How do I connect Leadfeeder to type.com?
Leadfeeder uses an API key. An admin adds it once to the connection and controls which Spaces can use it.
Can type.com flag new website visitors automatically?
Yes. Turn a Leadfeeder check into a type.com automation, such as a daily scan of new high-intent visits, and the agent posts findings to a channel.
Can Claude Code or Codex use Leadfeeder?
Yes. Once Leadfeeder is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Can I automate Leadfeeder on a schedule?
Yes. In a Space with Leadfeeder connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Is this the same as an MCP server for Leadfeeder?
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
More analytics & data connectors
All Analytics & Data integrationsConnect Smartproxy to Claude in type.com to generate proxy endpoints, check configurations by type, and manage whitelisted IPs in a thread.
Connect Solcast to Claude in type.com to pull historical weather data and manage PV power resources from a shared team thread.
Connect Supadata to Claude in type.com to transcribe videos, map website URLs, and scrape pages into markdown from a shared thread.
Connect Taggun to Claude in type.com to read receipts, export known merchants, and keep expense data consistent across your finance team.