Overview

This node operation updates the webhook settings of a specified form in the BCL Payment API. It allows enabling or disabling webhook notifications, setting the webhook URL, and selecting which events trigger the webhook (such as form submission, payment success, or direct debit). This is useful for automating notifications or integrations based on form activity.

Use Case Examples

1. Enable webhook notifications for a form to receive real-time updates on form submissions.
2. Set a webhook URL to trigger external workflows when a payment is successful on a form.
3. Configure webhook events to listen only for direct debit events on a specific form.

Properties

Output

JSON

• enabled - Indicates if webhook notifications are enabled for the form.
• url - The webhook URL set for the form.
• events - List of events configured to trigger webhook notifications.

Dependencies

• BCL Payment API with an API token credential

Troubleshooting

• Authentication failed errors indicate invalid or expired API token; verify and update credentials.
• Validation errors suggest missing or incorrect parameters; ensure all required fields are correctly filled.
• Bad request errors mean the request format or parameters are invalid; check the webhook URL and event selections.
• Forbidden errors indicate insufficient permissions; verify API token permissions.
• Not found errors mean the specified form ID does not exist; confirm the form ID is correct.
• Server errors indicate issues on the BCL API side; retry later or contact support.