Overview
This node acts as a trigger for workflows based on events occurring in Businessmap boards. It listens to specified webhook events related to cards, comments, subtasks, and board changes on a selected Businessmap board. When one of the chosen events happens, the node activates the workflow, passing along event data.
Common scenarios include automating task management processes, such as notifying teams when cards are created or moved, tracking comment updates, or responding to board structure changes. For example, you could use this node to start a workflow that sends an alert whenever a new card is added to a project board or when a comment is deleted.
Properties
| Name | Meaning |
|---|---|
| Board Name or ID | Select the Businessmap board to attach the webhook to. Choose from a list or specify an ID via expression. |
| Authenticate Incoming Webhook | Enable or disable authentication for incoming webhook requests to ensure they originate from Businessmap. |
| Events | Select one or more specific events to listen for. Options include all card, comment, subtask, and board-related events such as "Card Created", "Comment Updated", "Board Renamed", etc. |
Output
The node outputs JSON data representing the event payload received from Businessmap when a subscribed event occurs. The output contains detailed information about the event, including its type (e.g., card created, comment updated) and associated data.
If the event does not match any of the selected event types, the node outputs an empty array, effectively producing no workflow data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to connect securely to Businessmap.
- Needs proper configuration of the webhook URL within n8n to receive incoming HTTP POST requests from Businessmap.
- Uses Businessmap's REST API endpoints to manage webhooks (create, check existence, delete).
- The node depends on Businessmap's webhook infrastructure to push event notifications.
Troubleshooting
- Webhook Authentication Failure: If the "Authenticate Incoming Webhook" option is enabled, incoming requests must include the correct secret header (
x-kanbanize-secret). If missing or incorrect, the node responds with HTTP 403 Forbidden. Ensure the secret stored during webhook creation matches the header sent by Businessmap. - Webhook Not Triggering: Verify that the webhook URL configured in Businessmap matches the URL generated by n8n. Also, confirm that the selected board ID is correct and that the desired events are properly selected.
- API Request Errors: Errors during webhook creation or deletion may occur due to invalid credentials or network issues. These errors are surfaced with descriptive messages. Check API credentials and connectivity.
- Event Filtering: If no events are selected or if the event received is not among the selected ones, the node will output no data. Make sure to select relevant events to capture.
Links and References
- Businessmap API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- n8n Webhook Node Guide