Overview
Connect Zoho Bookings with Flows360
Zoho Bookings is an appointment scheduling software for managing bookings, services, and customer appointments.
Use the Zoho Bookings connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.
Available actions
- Book Appointment
- Reschedule Appointment
- Fetch Availability
- Get Appointment Details
- Cancel Appointment
Available triggers
- No triggers are declared in this pinned package.
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: Zoho Bookings
- Package:
@activepieces/piece-zoho-bookings@0.1.6 - Exact artifact digest:
sha256:811042663a9b6816a6c98eef5b5ef0f7ac2cb456a1c4eeb026dbb1badf34b3e4 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Book Appointment (
bookAppointment), Book an appointment for a customer for a desired service Classification: read. - Reschedule Appointment (
rescheduleAppointment), Reschedule an appointment to a different time or to a different staff Classification: read. - Fetch Availability (
fetchAvailability), Fetch availability of appointments across services Classification: read. - Get Appointment Details (
getAppointmentDetails), Get details of an appointment using its booking ID Classification: read. - Cancel Appointment (
cancelAppointment), Update the status of a booking (cancel, complete, or mark as no-show) Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Access token Required · protected credential
- Data Center Required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Book Appointment | Yes | No | Book an appointment for a customer for a desired service |
| Reschedule Appointment | Yes | No | Reschedule an appointment to a different time or to a different staff |
| Fetch Availability | Yes | No | Fetch availability of appointments across services |
| Get Appointment Details | Yes | No | Get details of an appointment using its booking ID |
| Cancel Appointment | Yes | No | Update the status of a booking (cancel, complete, or mark as no-show) |
Supported actions
Book Appointment · Read
Book an appointment for a customer for a desired service
book_appointment · Risk: low · Retry: safe
Inputs
workspace_id· string · Required, Select the workspace for the appointmentservice_id· string · Required, Select the service for which the appointment is bookedstaff_id· string · Optional, Select the staff member (use this OR resource_id OR group_id)resource_id· string · Optional, Select the resource (use this OR staff_id OR group_id)group_id· string · Optional, The unique ID of the staff group for collective booking (use this OR staff_id OR resource_id)from_time· string · Required, The starting time for the appointment (format: mm-dd-yyyy HH:mm:ss)to_time· string · Optional, End time for resource booking (optional, format: dd-MMM-yyyy HH:mm:ss)timezone· string · Optional, The timezone for the appointment (optional)customer_name· string · Required, Name of the customercustomer_email· string · Required, Email address of the customercustomer_phone· string · Required, Phone number of the customernotes· string · Optional, Additional information about the appointment (optional)additional_fields· object · Optional, Additional customer details as JSON object (optional)cost_paid· number · Optional, Amount paid for the booking (optional)
Reschedule Appointment · Read
Reschedule an appointment to a different time or to a different staff
reschedule_appointment · Risk: low · Retry: safe
Inputs
from_time· string · Required, Start of the date range used to fetch existing bookings (to help you select the Booking ID to reschedule). Not sent to the reschedule API. Format: dd-MMM-yyyy HH:mm:ssto_time· string · Optional, End of the date range used to fetch existing bookings (optional). Not sent to the reschedule API. Format: dd-MMM-yyyy HH:mm:ssbooking_id· string · Required, Select the appointment to get details forservice_id· string · Optional, Select service to filter staff optionsstaff_id· string · Optional, Select the staff to reschedule to (use this OR group_id OR start_time)group_id· string · Optional, The unique ID of the staff group to reschedule to (use this OR staff_id OR start_time)start_time· string · Required, The new time to reschedule the appointment to (format: dd-MMM-yyyy HH:mm:ss, use this OR staff_id OR group_id)
Fetch Availability · Read
Fetch availability of appointments across services
fetch_availability · Risk: low · Retry: safe
Inputs
workspace_id· string · Required, Select the workspace to fetch availability forservice_id· string · Required, Select the service for which availability is to be fetchedstaff_id· string · Optional, Select the staff member (use this OR group_id OR resource_id)group_id· string · Optional, The unique ID of the staff group associated with the service (use this OR staff_id OR resource_id)resource_id· string · Optional, Select the resource (use this OR staff_id OR group_id)selected_date· string · Required, The date on which services are checked for availability (format: mm-dd-yyyy)
Get Appointment Details · Read
Get details of an appointment using its booking ID
get_appointment_details · Risk: low · Retry: safe
Inputs
from_time· string · Required, The start time of the appointment (in ISO 8601 format)to_time· string · Optional, The end time of the appointment (in ISO 8601 format)booking_id· string · Required, Select the appointment to get details for
Cancel Appointment · Read
Update the status of a booking (cancel, complete, or mark as no-show)
cancel_appointment · Risk: low · Retry: safe
Inputs
from_time· string · Required, The starting time for the appointment (format: mm-dd-yyyy HH:mm:ss)to_time· string · Optional, The ending time for the appointment (format: mm-dd-yyyy HH:mm:ss)booking_id· string · Required, Select the appointment to get details for
Setup
Setup
- Add the Zoho Bookings connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- Data Center (
location), required.
OAuth scopes
zohobookings.data.CREATEzohobookings.data.READ
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-zoho-bookings@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 5 actions and 0 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Zoho Bookings connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-zoho-bookings@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.