Overview
The Symbiosika Chat Trigger node starts an n8n workflow when specific chat events occur within the Symbiosika platform. It is designed to listen for real-time chat messages or other defined events related to an organisation's Symbiosika environment.
Common scenarios where this node is beneficial include:
- Automating responses or follow-up actions when a new chat message is received in Symbiosika.
- Integrating Symbiosika chat events with other systems, such as CRM, ticketing, or notification platforms.
- Monitoring organisational-wide chat activity by setting up webhooks that trigger workflows on relevant events.
For example, you could use this node to trigger a workflow that logs every incoming chat message into a database or sends alerts to team members when certain keywords appear in chats.
Properties
| Name | Meaning |
|---|---|
| Organisation Name or ID | Select the organisation from a dynamically loaded list or specify its ID via expression. |
| Name To Display In Symbiosika | The name of the webhook as it will appear inside the Symbiosika platform. |
| Events | The event type to listen for. Currently supports "Chat Output" which triggers when a new message arrives. |
| Use Organisation-Wide? | Boolean flag indicating if the webhook applies to the entire organisation rather than a subset. |
Output
The node outputs JSON data representing the event payload received from Symbiosika. Specifically, the json output contains the full body of the webhook POST request, which includes details about the chat event (e.g., message content, sender, timestamps).
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Symbiosika Chat API.
- Needs network access to the Symbiosika API endpoints to register, check, and delete webhooks.
- The node uses dynamic loading of organisations via the Symbiosika API to populate the organisation selection dropdown.
Troubleshooting
- Failed to load organisations: This error occurs if the API call to fetch organisations fails or returns invalid data. Check that the API key credential is valid and has sufficient permissions.
- Symbiosika webhook registration failed: Indicates failure during webhook creation. Verify the webhook URL is accessible publicly and the API key is correct.
- Invalid response format for organisations: Means the API returned unexpected data. Confirm the API endpoint and credentials are correct.
- If the webhook does not trigger workflows, ensure the webhook URL configured in Symbiosika matches the one generated by n8n and that the event type is correctly selected.
Links and References
- n8n Expressions Documentation
- Symbiosika API documentation (not provided in source; consult your Symbiosika platform docs)