Webhooks now send job title, location and 19 other details
If you send Botdog webhooks into a spreadsheet, CRM, Zapier, Make, or another tool, each contact event now includes much more useful information.
Previously, webhook events included basics such as name, company, email addresses, phone numbers, and LinkedIn URL. Important details like job title, location, and your own imported columns were missing.
What is new
Every contact event can now also include:
- Job title and location
- LinkedIn headline, profile photo, and profile link
- Connection degree, such as 1st, 2nd, or 3rd
- Invitation and connection dates when the invitation was sent through Botdog
- Enriched email and phone details, when enrichment is used
- LinkedIn profile signals, including follower count, Premium status, creator mode, open to work status, and profile websites
- Your own imported columns, using the same column names from your uploaded file
- The source list and list name the contact came from
Your imported columns now come back in the webhook
This is especially useful when connecting Botdog to your own CRM or spreadsheet.
For example, if your uploaded file included columns such as:
- Record number
- Industry
- Account owner
those values can now be sent back with the webhook under the same column names.
This gives you a simple way to match each Botdog event to the correct record in your own system without relying on names or LinkedIn URLs.
Enriched details stay separate
Email addresses and phone numbers found through enrichment are sent in their own fields.
They stay separate from the contact details taken from LinkedIn, so you can clearly see where each piece of information came from.
Existing integrations keep working
Nothing has been removed or renamed.
Every webhook field you already receive keeps the same name and meaning. The new information is simply added alongside it.
If you use Zapier or Make, you may need to pull in a fresh sample before the new fields appear in your list of available fields.
Test webhooks now match real events
We also fixed an issue where the Test button sent one field with a slightly different name from real webhook events.
This could cause a field mapped from a test event to arrive empty once real events started coming in.
Test events now use exactly the same field names as real deliveries.
If you created your integration from a test webhook before this update, it is worth comparing the mapping with a real delivery in your webhook history.
When some fields may be empty
Most of the new profile information comes from LinkedIn when Botdog visits, invites, or messages the contact during a campaign.
This means the details are usually available by the time someone accepts your invitation.
If someone connected with you outside a campaign and Botdog has never opened their profile through a campaign step, some profile fields may still be empty.
Job title, location, and details from your own uploaded file can fall back to the information you originally imported, so those are more likely to remain available.
Good to know
This update does not apply to the Message received (outside campaigns) webhook event.
That event covers people who are not contacts in your campaigns, so Botdog does not have the same imported contact record or campaign profile information to include.
