Webhook activity log

The Webhook Activity Log can be viewed by companies with a Business subscription that have webhooks configured for any flow.

Users need permission to view other users' activity to access the Webhooks Activity Log. This is because sensitive information can be seen in the webhook payload, and all webhook data across the entire company is displayed on this page.

Permissions can be set by company admins on the team page.

 

The webhook activity log lets a user filter webhooks by process key, status, and the flow key. Read more about keys here.

On the Webhooks page, you can view

  • If the webhook has been delivered
  • the timestamp of the most recent delivery
  • the flow key
  • the recipient URL
  • the payload
  • the response
  • the event type
  • A link to the signing process in the activity log

You can resend the webhook as often as you need. Resending the webhook will attempt up to three times if it fails.

 

 

Get notified when a webhook fails


You don't have to watch the activity log to catch failures. When a webhook can't be delivered, Taktikal automatically sends an alert to your IT operations email.


Set this address in the Taktikal portal under Company settings, in the IT operations email field. As the field itself
 notes: "Notifications about failed data delivery via webhook and operational incidents will be delivered to this email."


 We recommend setting this to a monitored team inbox (for example <code>ops@yourcompany.com</code>) so failed deliveries are picked up quickly. From there, you can open the link in the email to inspect the failed delivery and resend it.

Articles in this section