Glassix Trigger icon

Glassix Trigger

Handle Glassix events via webhooks (v.0.1.0)

Overview

The Glassix Trigger node is designed to handle incoming webhook events from Glassix, a customer communication platform. It listens for specific event types (such as ticket changes, new messages, or user status updates) at a configurable path and triggers n8n workflows when those events occur. This node is useful for automating processes in response to real-time events from Glassix, such as updating CRM records when a ticket state changes, sending notifications on new messages, or logging signed documents.

Practical examples:

  • Automatically create tasks in your project management tool when a new ticket is created in Glassix.
  • Send alerts to Slack when a document is signed.
  • Update user status in an external system when it changes in Glassix.

Properties

Name Type Meaning
Path String The URL path where the webhook will listen for incoming Glassix events.
Events MultiOptions The list of Glassix event types to listen for (e.g., TICKET_STATE_CHANGE, NEW_TICKET).
Simplify Output Boolean Whether to simplify the output structure for easier downstream processing.

Output

  • The node outputs data received from the Glassix webhook as a JSON object.
  • If Simplify Output is enabled, the output is processed to provide a more concise and user-friendly structure.
  • The output always contains the event payload sent by Glassix. Example structure:
{
  "json": {
    // All fields provided by the Glassix webhook event,
    // possibly simplified if "Simplify Output" is true.
  }
}
  • If the event type received does not match any of the selected events (and "*" is not selected), the node responds with an error and does not trigger the workflow.

Dependencies

  • No external credentials are required for this node.
  • The node must be accessible from the internet so that Glassix can send webhook requests to the specified path.
  • Ensure the n8n instance is configured to allow webhooks and the chosen path is reachable.

Troubleshooting

  • Common Issues:

    • Webhook Not Triggering: Ensure the n8n instance is publicly accessible and the correct path is set both in n8n and in Glassix's webhook configuration.
    • Event Not Listened For: If you receive the error message The event "<event_name>" is not listened for!, make sure the event type is included in the "Events" property selection or use the wildcard "*".
    • Malformed Payloads: If the output is not as expected, try toggling the "Simplify Output" option.

  • Error Messages:

    • "The event \"<event_name>\" is not listened for!"
      Resolution: Add the relevant event to the "Events" property or select the wildcard "*".

Links and References

Discussion