Via API steps and webhooks No app to install: Kerux talks to Freshsales's API with HTTP steps and webhooks, set up once.

LinkedIn replies as Freshsales contacts

When a lead replies on LinkedIn, an API step creates the contact in Freshsales with its owner. When they book, the deal moves to the next stage.

Start free trial Read the setup guide

How it works

Daniel replies
He asks for a call.
Freshsales has the contact
With an owner and a lifecycle stage.
Daniel Kim
1. Meeting booked
2. Deal stage: Demo
3. Follow-up 2
Booked, so the deal moves
And LinkedIn stops.

An example workflow

LinkedIn invitation and messages.
Reply: the When the lead replies box sends them to a short follow-up campaign, where a Webhook / HTTP step creates the Freshsales contact with name, email, LinkedIn URL and owner.
The contact id comes back for the next steps.
Meeting booked: a campaign started by the Meeting booked Kerux event updates the deal stage.
The follow-ups stop because a meeting was booked.

What data flows

Kerux sends to Freshsales

email
lead.first_name
lead.last_name
lead.company
lead.title
lead.linkedin_url

Freshsales sends to Kerux

contact.id

Set it up

In Freshsales, open your profile's API settings and copy the API key. In Kerux, choose API key as the sign-in, header name Authorization, and paste Token token= followed by the key.
In Kerux, open Integrations > Connections and click Connect on Custom API (under Developers). Pick how Freshsales signs in, paste the key and Freshsales's Base URL, click Save, then Test connection.
Add a Webhook / HTTP step that POSTs to https://<your-domain>.myfreshworks.com/crm/sales/api/contacts with the lead's fields.
For the meeting, add a step that updates the deal's stage with its id.
In the campaign's Builder, click Test to open Test on one lead: the lead's journey shows what Kerux sent to Freshsales and what came back.

Questions

Does Kerux have a native Freshsales integration?

Not a one-click app. Kerux works with Freshsales today through Freshsales's own API: you save your Freshsales key once in Kerux, then HTTP steps and webhooks do the work inside your campaigns. Nothing to install and no Zapier needed.

Why Token token= before the key?

That's the format Freshsales' API reads: no Bearer and no basic auth. Kerux stores the whole value encrypted and sends it on each call.

What happens if Freshsales is down or refuses a call?

The lead stops with Freshsales's own error message and shows in Need attention with a Retry button. It never shows as finished because a call failed, and nothing else goes out to that lead until you decide.

Use it in a campaign

Try Kerux free for 10 days. No card needed.