How to Make Zap Webhook Trigger Requests Unique with Timestamp Values to Avoid Data Deduplication
Contribution by Troy Tessalone
Troy is a Certified Zapier Expert who puts Programmable Productivity to work for YOU!
If you want to send the same data to run a Zap that uses a Webhook Catch Hook trigger, then you need to make the data request unique by adding a timestamp value.
(more info below about system generated timestamps)
Deduplication is the process Zaps use to ensure your Zap only triggers for new information, avoiding duplicates.
Duplicate information is managed differently in Zap triggers and actions.
The deduplication system only checks within the same Zap.
Webhooks are notifications of events that happen in an app and include a payload of data about the event.
HTTP REST request methods supported to fire a Zap that uses a webhook trigger: GET, POST, PUT
The examples below use the POST method.
Zap Trigger: Webhook - Catch Hook
This will generate a unique webhook URL to configure in the origin/source app that is sending the event notification.
System Generated Timestamps: https://help.zapier.com/hc/en-us/articles/8496275717261
Add a timestamp in your timezone
Enter the following command in your action step:
When your Zap runs, it will insert the date and time in the following format:
NOTE: TS stands for timestamp.
Query String Parameter
How to add a dynamic timestamp variable as a query string parameter on a POST request.
Body Data Parameter
How to add a dynamic timestamp variable as a body data parameter on a POST request.
How the timestamp value comes thru on the Zap webhook trigger data payload.
- Top TS is for the Body Data Parameter approach.
- Bottom TS is for the Query String Parameter approach.