Solutions · RevOps
Create links from your workflows, stream view events to your warehouse, and meter usage predictably — over a REST API, signed webhooks, and an MCP server.
How it works
Your workflow calls the API — or your AI agent uses the MCP server — and gets a tracked link back.
Every API-created link passes the same PII scan and sanitization as the web app. No side doors.
link.created, link.viewed, link.expired, link.updated, usage.threshold — HMAC-signed to your endpoint, with retries.
Account-wide analytics endpoints roll per-link data up for your dashboards and your warehouse.
Use cases
A deal hits "Proposal sent" and your automation creates the tracked link, attaches it to the record, and notifies the rep — no human in the loop.
Webhook deliveries are HMAC-SHA256 signed, logged, and retried with backoff. Treat engagement data like any other pipeline source.
Reps create tracked links from Claude or ChatGPT without leaving the conversation — the MCP server and GPT action are ready to install.
Tracked-view metering is a soft cap: serving never stops, overage settles against prepaid blocks, and alerts fire at the threshold you set.
Personal keys for reps, org-scoped keys for systems. Each is prefix-identified, individually revocable, and shows last use.
Per-recipient URLs mean view events join cleanly to contacts in your CRM — engagement by person, not by anonymous fingerprint alone.
REST, webhooks, and MCP — documented and ready.