Webhook Ingestion
This page describes the Cinchy Webhook ingestion, including a video walkthrough and step-by-step guide
Compatibility: Webhook ingestion was introduced in Cinchy platform v4.21. Note that previous Cinchy versions will not include a Webhooks system table, and will not support this feature.
Context: A webhook uses a trigger event to initiate a data transfer that can then be ingested by another application. Many applications support webhooks to provide data updates in real time with minimal configuration required. Cinchy users can subscribe to and ingest webhooks via configuring a unique API endpoint. When the external application addresses this endpoint, a pre-identified saved query can be run, under an authorized user account, to ingest the data and insert or update it into Cinchy.
The following video walks you through a specific configuration, with a general step-by-step guide below:

Walkthrough Video

Step-by-Step Instructions for Configuring a Webhook

  1. 1.
    Identify the table in Cinchy that you want the information to be pushed to. (Image 1)
Image 1: Identifying your Table (Step 1)
Tip: Click here for instructions on creating a table within Cinchy.
2. Create your query in Cinchy. This query should take data from the webhook event, and push it into the Cinchy table that you identified in Step 1. (Image 2)
  • Your query will be running under a specific user account that you will assign in the next step. Ensure that whichever user you choose for this purpose has the correct permissions to execute the query, and to insert / update data in the target table.
Image 2: Creating your Query (Step 2)
Tip: Click here for instructions on creating a query within Cinchy.
Note: You will need administrator access to your Cinchy platform to perform Step 3.
3. Navigate to the webhooks table in Cinchy, and populate the following columns (Image 3):
  1. 1.
    Key: This can be any string (we recommend that you treat this like a password and make it random and unguessable).
  2. 2.
    Run As: Insert the user who will be running this query here. This should be the same user to whom you gave permissions in Step 2a.
  3. 3.
    Saved Query: Select the saved query that you created in Step 2.
  4. 4.
    Forward Payload as Parameter: This column will depend on the manner in which you would like to ingest the webhook payload.
    • If you are configuring individual parameters in the webhook payload (for example: @name, @url, etc.), you may leave this column blank.
    • If you are not configuring individual parameters, as an alternative you can ingest the entire payload under one parameter and specify it in this field. In the below image, we have defined it as “JSON”. This means that the full payload (which happens to be a JSON file in this case) will be parameterized as @JSON and then inserted into a table column named JSON.
Image 3: Configuring your Table (Step 3)
4. In your source application, navigate to the webhook settings and configure the following:
  • URL: This will be your Base URL + /API/callback?key= + the key value that you assigned in Step 3a.
    Example: {baseURL}/API/callback?key=rGh5tfgHK8989J5
Last modified 28d ago