Prerequisites
- A HeyReach account
- An API key that is allowed to create webhooks
Setup
1
Connect your account
Enter your HeyReach API key, found at HeyReach Settings → API → Copy API Key. RevyOps
verifies it before continuing.
2
Webhooks are created for you
Once the key checks out, RevyOps creates one webhook in HeyReach for each of the 12 events it
listens to, each named “RO” followed by its event and all pointing at your workspace. To see them, open
HeyReach Settings → Integrations → Webhooks. Connecting again skips any webhook that already
has the same event and URL.
3
Classify labels
HeyReach labels are managed manually. Use Edit Statuses to classify which labels count as
Interested and which are Blocked (Do Not Contact) statuses.
If setup can’t create the webhooks
When HeyReach refuses the request, the setup screen says why, for example that the API key isn’t allowed to create webhooks. Fix the cause and connect again, or create the webhooks by hand: copy the webhook URL from the HeyReach panel on the Integrations page, then in HeyReach Settings → Integrations → Webhooks add one webhook per row below. HeyReach takes one event per webhook, so pick the row’s name in the Event Type menu, paste the same URL each time, and keep every webhook active.
If your workspace has campaign keywords set under Campaign Mapping, events from a campaign whose name does not match are ignored.
Profile Viewed and Post Liked show on the person’s timeline and in filters, but no scoring rule scores them until you add one. LinkedIn campaign reports show them as Profiles Viewed and Posts Liked, and never count them as messages sent or prospects. RevyOps doesn’t use Follow Sent or Campaign Completed: Follow Sent never arrives and Campaign Completed names no lead. A workspace connected before 16 October 2026 may still have those two webhooks in HeyReach. They change nothing, and you can delete them.
Check it worked
The HeyReach panel on the Integrations page shows HeyReach as connected once setup finishes. After HeyReach sends its first event, the activity chart in the same panel starts counting it. HeyReach usually sends an event 20 to 80 minutes after it happens, so allow up to two hours before treating a quiet panel as a problem. A panel that stays connected with no activity after you have sent from HeyReach means the webhooks are not arriving. Check that all 12 webhooks exist and are active in HeyReach.Labels
HeyReach labels are not detected automatically. From Edit Statuses you:- Mark labels as Interested so leads with that label count as interested in your reports
- Mark labels as Blocked so leads with that label are treated as Do Not Contact
- Add a label manually if it isn’t already in the list
Meeting Booked and
Meeting Booked isn’t marked Interested, RevyOps saves the label but doesn’t count the lead
as interested in your reports, and nothing warns you.
Auto Tags
RevyOps also listens for HeyReach’s own auto-tagging events, so a lead HeyReach tags on its own can show up the same way a manually applied label does. A new auto tag that isn’t already classified shows up under Edit Statuses so you can mark it Interested or Blocked.LinkedIn Contacts and Identity
HeyReach leads are matched by LinkedIn profile. A LinkedIn-only lead from HeyReach and an existing email contact for the same person can appear as two separate contact records in RevyOps. The two records are not left disconnected, though. When a HeyReach event also carries a lead email, RevyOps links the LinkedIn-only contact and the email contact under the same person, so they show up together on one timeline.Do Not Contact Sync
Contacts marked Do Not Contact anywhere in RevyOps can be pushed to HeyReach automatically. When a contact is marked DNC, RevyOps also marks every other record it has for that same person, so every known address for that person is suppressed together.HeyReach’s Do Not Contact push only adds entries; it doesn’t support removing a contact from
HeyReach’s blocklist once pushed.