Sending enriched contacts to a webhook
Enriched contacts can be pushed to a webhook automatically as Signals run, or manually in bulk from the Contacts manager. Either way, each contact is sent as a rich JSON payload with 65+ fields covering personal, company, education, funding, and engagement data.
Written By Kevin Lawrie
Last updated About 24 hours ago
Two ways to send contacts
Automatic — via Signal configure: Every time a Signal enriches a contact (from a post author, reactor, or commenter), the enriched record is pushed to your webhook immediately. Set it up once and it runs on every Signal run.
Manual — from the Contacts manager: Select any contacts from your account and push them to a webhook on demand. Useful for one-time exports, backfills, or sending contacts from multiple Signals to a single destination.
Setting up automatic contact delivery (Signal configure)
In the Signal Configure step, each capture block — Capture Post Author, Capture Post Reactions, Capture Post Comments — has its own Send enriched contacts to webhook toggle.
Enable the capture block (e.g. Capture Post Reactions → Save Profile as Enriched Contact).
Toggle Send enriched contacts to webhook.
Select your webhook.
Use Send Test Payload (Contact) to verify.
Each contact is pushed as an individual HTTP call as soon as enrichment completes. The payload includes full contact data plus context about which post they came from and how they interacted with it (reaction or comment).
Manual contact export to webhook
Go to Contacts in the left sidebar.
Apply any filters to narrow your selection.
Select contacts using checkboxes, or use Select all (up to 1,000).
Click Export → Webhooks.
Choose your webhook from the dropdown.
Optionally enable Include Full Engagement History (see below).
Click Push Contacts.
Up to 150 contacts are sent per manual export. Contacts are delivered one per HTTP call with a 1-second delay between each to avoid overwhelming your endpoint.
Include Full Engagement History
This option is available on manual exports only. When enabled, each contact payload includes an additional engagement_history block containing:
Up to 50 recent reactions across all Signals
Up to 50 recent comments across all Signals
A summary: total reactions, total comments, number of Signals the contact appeared in, most active Signal, first activity date, latest activity date
This is particularly useful when sending contacts to a CRM or data warehouse where you want the full picture of their engagement — not just their enriched profile.
What's in a contact payload
Each contact payload is structured into clear sections:
Signal context Which Signal created this contact, Signal name, and monitoring type.
Personal First name, last name, email, email status (verified/risky/not found), headline, bio summary, LinkedIn URL, LinkedIn URN, profile picture, skills, mobile phone.
Location City, country, full location string.
Current position Job title, employment type, company name, job location.
Company Name, LinkedIn page, website, industry, company size, description, tagline, specialities, type, founding year, follower count, funding rounds, last funding type and year, company address.
Education School, degree, field of study (supports two education entries).
Engagement context The original post that generated this contact, the author of that post, and the specific interaction (reaction type and timestamp, or comment text and timestamp).
Contact payload origins
The origin field in each payload tells you how the contact was sent: