Webhook Setup Guide
Prerequisites
To connect Webhooks to Matia, you need an HTTP client setup on your website, application, or any other place.
Setup Guide
In the integration setup form:
- Enter the Destination schema name of your choice.
- Enter the Destination table name.
- Select the Sync format in which form you'd like your data to be loaded, Packed or Unpacked.
Packed vs Unpacked
Matia can deliver your data in either packed or unpacked format. For example:
{
"foo": 1,
"nested": {
"bar": 2
}
}
Unpacked
Matia unpacks one layer of nested fields and infer types. This produces a table that looks like:
| _ID INTEGER | FOO INTEGER | NESTED JSON |
|---|---|---|
| ? | 1 | {"bar":2} |
Packed
Matia loads all your data into a single column. This produces a table that looks like:
| _ID INTEGER | DATA JSON |
|---|---|
| ? | {"foo":1,"nested":{"bar":2}} |
In the connector setup form:
- Enter a Name for the connector.
- (Optional) Enter a Description for the connector.
- Select the Owner of the connector.
- (Optional) Verify that your Webhook is successfully connected by clicking on Test Connection.
- Click Connect.
Schema Information
For every webhook integration, we create a single table. To have multiple tables in a single schema, you can create multiple webhook connections.
Each table that we create has the following default columns:
| COLUMN | DESCRIPTION |
|---|---|
| _created | 🔑 The timestamp when the event is entered in our Matia system. |
| _id | 🔑 A randomly generated UUID that is assigned to each received event. |
| _index | 🔑 A sequential identifier to distinguish events within a batch, as all these events share the same _id value. For instance, the _index value is 0 for the first event, 1 for the second event, and so on. |
| _ip | IP address of the client that sent the event. |