Actions14
Overview
This node integrates with the Nookal practice management system via its GraphQL API, allowing users to manage appointments programmatically within n8n workflows. Specifically, the "Appointment - Update" operation enables updating details of an existing appointment by specifying its ID and the new data fields.
Common scenarios for this node include:
- Rescheduling an appointment by changing start and end times.
- Updating appointment details such as type or notes.
- Changing associated patient, practitioner, or location information.
Practical example: A clinic automates appointment rescheduling by triggering this node when a patient requests a new time slot, updating the appointment's start and end times accordingly.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the appointment to update. |
| Appointment Data | Collection of fields to update on the appointment: - Patient ID (string, required) - Practitioner ID (string, required) - Location ID (string, required) - Start Time (dateTime, required) - End Time (dateTime, required) - Type (string) - Notes (string, multiline) |
Output
The node outputs JSON data representing the updated appointment object, including fields such as:
id: Appointment identifier.startTimeandendTime: Updated timestamps.type: Appointment type.status: Current status of the appointment.notes: Any notes attached to the appointment.updatedAt: Timestamp of last update.
If errors occur during the update, the output includes an errors array detailing which fields caused issues and corresponding messages.
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Nookal GraphQL API.
- Relies on the external Nookal practice management system being accessible and the API credentials having sufficient permissions to update appointments.
Troubleshooting
- Invalid ID: If the provided appointment ID does not exist, the API will return an error. Verify the ID is correct.
- Missing Required Fields: The update requires certain fields in the appointment data (patientId, practitionerId, locationId, startTime, endTime). Omitting these may cause errors.
- API Authentication Errors: Ensure the API key or OAuth2 token is valid and has not expired.
- JSON Parsing Errors: Input properties must be correctly formatted; invalid JSON in variables or input fields can cause failures.
- Error Messages: The node surfaces API errors in the
errorsfield of the output. Review these messages to identify and fix issues such as validation errors or permission problems.
Links and References
- Nookal API Documentation (for detailed API schema and capabilities)
- GraphQL Basics (to understand query and mutation structure)