We’re currently doing some private testing on our Incoming Webhooks integration. Want to be a part of it? Get in touch with us.
Webhooks are a simple, flexible way to keep everyone in the loop. With Stitch’s Incoming Webhooks integration, you have the ability to quickly and easily integrate with dozens of services that use webhook APIs.
To use Stitch Incoming Webhooks, you’ll need to:
stitch_webhooksin the data warehouse.
Next, you’ll define the Primary Key for the data that your Incoming Webhook integration will send to your data warehouse. A Primary Key is a field that’s used to uniquely identify each message in the webhook data. Primary Keys must:
In the Primary Key field, enter the name of the field you want to use as a Primary Key. Note that this field isn’t required, but if left blank Stitch will auto-generate a Primary Key instead.
Replication & Primary Keys
Defining a Primary Key for Incoming Webhooks is optional, but before you skip this step, note that the Incremental Replication Method Stitch uses will depend on whether one is provided:
_sdc_primary_keywill be automatically generated. This is because Stitch requires Primary Keys to replicate data and prevent duplication.
Additionally, we don't recommend changing a Primary Key once the integration has been set up and data has replicated. This could result in fields not being updated properly.
Click Save Integration to continue.
Once Stitch has successfully saved and created the webhook integration, you’ll be redirected to a page that displays your incoming webhook URL and token (which is blurred in the image below):
Click the Copy button to copy it.
Note that this particular URL won’t display in Stitch again once you click Continue. Think of this URL like you would your login or API credentials - keep it secret, keep it safe. You can, however, generate another URL should you need it.
Once you’ve copied your webhook URL, click Continue to wrap things up.
Depending on the provider you’re using, the steps for implementing webhooks may differ. We recommend checking out your provider’s documentation for instructions and reaching out to their support team if necessary.
In v1 of the Stitch Incoming Webhooks integration, Stitch will create a single table - called
data - in the webhook integration schema (this will be the name you enter in the Integration Schema field when you set up the integration) of your data warehouse.
The schema of an Incoming Webhooks table will contain two “types” of columns: columns used by Stitch (prepended with
_sdc) and the columns sent by the provider’s webhook API.
Aside from the Stitch columns, the schema of this table will depend entirely on the provider of the webhook API. For example: if the webhook API you integrate with only contains
value fields, these are the only fields that will be created in the
With the exception of the
_sdc fields and a Primary Key if one isn’t provided, Stitch does not augment Incoming Webhooks data nor does it have any control over the fields sent by the webhook provider.