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 Location resource and the Get operation, it retrieves detailed information about a single location by its unique ID.

Use cases include:

  • Fetching address, contact, and timezone details of a specific clinic or office location.
  • Integrating location data into workflows that require geographic or contact info for appointments or practitioners.
  • Synchronizing location details from Nookal into other systems or databases.

Example: You want to get the full address and contact info of a location before scheduling an appointment or sending notifications.

Properties

Name Meaning
ID The unique identifier of the Location resource to retrieve. This is required.

Output

The output JSON contains a location object with the following structure:

  • id: Unique identifier of the location.
  • name: Name of the location.
  • address: An object containing:
    • street
    • city
    • state
    • postcode
    • country
  • phone: Contact phone number.
  • email: Contact email address.
  • timezone: Timezone of the location.
  • createdAt: Timestamp when the location was created.
  • updatedAt: Timestamp when the location was last updated.

No binary data is output by this operation.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate with the Nookal GraphQL API.
  • Network access to the Nookal API endpoint.
  • Proper permissions on the API key to read location data.

Troubleshooting

  • Invalid ID error: If the provided ID does not exist or is malformed, the API may return an error or empty result. Verify the ID is correct.
  • Authentication errors: Ensure the OAuth2 credentials are valid and have not expired.
  • Network issues: Check connectivity to the Nookal API endpoint.
  • JSON parsing errors: Not applicable here since no user-provided JSON input is parsed for this operation.
  • API rate limits: If many requests are made rapidly, the API might throttle; implement retry logic or reduce request frequency.

Links and References

Discussion