The flow is straightforward:<\/p>\n\n\n\n Tolinku sends a POST request to Zapier's URL every time a matching event occurs. Zapier parses the JSON payload and makes the data available to downstream action steps.<\/p>\n\n\n\n Do not close this tab yet. Zapier needs to receive a test webhook before you can configure the action steps.<\/p>\n\n\n\n For a Zapier integration, you'll typically want to subscribe to specific events rather than all of them. Each Zap works best when it handles one event type, so you can tailor the automation to that event's data shape.<\/p>\n\n\n\n Use the Test<\/strong> button on your webhook in the Tolinku dashboard. This sends a test payload to Zapier so it can detect the data structure.<\/p>\n\n\n\n The test payload looks like:<\/p>\n\n\n\n After sending the test, go back to the Zapier tab and click "Test trigger." Zapier should find the test event and display the parsed fields: For a more realistic test, trigger an actual event by clicking one of your deep links. This gives Zapier a real This is where Zapier's power shows up. You can connect the webhook data to any of Zapier's 6,000+ app integrations. Here are the most common patterns for deep link events.<\/p>\n\n\n\n Good for: Marketing teams who want a simple event log without touching a database.<\/p>\n\n\n\n Every webhook event becomes a new row. This gives you a live event feed you can filter, chart, and share.<\/p>\n\n\n\n Good for: Startup teams who want to celebrate every new install in real time.<\/p>\n\n\n\n Filter the Zap to only trigger on Good for: Sales teams tracking referral-driven signups.<\/p>\n\n\n\n This automatically creates a CRM record when a referred user completes their signup or first purchase.<\/p>\n\n\n\n Good for: Product managers who want to know when specific campaigns drive conversions.<\/p>\n\n\n\n Good for: Re-engagement workflows based on deep link behavior.<\/p>\n\n\n\n Zapier handles nested JSON well. The Tolinku webhook payload has a top-level If Zapier doesn't automatically detect nested fields, use the "Catch Raw Hook" trigger instead of "Catch Hook." This gives you the raw JSON body, which you can parse with a Code step.<\/p>\n\n\n\n If you subscribed to multiple events on a single webhook, use Zapier's Filter<\/a> step to route events:<\/p>\n\n\n\n A cleaner alternative: create separate webhooks in Tolinku for each event type, each pointing to a different Zap. This way, each Zap only receives the events it cares about, and you don't need filter steps.<\/p>\n\n\n\n Signature verification.<\/strong> Zapier's "Catch Hook" trigger does not verify the Rate limits.<\/strong> Zapier's webhook trigger has rate limits that vary by plan. On the free plan, Zaps run every 15 minutes (they're polled, not instant). On paid plans, Zaps run within 1-2 minutes of receiving a webhook. For real-time use cases, you need at least a Zapier Starter plan.<\/p>\n\n\n\n Payload size.<\/strong> Zapier can handle the Tolinku webhook payload without issues. The payloads are small (typically under 1 KB).<\/p>\n\n\n\n Retry handling.<\/strong> Tolinku retries failed webhook deliveries (3 retries at 1 minute, 5 minutes, and 30 minutes). If Zapier's endpoint returns an error, the retry will send the same event again. Zapier does not deduplicate, so your downstream actions may fire multiple times. For idempotent actions (updating a record) this is fine. For non-idempotent actions (sending an email), consider adding a deduplication step<\/a> using a hash of the event data. See the webhook retry logic guide<\/a> for more on handling retries.<\/p>\n\n\n\n The real power of Zapier comes from chaining multiple actions. Here's an example of a multi-step Zap for referral tracking:<\/p>\n\n\n\n Each step uses data from the original webhook payload. Zapier passes the data through the entire chain.<\/p>\n\n\n\n Zapier is excellent for getting started quickly and for teams without engineering resources. Consider moving to a custom integration when:<\/p>\n\n\n\n For many teams, Zapier remains the right choice indefinitely. The tradeoff is cost and control versus speed and simplicity.<\/p>\n\n\n\n![\"Tolinku](\"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/platform-webhooks.png\")
\nThe webhooks page with create form, webhook list, and delivery log.<\/em><\/p>\n\n\n\nHow It Works<\/h2>\n\n\n\n
\n
Step 1: Create the Zapier Trigger<\/h2>\n\n\n\n
\n
https:\/\/hooks.zapier.com\/hooks\/catch\/123456\/abcdef\/<\/code><\/li>\n<\/ol>\n\n\n\nStep 2: Configure the Tolinku Webhook<\/h2>\n\n\n\n
\n
\n
link.clicked<\/code>: When someone taps a deep link<\/li>\ndeferred_link.claimed<\/code>: When a deferred link is resolved after install<\/li>\ninstall.tracked<\/code>: When an app install is attributed<\/li>\nreferral.created<\/code>: When a new referral is registered<\/li>\nreferral.completed<\/code>: When a referred user completes the required action<\/li>\n<\/ul>\n\n\n\nStep 3: Send a Test Event<\/h2>\n\n\n\n
{\n "event": "test",\n "timestamp": "2026-05-20T10:00:00.000Z",\n "data": {\n "message": "This is a test webhook from Tolinku.",\n "webhook_id": "wh_abc123",\n "appspace_id": "as_xyz789"\n }\n}\n<\/code><\/pre>\n\n\n\nevent<\/code>, timestamp<\/code>, and the nested data<\/code> object.<\/p>\n\n\n\nlink.clicked<\/code> payload with all the fields your automation will use.<\/p>\n\n\n\nStep 4: Build the Action<\/h2>\n\n\n\n
Pattern 1: Log Events to Google Sheets<\/h3>\n\n\n\n
\n
\n
event<\/code><\/li>\ntimestamp<\/code><\/li>\ndata.platform<\/code><\/li>\ndata.campaign<\/code><\/li>\ndata.token<\/code><\/li>\n<\/ul>\n\n\n\nPattern 2: Slack Notification on Install<\/h3>\n\n\n\n
\n
New install tracked!\nPlatform: {{data.platform}}\nDevice: {{data.device_type}}\nCampaign: {{data.campaign}}\nTime: {{timestamp}}\n<\/code><\/pre>\n\n\n\ninstall.tracked<\/code> events. You can do this with a Zapier Filter step: "Only continue if event<\/code> exactly matches install.tracked<\/code>."<\/p>\n\n\n\nPattern 3: CRM Update on Referral<\/h3>\n\n\n\n
\n
event<\/code> exactly matches referral.completed<\/code><\/li>\nPattern 4: Email Alert on High-Value Events<\/h3>\n\n\n\n
\n
event<\/code> exactly matches referral.completed<\/code><\/li>\nSubject: Referral Completed - {{data.token}}\n\nA referred user completed the required action.\n\nTimestamp: {{timestamp}}\nDetails: {{data}}\n<\/code><\/pre>\n\n\n\nPattern 5: Trigger a Marketing Automation<\/h3>\n\n\n\n
\n
deferred_link.claimed<\/code> (user installed the app after clicking a link)<\/li>\nWorking with Nested Data<\/h2>\n\n\n\n
event<\/code> and timestamp<\/code>, with event-specific fields nested inside data<\/code>. In Zapier's field mapper, you access nested fields with dot notation:<\/p>\n\n\n\n\n
data.platform<\/code> gives you the platform (ios, android, web)<\/li>\ndata.campaign<\/code> gives you the campaign identifier<\/li>\ndata.token<\/code> gives you the link token (the path segment of the deep link)<\/li>\n<\/ul>\n\n\n\nFiltering by Event Type<\/h2>\n\n\n\n
\n
event<\/code> exactly matches link.clicked<\/code>"<\/li>\ndata.platform<\/code> exactly matches ios<\/code>"<\/li>\ndata.campaign<\/code> contains facebook<\/code>"<\/li>\n<\/ul>\n\n\n\nLimitations to Know About<\/h2>\n\n\n\n
X-Webhook-Signature<\/code> header. This means anyone who discovers your Zapier webhook URL could send fake events. For low-risk automations (logging to a spreadsheet, Slack notifications), this is usually acceptable. For anything that triggers financial actions or modifies customer records, use a custom receiver that verifies signatures and then forwards to Zapier, or build the integration with code instead.<\/p>\n\n\n\nMulti-Step Zaps<\/h2>\n\n\n\n
\n
referral.completed<\/code> event<\/li>\nWhen to Graduate from Zapier<\/h2>\n\n\n\n
\n