# Trigger Destination webhooks based on connection and data mode

> You can now configure event bindings to trigger a Destination webhook based on connection and data mode (Test or Production).

Published Jan 3, 2024

Product: EDI platform

You can now configure `transaction.processed.v2` event bindings to trigger a Destination webhook based on the following new filters:

- **Connection**: Inbound files from a specific connection. This option is useful when there are multiple connections within the same partnership. For example, you may set up a separate SFTP connection for test files and route them to a test endpoint.

- **Mode**: The transaction contains a specific value in the [ISA-15 element](https://www.stedi.com/edi/x12/segment/ISA#ISA-15), which is used in X12 to distinguish between test and production files. This option is useful when you want to send test and production data to separate endpoints.

Destination webhooks allow you to automatically send data and events from Stedi to any external API. You can configure one or more event bindings that conditionally trigger each webhook. The new **Connection** and **Mode** filters are available under the **Advanced** menu.