Leadfeeder

Leadfeeder + Konnectify

Leadfeeder Integration with Konnectify

Automatically capture company visits and lead activity from Leadfeeder, then enrich accounts and route high-intent website behavior into your workflows for faster sales follow-up and cleaner analytics.

Visits Leads Accounts 3 Triggers 2 Actions

ON THIS PAGE

→ What is Leadfeeder? → API & Authentication → How to connect → Triggers (3) → Actions (2) → Popular automations → FAQ

What is Leadfeeder?

Leadfeeder identifies companies visiting your website and tracks their behavior across pages and sessions, helping sales and marketing teams spot high-intent accounts.

By connecting Leadfeeder to Konnectify, you can automatically pull fresh visit activity, enrich the related account and lead context, and route those signals to downstream systems (CRM, Slack/Teams, email, data warehouse) with consistent deduplication and alerting.

New to Leadfeeder?

Create an account to start identifying companies and capturing website visits.

New to Konnectify?

Build workflows that connect Leadfeeder to the rest of your stack in minutes.

Create a Konnectify account

What you can automate

• Monitor new website page visits in near real-time

• Detect new lead visits and trigger immediate follow-up

• Pull full visit session details for analytics and scoring

• Fetch a specific lead by Account ID + Lead ID for enrichment

• Fetch account details to route/account-match in your CRM

• Send alerts when high-value accounts return to your site

API & Authentication

Authentication method: API Key (credentials)

Konnectify connects to Leadfeeder using an API Key. You’ll paste the key into the Leadfeeder connection form in Konnectify. Keep this key private—anyone with access can read visit, lead, and account data permitted by your Leadfeeder workspace.

API capabilities in this connector:

Read newly detected page visits and visit sessions (polling-based triggers)
Read newly detected lead visits (polling-based trigger)
Fetch lead details by Account ID and Lead ID
Fetch account details by Account ID

Note on rate limits & plan restrictions

Leadfeeder API availability and rate limits can vary by plan and workspace settings. If you notice missed events or slower updates, reduce polling frequency, narrow the workflow scope, or confirm your Leadfeeder plan supports the required API endpoints.

Official documentation: Leadfeeder API Docs (If your workspace uses a different API portal, use the docs link shown in your Leadfeeder settings.)

How to connect Leadfeeder to Konnectify

Prerequisites

A Leadfeeder account with access to the workspace you want to automate
A Leadfeeder API Key (from your Leadfeeder settings)
A Konnectify account and permission to create/edit workflows

Add Leadfeeder to a Workflow

In Konnectify, create a new Workflow (or open an existing one).
Click Add step and choose Leadfeeder.
Select a Trigger (for inbound events) or an Action (for data fetch/enrichment).

Authorize via API Key

When prompted, click Add new connection.
Paste your Leadfeeder API Key into the API Key field.
Save the connection. Konnectify will validate it and use it for subsequent runs.

Configure the Trigger or Action

For Triggers, set the polling window and any available filters (if shown).
For Actions, map the required IDs (for example, Account ID and Lead ID).
Optionally add downstream steps (CRM update, Slack message, email, data storage).

Warning

If your workflow relies on polling triggers, avoid very small polling intervals unless necessary—aggressive polling can hit API rate limits and may cause temporary throttling.

Test the Workflow

Run a test to confirm Konnectify can fetch recent visits/leads from Leadfeeder.
Verify ID mappings and data fields (company/account identifiers, pages, timestamps).
Confirm any notifications or downstream updates look correct.

Activate the Workflow

Turn on the workflow.
Monitor the first few executions to confirm new visits are being captured as expected.
Adjust polling window or filtering if you see too much or too little data.

Triggers 3

This integration includes 3 polling triggers. Konnectify periodically checks Leadfeeder for new activity within your configured polling window and emits events when new records are detected.

Visits 3 triggers

New Page Visit

Polls Leadfeeder for new page visits within the polling window.

New Lead Visit

Polls Leadfeeder for new lead visits within the polling window.

New Visit

Polls Leadfeeder for newly detected visits and returns full visit session data.

Actions 2

Use actions to fetch Leadfeeder data on-demand (for enrichment, routing, and scoring) using IDs captured from triggers or stored in your systems.

Leads & Accounts 2 actions

Get Lead

Fetches a lead using Account ID and Lead ID from Leadfeeder.

Get Account

Fetches detailed account information using Account ID.

Popular automations

Examples of common workflows you can build with Leadfeeder + Konnectify using the triggers and actions available in this connector.

Enrich a lead the moment they return

When a new lead visit is detected, fetch the latest lead profile so downstream steps can score and route the lead accurately.

New Lead Visit → Get Lead

Enrich visiting companies for routing

When a new visit session appears, fetch the account details to map the visitor to the right owner, territory, or segment.

New Visit → Get Account

Build a “hot pages” follow-up flow

When a page visit occurs, pull the account context and pass it to your next steps (e.g., notify sales when pricing or demo pages are viewed).

New Page Visit → Get Account

Enrich both lead and account for scoring

When a lead visit is detected, fetch the lead record and also fetch the associated account record for a more reliable score and routing decision.

New Lead Visit → Get Lead → Get Account

FAQ

How does authentication work for the Leadfeeder connector?

Konnectify uses API Key authentication. Create or copy your Leadfeeder API Key from Leadfeeder settings, then paste it into the Konnectify connection field labeled API Key.

Which Leadfeeder plans are supported?

Any plan that provides API access to the endpoints used by your selected triggers/actions should work. If your connection validates but triggers return no data, confirm your workspace and plan include the necessary API features in Leadfeeder.

Are Leadfeeder triggers real-time?

These are polling triggers. Konnectify checks Leadfeeder at a set interval and pulls new page visits, lead visits, or visit sessions within your polling window. Shorter polling intervals can reduce detection lag but may increase API usage.

How do I prevent duplicate events from polling triggers?

Konnectify uses cursor-based polling for these triggers, which helps resume from the last seen record. For added safety, you can also implement an idempotency check in your workflow (for example, store processed visit IDs in a table or use your destination system’s native dedupe logic).

What happens if Leadfeeder rate-limits the API?

If Leadfeeder returns a throttling response, workflow runs may slow down or retry depending on your Konnectify execution settings. To reduce the chance of throttling, increase the polling interval, narrow filters (if available), or limit parallel workflows using the same connection.

Can I connect multiple Leadfeeder accounts or workspaces?

Yes. Create separate Konnectify connections using different API keys (or keys tied to different workspaces). Then select the correct connection per workflow step.

What IDs do “Get Lead” and “Get Account” require, and where do I get them?

Get Lead requires both an Account ID and a Lead ID. Get Account requires an Account ID. Typically, these IDs are available in the payload emitted by Leadfeeder triggers (visit/session objects) or can be stored in your CRM once you’ve matched the visitor to an account/lead.

Ready to automate your Leadfeeder workflows?

Connect Leadfeeder to Konnectify to turn website intent signals into reliable, scalable automations.

Get started free →