Superchat Trigger icon

Superchat Trigger

Handle Superchat events via webhooks

Superchat Trigger

AI-generated

Overview

This node acts as a trigger for Superchat events via webhooks. It listens for various event types such as contact creation, contact updates, note creation, inbound and outbound messages, failed messages, and conversation status changes. Users can filter these events by specific channels, inboxes, custom attributes, built-in attributes, or conversation statuses. This node is useful for automating workflows based on real-time Superchat events, such as updating CRM systems when a contact is created or sending notifications when a message fails.

Use Case Examples

  1. Trigger a workflow when a new contact is created in Superchat.
  2. Listen for inbound messages on specific channels to automate responses.
  3. React to conversation status changes like 'done' or 'open' to update task statuses.

Properties

Name Meaning
Trigger On Specifies the type of Superchat event to listen for, such as contact creation, message inbound, or conversation status changes.
Filter by Channel Filter events to only listen for messages or conversation status changes on specified channels.
Filter by Inbox Filter events to only listen for messages or conversation status changes on specified inboxes.
Filter by Custom Attribute Filter contact updated events based on changes to specified custom attributes.
Filter by Built-in Attribute Filter contact updated events based on changes to specified built-in attributes like first name, last name, or gender.
Filter by Conversation Status Filter conversation status change events based on the new status, such as done, open, or snoozed.

Output

JSON

  • body - The JSON payload received from the Superchat webhook containing event data.

Dependencies

  • Requires an API key credential for Superchat API authentication to manage webhooks.

Troubleshooting

  • Webhook creation may fail if the target URL is incorrect or unreachable. Ensure the webhook URL is accessible from Superchat.
  • If events are not triggering, verify that the correct event type and filters are set in the node configuration.
  • Deleting a webhook may fail if the webhook ID is missing or invalid; ensure the workflow static data is intact.
  • API request failures may occur due to invalid credentials or network issues; check API key validity and network connectivity.

Links

Discussion