Webhook trigger: Configuring Pendula with third party applications

Angel Cheung
Angel Cheung
  • Updated

Which configuration method should be used?

While many third party apps can trigger webhooks, how simple or complex this is will depend on the third party app itself. Below are different configuration methods, listed in ascending complexity:

Configuration within Third Party via Basic Auth

Use this if the third party allows specifying:

  • HTTP Callout URL – this is where the Pendula’s inbound webhook URL can be specified
  • Basic Authentication – username (tenant ID) and password (Pendula’s Inbound API token) to be attached on every request.

Configuration within Third Party via Custom Headers

Use this if the third party allows specifying:

  • HTTP Callout URL - This is where the Pendula’s Inbound webhook URL can be specified.
  • Custom Header to be attached on every request. This is another way of specifying Pendula’s Inbound API token.

Calling via a Simple HTTP Proxy Server

Use this if the third party:

  • Does not allow specifying an http callout url
  • Does not allow Kong
  • Allows a HTTP proxy application to be running in their tech stack

Calling via a Simple Intermediary Application

Use this if the third party does not allow specifying an HTTP callout URL and requires integrations to follow an app approach.

Configuration via Third Party Code

Use this if third party integrations are specifying using a code configuration approach.