Send Webhook

A webhook is a notification sent not to a human, but to a computer (a server).

These notifications contain data – for example, a form submission – much like an email you may receive notifying you that a form has been submitted.

Software developers on your end can write code to receive webhooks – and do things with these digital notifications on your end.

Paminga can send webhooks notifying your systems of various events that occur throughout the platform.

Send Webhooks Conditionally

You may choose to send webhooks conditionally by using Conditional Actions.

Conditional Actions are only triggered when conditions of your choosing are met.

Configuring Your Webhook

Simply enable your Send Webhook Action by checking the box.

Enter a valid URL to which you'd like the webhook to be sent. URLs must begin with https://.

Send Webhook Action

Validating Encryption/Security

Paminga verifies that the SSL certificate of your "destination URL" is valid. If it is not, Paminga will consider the webhook call failed.

Webhook Payload

Webhook payloads are sent via POST in JSON format.

The content of the webhook payload varies based on its source.

Verifying Received Webhooks

Paminga can add a header called Signature that you can be used to ensure the payload has not been tampered with.

Please contact support if you require verified webhooks, so that a "shared secret" may be implemented.

Automatic Retry

When the destination URL to which the webhook is sent fails to respond with a 2xx HTTP status code, Paminga will consider the call as failed. The call will also be considered failed if a response is not received within 3 seconds.

When a webhook call fails, we'll retry the call two more times using an exponential backoff strategy.