Can multiple RB2B accounts push to the same Webhook?
Can multiple RB2B accounts push to the same Webhook?
Yes, multiple RB2B accounts can be connected to and push notifications to the same Webhook.
How many Webhooks can I connect my RB2B account to?
How many Webhooks can I connect my RB2B account to?
RB2B is designed to permit a single integration connection per account. For users integrating with Webhook, this means you can push data to only one selected Webhook of your choice.
This setup ensures a streamlined and efficient data flow between RB2B and Webhook, making it easier to manage and analyze your data within a singular, cohesive environment.
Why did my Webhook integration shut off?
Why did my Webhook integration shut off?
If your Webhook integration has shut off unexpectedly, it may be due to recurring errors such as schema mismatches or connectivity issues. These errors prompt RB2B to disable the webhook automatically to prevent further unsuccessful requests.
Common Causes of Webhook Errors
Schema Mismatches A common issue is a mismatch between the payload sent by RB2B and the schema expected by the receiving endpoint. Errors such as "Invalid type. Expected String but got Null." often occur when fields are not aligned. To address this:
Update the receiving endpoint's schema to accept nulls for optional fields.
Ensure every required field is correctly populated. Use empty strings (
"") instead of null for mandatory string fields.
Connectivity Issues Timeouts or connection failures are another frequent source of problems. For instance, a timeout after a specific period (e.g., 15 seconds) may repeatedly cause Webhook failures.
Automatic Webhook Disabling
When the system detects repeated failures, RB2B disables the Webhook and notifies the user via the registered email. This mechanism ensures smoother operation and prevents disruptions.
Troubleshooting Steps to Reactivate Webhooks
Follow these steps to prevent and resolve recurring errors:
Review Logs and Error Messages: Check RB2B's logs to identify specific errors like schema mismatches or timeouts.
Validate Payload and Schema Compatibility: Confirm that the outgoing payload aligns with the receiving application's schema.
Set Timeout Thresholds: Adjust timeout settings in the receiving application to reduce disconnections.
Monitor Webhook Activity: Regularly review webhook performance logs to promptly address errors and avoid disruptions.
Re-enable Disabled Webhooks: After resolving issues, manually re-enable the webhook in RB2B settings. By following these steps, you can minimize errors and maintain stable webhook integration. If issues persist, contact RB2B support for further assistance.