Aircall Integration Explained
Setting up webhook triggers in Aircall allows you to send real-time data to your external systems based on specific events. This is essential for building custom integrations and automating workflows.
Wix Integration Explained
This guide outlines how to use the Wix Automations feature to send data from your site to an external system using a webhook. This allows you to trigger actions on other platforms based on events that happen on your Wix site, like a form submission or a new order.
Introduction
💡 OverviewThis guide outlines how to use the Wix Automations feature to send data from your site to an external system using a webhook. This allows you to trigger actions on other platforms based on events that happen on your Wix site, like a form submission or a new order.
⚙️ How to Create a Webhook Automation in Wix
Follow these steps to configure a new automation that sends data via a webhook.
- Navigate to the Automations section in your site's dashboard.
- Click the "+ New Automation" button in the top right corner.
- Select "Start from Scratch" or choose a relevant template.
- Click the default title to give your automation a descriptive name.
- Specify the Trigger event that will initiate the automation (e.g., "Wix Forms - Form Submitted").
- For the automation's Action, choose "Send via webhook".
- Enter the Target URL where the webhook notification should be sent.
- Decide how much data to send:
- All keys and values: Sends all available data from the trigger event.
- Customize structure: Allows you to select specific data points. Click "Insert Variable" to map values from the trigger to custom keys.
- (Optional) Click "View Structure" to preview the data that will be sent in the webhook payload.
- When you're done, click "Save".
- Select the desired Timing for when the automation should run.
- Finally, click "Activate" to finalize the setup.
⚠️ Important Considerations & Best Practices
Delayed or Out-of-Order Events
If your server fails to respond with a
200 status code within 1250 milliseconds, Wix will make additional delivery attempts. This can lead to subsequent events being received before earlier ones. Resent webhooks will always contain the original event data.Duplicate Events
To ensure reliability, Wix stores event copies on multiple servers. In rare cases where a server is inaccessible during delivery, you might receive the same event more than once. It is crucial to design your application to handle and de-duplicate events properly.
Retry Policy
If a webhook fails due to a timeout or a non-
200 response, the system will make up to 12 additional attempts on the following schedule:- 1st Retry: 1 minute after failure
- 2nd Retry: 10 minutes after previous failure
- 3rd Retry: 1 hour after previous failure
- 4th-5th Retries: 2 hours after previous failure
- 6th-9th Retries: 4 hours after previous failure
- 10th-11th Retries: 8 hours after previous failure
- 12th Retry: 12 hours after previous failure
✅ Best Practices
- Respond Quickly: Always respond with a
200status code immediately upon receiving a webhook to confirm successful receipt before performing any complex logic.
- Verify Data: Periodically make API requests to ensure your received webhook data accurately reflects the current state of your site.
- Handle Edge Cases: Ensure your server can properly handle out-of-order and duplicate webhook notifications.
- Stay Updated: If you see alerts about outdated webhook URLs in the Developer Center, update your configurations promptly to prevent service disruptions.
📚 References
Related Posts
Monday.com Integration Explained
This guide explains how to set up a webhook integration in Monday.com to send real-time data to your external systems based on events happening on your boards.
Zenoti Integration Explained
Zenoti is a cloud-based software platform for businesses in the wellness and beauty industries, such as spas, salons, and fitness centers.
Made with Bullet