Overview
This node sends a booking link notification using the 97Display Notification API. It is designed to send notifications via email and/or SMS based on the provided booking information. Typical use cases include automating appointment reminders, event invitations, or any scenario where a calendar booking link needs to be communicated to users through multiple channels.
For example, when a new booking is created in a system, this node can automatically send an email and SMS containing the booking link to the customer, improving communication efficiency and reducing manual follow-up.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The identifier of the organization, typically extracted from incoming webhook data. |
| Workflow ID | The unique identifier of the current workflow execution. |
| Send Email? | Boolean flag indicating whether to send the booking link via email (true/false). |
| Send SMS? | Boolean flag indicating whether to send the booking link via SMS (true/false). |
| APIKey | The API key used for authenticating requests to the 97Display Notification API, sourced from environment variables. |
Output
The node outputs an array of JSON objects, each representing the response from the 97Display Notification API for each input item processed. Each output JSON contains the API's response data confirming the success or failure of sending the booking link notification.
If an error occurs during processing and the node is configured to continue on failure, the output JSON will contain an error field with the error message.
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 credential set as an environment variable (
apikey) for authentication. - Relies on webhook input data containing booking details such as tokens for email and organization name, and the calendar booking link.
Troubleshooting
Common issues:
- Missing or invalid API key will cause authentication failures.
- Incorrect or missing booking link or email tokens in the webhook payload may result in failed notifications.
- Network connectivity issues to the API endpoint can cause request timeouts or errors.
Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Common error messages might relate to authorization failures or malformed request bodies.
Resolution tips:
- Verify that the API key environment variable is correctly set and valid.
- Ensure the webhook payload includes all required fields (
@LocationEmail,@OrganizationName,CalendarBookingLink). - Check network connectivity and API endpoint availability.
Links and References
- 97Display Notification API Documentation (assumed public API docs)
- n8n documentation on HTTP Request Node for understanding API calls within workflows