Each incoming webhook received by FlexDeploy will be saved as a webhook message. This provides a way to track everything that's coming in and debug as needed. Messages can be viewed by navigating to Administration → Integrations → Webhooks and clicking .
Viewing Messages
The table on the left side of the screen shows all webhooks received within the last week. Messages are purged automatically after 7 days.
Field | Description |
---|---|
Message Id | The id given to message |
Provider Name | The provider the message was matched to |
Status | The status of the message. Can be SUCCESS, PENDING, or FAILED |
Uri | The uri where the webhook was received |
Message | A message containing more detail on the execution. This message can be set in a function script by using the LOG.setMessage function. If any errors occur during execution, the message will be overwritten |
Created By | User who created the webhook |
Created On | Date and time of webhook message creation |
Viewing Message Details
Click on any webhook message row in the table to view more details about an individual message. This will show more detail about the execution, including any webhook functions which were executed from this trigger and their statuses, as well as more context about the incoming webhook, including query parameters, headers, and additional properties. More information on the execution can be viewed by clicking . This will show any log messages printed in function scripts using the LOG methods. Click to view the entire JSON POST payload as received from the provider. You can also submit an incoming webhook message to be executed again with the button. Keep in mind this is only meant to be used for debugging purposes.
Log Messages
Some logs are printed automatically during execution, but most are printed by using the LOG methods in the provider match and function scripts. By default, the logging level will be based on the global FlexDeploy logging level. This can be modified specifically for webhook logs by setting the logging level for flexagon.fd.services.webhooks.functions.LogFunctions in Admin → Admin Operations.