# Destinations overview
Source: https://www.stedi.com/docs/edi-platform/configure/destinations

***

title: Destinations overview
sidebarTitle: Overview
----------------------

<Warning>
  {" "}

  Destinations is a legacy feature. It is not deprecated, but it has been
  superseded by [Webhooks](/edi-platform/configure/webhooks). Please [contact
  support](https://www.stedi.com/contact) with questions.
</Warning>

Each time you receive an EDI file from a trading partner, you will want to send the included transactions to your downstream system for processing. You can do this by configuring a Destination webhook. Destination webhooks allow you to send data from Stedi to third-party services without writing any custom code.

The most common use case is sending processed transaction data to your internal systems and business applications. You can also configure webhooks for other [Stedi events](/edi-platform/operate/event-types), like when a processing error occurs. This can be used to trigger alerts in systems like Slack, PagerDuty, or Zendesk for further review.

Stedi can send webhooks to:

* Custom applications using Basic, OAuth, or API Key authorization
* Cloud functions, including AWS Lambda, Google Cloud Functions, and Azure Functions
* iPaaS platforms, such as Zapier, Workato, or Tray.io
* ERPs like NetSuite, SAP, or Oracle.