Zoho Bookings icon

Zoho Bookings

Node for Zoho Bookings

Actions11

Overview

This node integrates with Zoho Bookings to manage appointment-related actions, specifically here focusing on the "Mark As No Show" operation for appointments. It allows users to mark an existing appointment as a no-show after it has started, which is useful for tracking attendance and managing scheduling workflows.

Common scenarios include:

  • Automatically updating appointment status when a client fails to show up.
  • Triggering follow-up actions or notifications based on no-shows.
  • Keeping accurate records of appointment outcomes for reporting or billing.

Example: After an appointment time passes without client attendance, this node can be used to mark that appointment as a no-show in Zoho Bookings, enabling downstream automation such as sending reminders or applying penalties.

Properties

Name Meaning
Booking ID The unique identifier of the appointment to update, found under the "Booking ID" field on the appointment page (e.g., "#appt-06594").
Additional Fields > Zoho Region Select the Zoho region corresponding to your account's data center. Options: United States of America (.com), European Union (.eu), India (.in), Australia (.com.au), China (.com.cn).
This will only work after the appointment has started. See docs for more info. Informational notice indicating that marking an appointment as no-show is only valid after the appointment start time.

Output

The node outputs a JSON object containing the response from the Zoho Bookings API related to the status update request. Specifically:

  • json.zohoResponse: Contains the raw API response confirming the appointment status change to "no-show". This typically includes success confirmation or error details if the update failed.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Zoho Bookings OAuth2 API credential configured in n8n for authentication.
  • Depends on the Zoho Bookings API endpoint, which varies by selected region (e.g., .com, .eu).
  • Uses the luxon library internally for date/time formatting but this is abstracted away from the user.

Troubleshooting

  • Common issues:

    • Attempting to mark an appointment as no-show before its scheduled start time will likely fail or have no effect, as per the informational notice.
    • Incorrect or missing Booking ID will cause the API call to fail.
    • Using the wrong Zoho region may result in authentication errors or resource not found errors.

  • Error messages:

    • Authentication errors indicate problems with the OAuth2 credentials; verify token validity and permissions.
    • "Booking not found" or similar errors suggest the Booking ID is incorrect or does not exist in the specified region/account.
    • API rate limits or network errors may cause temporary failures; retry logic or error handling should be implemented accordingly.

Links and References

Discussion