Nookal icon

Nookal

Interact with Nookal practice management system via GraphQL API

Actions14

Overview

This node integrates with the Nookal practice management system via its GraphQL API, allowing users to perform various operations on healthcare-related resources such as Patients, Appointments, Practitioners, and Locations. Specifically, for the Patient - Get operation, the node retrieves detailed information about a single patient by their unique ID.

Common scenarios where this node is beneficial include:

  • Fetching patient details to display in a custom dashboard or application.
  • Integrating patient data retrieval into automated workflows, such as appointment scheduling or follow-up reminders.
  • Synchronizing patient records between Nookal and other systems.

Example use case: A clinic wants to automatically pull patient contact details when an appointment is booked, enabling staff to quickly access relevant patient information.

Properties

Name Meaning
ID The unique identifier of the patient resource to retrieve. This is required for the "Get" operation.

Output

The output JSON contains detailed patient information structured as follows:

  • id: Patient's unique identifier.
  • firstName: Patient's first name.
  • lastName: Patient's last name.
  • email: Patient's email address.
  • phone: Patient's phone number.
  • dateOfBirth: Patient's date of birth.
  • gender: Patient's gender.
  • address: An object containing:
    • street
    • city
    • state
    • postcode
    • country
  • createdAt: Timestamp when the patient record was created.
  • updatedAt: Timestamp when the patient record was last updated.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication credential (OAuth2 token) configured in n8n to access the Nookal GraphQL API.
  • Relies on the internal helper function to make authenticated GraphQL requests to Nookal.
  • No additional external dependencies are needed beyond proper API credentials.

Troubleshooting

  • Invalid or missing ID: If the provided patient ID is incorrect or not found, the API may return an error or empty result. Verify the ID is correct.
  • Authentication errors: Ensure that the OAuth2 API credentials are correctly set up and have sufficient permissions.
  • Network issues: Connectivity problems can cause request failures; check network access to the Nookal API endpoint.
  • Malformed response or parsing errors: These are rare but could occur if the API changes; updating the node or checking API status might help.

Common error messages:

  • "Unknown patient operation": Indicates an unsupported operation was requested; verify the operation parameter.
  • "Invalid JSON in variables field": Relevant only for custom queries; ensure JSON syntax is correct if used.

Links and References

Discussion