Nookal icon

Nookal

Interact with Nookal practice management system via GraphQL API
Join our community

Actions14

Overview

This node integrates with the Nookal practice management system via its GraphQL API. Specifically, for the Patient - Get All operation, it retrieves a list of patients from the Nookal system. This is useful in scenarios where you want to fetch multiple patient records for reporting, synchronization, or further processing within an automation workflow.

For example, a healthcare provider might use this node to pull all patient data into a CRM or analytics platform, or to trigger follow-up actions based on patient information.

Properties

Name Meaning
Limit Max number of patient results to return (minimum 1, maximum 100). Controls how many patient records are fetched in one execution. Default is 50.

Output

The output JSON contains a list of patient objects under the patients field structured as follows:

  • Each patient includes:
    • id: Unique identifier of the patient.
    • firstName, lastName: Patient's name.
    • email: Contact email.
    • phone: Contact phone number.
    • dateOfBirth: Patient's date of birth.
    • gender: Gender of the patient.
    • createdAt, updatedAt: Timestamps for record creation and last update.

Additionally, pagination info is provided under pageInfo with fields:

  • hasNextPage, hasPreviousPage: Booleans indicating if more pages exist.
  • startCursor, endCursor: Cursors for pagination control.

The node returns these patient records as an array of JSON objects, suitable for downstream processing.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate with the Nookal GraphQL API.
  • The node depends on the internal helper function to make authenticated GraphQL requests to Nookal.
  • No other external dependencies are required.

Troubleshooting

  • Invalid limit value: Ensure the "Limit" property is between 1 and 100. Values outside this range may cause errors or unexpected behavior.
  • Authentication errors: If the node fails due to authentication, verify that the OAuth2 credentials are correctly set up and have not expired.
  • API request failures: Network issues or API downtime can cause errors. Check connectivity and Nookal service status.
  • JSON parsing errors: Although unlikely in this operation, malformed responses could cause issues; ensure the API response format matches expectations.

If errors occur, the node will throw descriptive messages indicating the problem, such as unknown operations or invalid parameters.

Links and References

Discussion