Actions14
Overview
This node integrates with the Nookal practice management system via its GraphQL API, allowing users to manage healthcare-related resources such as patients, appointments, practitioners, and locations. Specifically, for the Practitioner resource with the Get All operation, the node fetches a list of practitioners from the Nookal system.
Common scenarios where this node is beneficial include:
- Retrieving a list of all practitioners in a healthcare practice for reporting or synchronization purposes.
- Automating workflows that require practitioner data, such as scheduling or notifications.
- Integrating practitioner information into other systems like CRM or billing platforms.
For example, a clinic might use this node to regularly pull updated practitioner lists to keep their internal directory current or to assign appointments dynamically based on available practitioners.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return. Accepts a number between 1 and 100. Defaults to 50. |
Output
The output JSON contains an array of practitioner objects with the following structure for each practitioner:
id: Unique identifier of the practitioner.firstName: Practitioner's first name.lastName: Practitioner's last name.email: Email address of the practitioner.phone: Contact phone number.specialties: List of specialties associated with the practitioner.locations: Array of location objects where the practitioner works, each containing:id: Location ID.name: Location name.
createdAt: Timestamp when the practitioner record was created.updatedAt: Timestamp when the practitioner record was last updated.
Additionally, pagination information is included under pageInfo with fields:
hasNextPagehasPreviousPagestartCursorendCursor
This allows handling of paginated results if more practitioners exist beyond the specified limit.
The node does not output binary data.
Dependencies
- Requires an active connection to the Nookal practice management system via its GraphQL API.
- Needs an API authentication token configured in n8n credentials (an OAuth2 API credential).
- The node uses internal helper functions to send GraphQL queries to Nookal's API endpoint.
Troubleshooting
- Invalid JSON in variables field: If using custom queries with variables, ensure the JSON syntax is correct.
- Unknown operation error: Selecting an unsupported operation for the Practitioner resource will throw an error. Use only "Get" or "Get All".
- API authentication errors: Ensure the API key or OAuth2 token is valid and has sufficient permissions.
- Limit out of range: The limit property must be between 1 and 100; values outside this range may cause errors or unexpected behavior.
- Network or API downtime: Connectivity issues with the Nookal API will result in request failures.
To resolve these issues, verify credentials, input parameters, and network connectivity.
Links and References
- Nookal Practice Management System
- GraphQL Pagination Concepts
- n8n Documentation on Creating Custom Nodes