Overview
This node acts as a trigger for SuperSaaS events, allowing workflows to start when specific changes or actions occur within a SuperSaaS account. It listens for various event types such as new or changed appointments, forms, users, sending mails, reminders, and follow-ups. When the selected event happens, the node receives a webhook call from SuperSaaS containing relevant data, which it then outputs to the workflow.
Common scenarios include:
- Automating notifications or follow-up actions when a new appointment is created.
- Syncing user data when a user is added or modified.
- Triggering workflows based on form submissions or changes.
- Responding to sent emails or reminders automatically.
For example, you could use this node to start a workflow that sends a Slack message whenever a new user registers or to update a CRM system when an appointment changes.
Properties
| Name | Meaning |
|---|---|
| Event (gets parent ID) | The type of SuperSaaS event to listen for. Options include: Changed Appointment, Changed Credit, Changed Form, Changed User, New Appointment, New Form, New User, Send Mail, Sent Follow-Up, Sent Reminder. |
| Parent ID | The identifier related to the selected event, such as Account, Schedule, or Form ID. This value is dynamically loaded based on the chosen event and specifies the scope or parent entity for the webhook. |
Output
The node outputs JSON data received from the SuperSaaS webhook corresponding to the triggered event. The output contains all details sent by SuperSaaS about the event, structured as an array with one object per webhook call.
No binary data output is involved.
Example output structure (simplified):
[
{
"event": "U",
"parent_id": "12345",
"data": {
// event-specific details here
}
}
]
Dependencies
- Requires an API key credential for authenticating with the SuperSaaS API.
- The node uses SuperSaaS REST API endpoints to manage webhooks and load options dynamically.
- If running locally, an optional ngrok URL can be configured in credentials to expose the webhook endpoint publicly.
Troubleshooting
- Missing Parent ID: The node requires a valid Parent ID for the selected event to create the webhook. Ensure you select or load the correct schedule, account, or form ID.
- Webhook Creation Failure: Errors during webhook creation often relate to invalid API keys or network issues. Verify your API key credential and ensure the webhook URL is accessible.
- Webhook Not Triggering: Confirm that the webhook exists in SuperSaaS and matches the event and parent ID. Use the node’s checkExists method or review SuperSaaS webhook settings.
- Localhost Webhook URL Issues: If running n8n locally, configure an ngrok URL in credentials to replace localhost URLs so SuperSaaS can reach the webhook.