Build meaningful on-brand scheduling experiences with OnceHubs online appointment booking software
Oncehub currently provides 9 triggers that can start a workflow and 3 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Booking Canceled Then Rescheduled
Triggered when Customer cancels a booking and then reschedules on a different booking page.
Booking Canceled
Triggered when User or Customer cancels a booking
Booking Completed
Triggered when booking end time has passed.
Booking No-Show
Triggered when User sets the completed booking to No-show
Booking Rescheduled
Triggered when Customer reschedules a booking on the same booking page and Customer reschedules a booking following a request from the User to reschedule
Booking Scheduled
Triggered when Customer schedules a booking and when User approves a booking requested by a Customer
Conversation Abandoned
Triggered when website visitor stops interacting with a bot for more than 10 minutes.
Conversation Closed
Triggered when: Website visitor reaches the end of the conversation flow and when Website visitor starts a new conversation with a different chatbot
Conversation Started
Triggered when website visitor starts interacting with a chatbot.
Find Contact
Search for contacts in Oncehub by various criteria
Create Contact
Create a new contact in Oncehub. Either email or mobile_phone is required.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Oncehub event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Booking Canceled Then Rescheduled
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Oncehub action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Find Contact
Combine Oncehub with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
Booking Canceled Then Rescheduled
Finishes with
Find Contact, then preserve the outcome in Coherence
The exact authentication fields depend on Oncehub. The workflow structure stays straightforward:
Authorize the Oncehub account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Oncehub or provide a complementary trigger or action.
Oncehub currently provides 9 triggers that can start a workflow and 3 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Oncehub currently lists 9 triggers and 3 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Oncehub triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
