Switch guide
Trigify turned engagement with social posts into leads. WhoLayer doesn't do that: we don't scrape LinkedIn or any social network. What we offer instead is a first-party version of the same signal: when people click from your posts to your site, WhoLayer can identify them.
Checked November 4, 2026.
Shut down
The Trigify team joined HubSpot (announced September 23, 2026). For most customers, platform access, integrations, and API access ended at 11:59pm BST on October 22, 2026. Accounts are not migrated to HubSpot. [1], November 4, 2026
Every WhoLayer endpoint and MCP tool below exists today. Where there's no equivalent, we say so.
| What you used Trigify for | WhoLayer | REST endpoint | MCP tool | Status |
|---|---|---|---|---|
| People who engaged with your posts | People who clicked from your posts to your site, identified by the tag (use UTM-tagged links) | GET /v1/visitors?level=person | — | Available (US only) |
| Companies engaging with your content | Company-level visitor ID, free and unlimited | GET /v1/visitors?level=company | — | Available |
| Push leads to Slack, CRM, or sequences | Slack or Microsoft Teams, one-way CRM sync (HubSpot, Pipedrive, Attio, Salesforce), and signed webhooks (for Clay, Zapier, Make, n8n, or your sequencer) | — | — | Available |
| Enrich leads with contact details | Enrich a person; verify emails | POST /v1/people/enrich | enrich_person1 credit per work email, 2 per personal email, and 5 per mobile returned, plus 10 for a reverse lookup when you send only an email and we find the person. Nothing if no match. | Available (US only) |
| Social engagement scraping (LinkedIn, X, Reddit, YouTube) | No equivalent, by design | — | — | Not offered |
| Keyword and competitor monitoring | No equivalent | — | — | Not offered |
REST base URL: https://api.wholayer.com/v1. MCP server: https://mcp.wholayer.com/mcp. Full reference in the API docs and OpenAPI spec.
WhoLayer isn't a complete replacement. Plainly:
Step 1
Sign up with your work email. The Free plan needs no card.
Step 2
Under Settings, API keys. Use a wl_test_... key first: every endpoint and MCP tool returns sandbox data and never spends credits.
Step 3
Paste one async script in your site header or install through Google Tag Manager.
Step 4
Add UTM parameters to links in your posts so you can see which visits came from social, and route by the landing pages they hit.
Step 5
Send identified visitors to Slack, HubSpot, or a signed webhook into your sequencer.
Because it depends on scraping, which we don't do. WhoLayer identifies people who visit your own site.
You can verify or enrich exported emails through the API or MCP server, including in bulk. WhoLayer doesn't import lists as visitors.
Competitor information is from public sources as of November 4, 2026 and may have changed. Trademarks belong to their owners. WhoLayer wrote this page; if something here is wrong, tell us and we'll fix it.
Ready when you are
The Free plan includes 100 credits a month for visitor ID, the Data API, and the MCP server. No card needed.