Overview
This node acts as a webhook trigger for Glassix events, allowing workflows to respond to specific events from the Glassix platform. It listens on a user-defined HTTP path and filters incoming events based on user-selected event types. It is useful for automating processes triggered by changes or actions in Glassix, such as ticket updates, new messages, or user status changes.
Use Case Examples
- Automatically update a CRM when a new ticket is created in Glassix.
- Send notifications when a ticket's state changes.
- Log user status changes for analytics.
Properties
| Name | Meaning |
|---|---|
| Path | The HTTP path on which the webhook listens for incoming Glassix events. |
| Events | The specific Glassix events to listen for. Users can select multiple events or use a wildcard to listen to all events. |
| Simplify Output | Whether to simplify the output data structure for easier consumption in workflows. |
Output
JSON
json- The JSON payload of the Glassix event received via webhook. If 'Simplify Output' is enabled, this will be a simplified version of the event data.
Troubleshooting
- If the webhook receives an event not included in the selected 'Events' list, it responds with HTTP 405 and no workflow execution occurs. Ensure the event types selected match the incoming events.
- If the webhook path is incorrect or not reachable, the node will not trigger. Verify the path parameter matches the URL used to send events.
- If 'Simplify Output' is enabled but the output is not as expected, check the event data structure and the simplification logic to ensure compatibility.