With Stitch, you can consolidate data from a variety of webhook apps into destinations.

Historical webhook data

Webhook data is sent in real-time, which means that only records created after you set up the integration in Stitch will be replicated to your destination.

While most webhook integrations don’t retain historical data due to this as-it-happens approach, some apps may allow you to replay data and send it to Stitch. This is dependent on if the app has this feature, however.

If you want to replay historical webhook data and send it to Stitch, contact that app’s support for assistance.

Append-Only loading and querying

The majority of Stitch’s webhook integrations load data in an Append-Only fashion. When data is loaded using the Append-Only behavior, records are appended to the end of the table as new rows. Existing rows in the table aren’t updated even if the source has defined Primary Keys. Multiple versions of a row can exist in a table, creating a log of how a record has changed over time. Refer to the Understanding loading behavior guide for more info and examples.

While data stored using this method can provide insights and historical details about how rows change over time, grabbing the latest data does require a different querying strategy than usual. Refer to the Querying Append-Only Tables guide for more details.

All webhook integrations

If you don’t see what you’re looking for in the list below, check out the Singer project. A simple, composable, open-source ETL standard, Singer allows you to extract data from any source. Check out the GitHub repo to see what’s currently being worked on.

Additionally, Stitch’s Import API or Incoming Webhooks integrations can be used to extract data from sources that don’t currently have a native integration.