Symbiosika Chat Trigger icon

Symbiosika Chat Trigger

Starts the workflow when Symbiosika chat events occur
Join our community

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 actions when new chat messages arrive in Symbiosika.
  • Integrating Symbiosika chat events with other systems, such as CRM, ticketing, or notification platforms.
  • Monitoring organisational-wide chat activity or specific team chats for triggers.

For example, you could use this node to trigger a workflow that logs every incoming chat message into a database or sends alerts to a Slack channel whenever a new message is received.

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 for identification.
Events The event type to listen for. Currently supports: "Chat Output" which triggers on new messages.
Use Organisation-Wide? Boolean flag indicating if the webhook applies to the entire organisation (true) or not (false).

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 triggered.

No binary data output is produced by this node.

Example output structure (simplified):

[
  {
    "messageId": "string",
    "content": "string",
    "sender": "string",
    "timestamp": "string",
    ...
  }
]

The exact fields depend on the Symbiosika chat event payload.

Dependencies

  • Requires an API key credential for authenticating with the Symbiosika Chat API.
  • Needs network access to the Symbiosika API endpoints.
  • The node dynamically loads organisations via the API to populate the organisation selection dropdown.
  • The webhook URL must be publicly accessible for Symbiosika to send events.

Troubleshooting

  • Failed to load organisations: This error occurs if the API key is invalid or the Symbiosika API is unreachable. Verify the API key and network connectivity.
  • Symbiosika webhook registration failed: Happens if the webhook creation request fails. Ensure the webhook URL is reachable and the API key has sufficient permissions.
  • Invalid response format for organisations: Indicates unexpected API response; check if the API endpoint or credentials have changed.
  • If no events are triggering workflows, confirm that the webhook is correctly registered in Symbiosika and that the selected event matches the expected trigger.
  • Make sure the "Use Organisation-Wide?" setting aligns with your intended scope; incorrect usage may cause missed events.

Links and References

Discussion