// Integration
CSV / webhook todayTrackyr + Make
Build multi-step Trackyr automations by catching the webhook batch in Make today, with a native Make app planned.
How it works
Connect Trackyr to Make today using the outbound webhook. Add a 'Custom webhook' trigger module in a Make scenario, copy its URL into Trackyr's webhook settings, and when you click Push, Trackyr sends a signed JSON batch of up to 500 contacts that runs the scenario. Add an Iterator module over the contacts[] array, then route each one to a CRM, sequencer, or any Make module. Requests are HMAC-signed for verification. A native Trackyr Make app is planned but not built yet, so the custom webhook is the current path.
// Step by step
Send contacts to Make.
- 1In Make, create a scenario starting with a 'Custom webhook' trigger module.
- 2Click 'Add' to generate the webhook URL and copy it.
- 3Paste the URL into Trackyr's Settings → Integrations webhook destination.
- 4Click Push in Trackyr so Make captures the data structure from a real batch.
- 5Add an Iterator over the contacts[] array, then downstream modules (CRM, sequencer, router).
- 6Map the fields and activate the scenario.
// Common questions
Answered.
Does Trackyr have a native Make integration?+
A native Make app is planned but not built yet. Today you connect with the 'Custom webhook' trigger module, which supports full multi-step scenarios.
The webhook sends a batch — how do I handle it in Make?+
The payload is a contacts[] array of up to 500. Add a Make Iterator module to split it into individual bundles, then process each contact downstream — and branch on verification status with a router.
How is the webhook secured?+
Trackyr signs each request with HMAC over `<timestamp>.<body>`. Validate the X-Trackyr-Signature in a Make function, or rely on the secret webhook URL for low-risk flows.
Verified contacts, in your stack.
Find and verify creator + B2B contacts, then export to CSV or push a webhook anywhere.
Start hunting →