Video walkthrough: Setting up webhooks in Digit
Watch this video to see how to activate webhooks, configure a destination endpoint via the Svix portal, and confirm that real-time event notifications are working.
Before you begin
Webhooks must be enabled by the Digit support team before you can access this feature.
β Add-on required: If you donβt already have access in your account, Contact your Customer Success Manager or reach out to our support team at [email protected] to request webhooks be enabled for your account before proceeding.
Step 1: Activate webhooks in Digit
Once webhooks have been enabled for your account, activate the feature in your settings.
Navigate to Settings in the left side panel.
Under the Setup section, open the Webhooks tab.
Toggle the switch to activate the feature.
Activating webhooks gives you access to the Svix portal, where you will configure the destinations that receive your event notifications.
π‘ Digit Tip: The Webhooks tab includes two links, one to open the Svix endpoints page and one to access Svix Play, a testing tool used to inspect and verify that events are being delivered correctly.
Step 2: Configure an endpoint in the Svix portal
An endpoint is the destination URL where Digit will send event notifications. You will need to generate this URL from your automation platform, such as Make, Zapier, or any platform that supports custom webhooks.
β
Get your endpoint URL from your automation platform
The following example uses Make.com to generate a webhook URL.
Open Make.com and click Create scenario.
Click the + button and select Webhooks.
Choose Custom webhook.
Select an existing webhook or create a new one. To create a new one,
Click Copy address to copy the generated webhook URL.
Add the endpoint in Svix
Return to the Svix portal and Paste your webhook URL directly into the Endpoint URL field.
Add an optional description to identify what this endpoint does.
Under Subscribe to events, locate the relevant event category. You can either select individual events (for example, sales_order.created) or select the entire category to track all events within it (for example, sales_order to capture created, deleted, and updated).
Click Create.
You will be taken to the endpoint details page, confirming the endpoint has been created.
β Best practice: Give each endpoint a clear description so your team can easily identify which automation it is connected to.
Step 3: Verify the integration
Test that events are being delivered to your endpoint by triggering an event in Digit for which you just created a webhook.
Navigate to the relevant module in Digit for this example, go to Sales orders.
Create a new order and click Create Order to trigger the endpoint.
Return to the endpoint details page in the Svix portal and confirm that a message has been successfully delivered.
Your webhooks integration is now live. Digit will automatically notify your connected automation platforms such as Make or Zapier whenever the events you configured occur in your system, enabling you to trigger workflows and keep your tools in sync in real time.
π Digit Tip: You can add multiple endpoints in the Svix portal to send event notifications to more than one automation platform at the same time.
Tips and tricks: Managing your webhook subscriptions
As you build out your automations, how you structure your webhook subscriptions can have a big impact on how simple or complex your workflows become. Here are two approaches to consider.
Subscribe to fewer events per webhook
When an endpoint is subscribed to many events, your automation platform receives all of them and has to determine what to do with each one, which means building more complex filtering logic into your workflow.
Instead, consider creating separate, focused webhooks, for example, one webhook for sales_order.created and sales_order.updated, and another for purchase order events. This way, each automation only receives the events it needs, keeping your workflow logic simple and easier to maintain.
β
Use the right platform for your workflow
Different automation platforms handle webhook payloads differently. Common platforms that support custom webhooks include Make, Zapier, n8n, and Pipedream. If you find that filtering or conditional logic is becoming complex, it may be worth exploring whether a different tool is a better fit for your use case.





















