Zoho Bookings icon

Zoho Bookings

Node for Zoho Bookings

Actions11

Overview

This node integrates with Zoho Bookings to manage appointments programmatically. Specifically, the "Mark As Completed" operation allows users to mark an existing appointment as completed after it has started. This is useful in workflows where you want to update the status of appointments automatically based on external triggers or business logic, such as confirming service delivery or closing tasks related to the appointment.

Practical examples include:

  • Automatically marking appointments as completed once a service provider confirms the job is done.
  • Integrating with CRM or invoicing systems to trigger billing only after appointments are marked completed.
  • Updating calendars or dashboards to reflect the current status of appointments without manual intervention.

Properties

Name Meaning
Booking ID The unique identifier of the appointment to be marked as completed. It corresponds to the "Booking ID" shown on the appointment page.
Additional Fields > Zoho Region Select the Zoho region for the API endpoint. Options: United States of America, European Union, India, Australia, China. Defaults to United States of America (.com).
This will only work after the appointment has started. See docs for more info. Informational notice indicating that marking an appointment as completed is only valid after the appointment start time.

Output

The node outputs a JSON object under the field zohoResponse containing the response from the Zoho Bookings API after attempting to mark the appointment as completed. This typically includes confirmation of the status update or error details if the operation failed.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "zohoResponse": {
    "status": "success",
    "message": "Appointment marked as completed",
    "booking_id": "#appt-06594"
  }
}

Dependencies

  • Requires an active Zoho Bookings OAuth2 API credential configured in n8n for authentication.
  • Depends on the Zoho Bookings API being accessible and the correct region selected to form the API base URL.
  • 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 completed before its scheduled start time will likely fail or have no effect, as indicated by 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:

    • Errors returned from the Zoho API will be included in the node's error output. Common messages might relate to invalid booking IDs, unauthorized access, or invalid request parameters.
    • If the node throws an error about authentication, verify that the OAuth2 credentials are correctly set up and authorized.
    • Timezone mismatches or incorrect date formats can cause failures; ensure the appointment times are correctly formatted and timezone-aware if applicable.

Links and References

Discussion