Lead feed and Tern
Tern pulls leads on a schedule from any platform that serves the Tern Lead Feed standard: two read only HTTPS endpoints, a token and an optional signature. The feed name you choose becomes the lead source.
How Lead feed connects
Plain facts
- HTTPS only, a bearer token and an optional HMAC signature on every request
- Only changed leads are fetched and a lead that comes back unchanged costs nothing
- Every call is made from Tern's server, never from a browser
- Any platform can build it from the published guide and JSON schema
What Tern captures
The platform publishes GET /health and GET /leads as the published guide describes and gives you a base URL and a token. You add it in Tern under Integrations, Lead feeds, test the connection and name the feed. From then on Tern pulls only what changed, on the schedule you pick, and every lead arrives with the feed name as its source.
What Tern does with it
Tern reads and never writes back to the platform through a lead feed. Each record is validated, matched against existing contacts by phone, WhatsApp and email and given an outcome and a playbook. A record that fails validation is skipped and listed with the reason.
Ready to start?
Stop losing
follow ups.
$99 per month per workspace. Connect WhatsApp and your phone system today and your first priority call list is ready tomorrow morning.