Overview
This node sends a booking link notification via the 97Display Notification API. It is designed to send notifications through email and/or SMS based on user preferences. The node extracts relevant data from an incoming webhook payload, such as organization details, email tokens, and booking links, then posts this information to the external notification service.
Common scenarios include:
- Automatically notifying customers or clients with booking links after they complete a booking process.
- Sending reminders or confirmations via email and SMS simultaneously.
- Integrating booking notifications into workflows that handle scheduling or appointment management.
Practical example:
A workflow receives booking data from a webhook when a customer schedules an appointment. This node then sends the booking link to the customer’s email and phone number using the configured notification API.
Properties
| Name | Meaning |
|---|---|
| Organization ID | Hidden field automatically populated from the webhook payload's OrganizationId value. |
| Workflow ID | Hidden field set to the current workflow's ID. |
| Send Email? | Boolean option to enable or disable sending the booking link via email. Default: true. |
| Send SMS? | Boolean option to enable or disable sending the booking link via SMS. Default: true. |
Output
The node outputs an array of JSON objects, each representing the response from the notification API for each input item processed. Each output item contains the full JSON response returned by the API call.
If an error occurs during the request and the node is configured to continue on failure, the output will contain an object with an error property describing the issue.
No binary data is produced by this node.
Dependencies
- Requires access to the 97Display Notification API endpoint at
https://notificationapitest.api97.com/api/Notification/SendBookingLink. - Needs an API key provided via an environment variable named
MY_API_KEY. - Expects incoming webhook data containing fields like
OrganizationId,Tokens['@LocationEmail'],Tokens['@OrganizationName'], andCalendarBookingLink. - The node uses standard HTTP POST requests with JSON payloads.
Troubleshooting
- Missing or invalid API key: If the environment variable
MY_API_KEYis not set or incorrect, the API call will fail. Ensure the API key is correctly configured in n8n environment variables. - Webhook data missing required fields: The node expects specific fields in the webhook payload (e.g.,
Tokens['@LocationEmail'],CalendarBookingLink). Missing these will cause errors or incomplete notifications. - Network or API errors: If the notification API is unreachable or returns an error, the node will throw an error unless "Continue On Fail" is enabled.
- Incorrect boolean flags: Setting both "Send Email?" and "Send SMS?" to false will result in no notification being sent; verify these settings before execution.
Links and References
- 97Display Notification API Documentation (assumed base URL)
- n8n documentation on HTTP Request Node for understanding API calls
- n8n environment variables setup guide for managing API keys