OnceHub

OnceHub

· #183 most-used

Schedule smarter — book, qualify, and act without lifting a finger

SchedulingCRMSalesMarketingAutomationCommunicationProductivity

OnceHub is a scheduling and lead-capture platform that combines booking pages, chatbot qualification, and contact management into one pipeline-ready system. Connect it to Actionist and your agents can schedule meetings, recover no-shows, mark cancellations, route leads by segment, and react to every booking lifecycle event — all in real time, all without a rep lifting a finger. Whether you need to auto-book renewal calls when trials expire or fire a re-engagement sequence the instant a prospect no-shows, OnceHub gives your agents the scheduling backbone to close the loop autonomously.

Average time saved
10 hours
per person · per month
1 workdays back

Eliminates manual work. Agents eliminate manual no-show recovery, post-call CRM updates, re-engagement follow-ups, and cross-system booking synchronisation — the repetitive scheduling overhead that eats 14 hours a week across a typical revenue team.

Schedule

What your OnceHub agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
TueThu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

OnceHub × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~35 hrsSaved / week
6Personas served
For customer success
Featured4 apps

No-show to re-booked in minutes

When a customer misses their scheduled check-in, your agent takes over the recovery sequence immediately — the booking is marked no-show in OnceHub, their future meeting schedule is checked for gaps, the CRM activity is updated, a personalised re-booking message lands in Slack for the CSM, and a fresh calendar hold is placed for the earliest available slot. The customer gets a re-engagement email before the rep has even noticed the missed call.

~8 hrs / week

Time saved for your team — every week, on autopilot

The flow
Trigger·When a booking ends without the customer joining and OnceHub fires a Booking No-Show event
Result
Mark Booking as No-Show and trigger recovery flowPost re-engagement alert to CSM with contact summary and re-book linkCreate a follow-up calendar hold for the next available recovery slot
The win
Saved per run
25 min
Runs / week
~18×
Zero missed recovery windows
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual demo briefing prep

    Rep opens CRM, exports intake form answers, and writes a pre-call brief — takes 18 minutes per meeting.

    Sales Agent
    0 min
    Agent delivers briefing in 60 seconds

    The moment a booking is confirmed, the agent pulls form answers and drops a structured brief in Slack before the rep even opens their calendar.

  • Marketing
    13 min / week
    Campaign-to-demo tracking

    Marketer manually traces which campaign drove each demo booking and logs it in the attribution sheet — 13 minutes per week.

    Marketing Agent
    0 min
    Agent auto-logs campaign attribution

    On every booking triggered by a campaign click, the agent writes the source, UTM params, and booking ID to the attribution tracker in one pass.

  • Customer Support
    18 min / week
    No-show recovery emails

    CSM notices a missed check-in, writes a personalised re-booking email, and waits — 18 minutes of attention per no-show.

    Customer Support Agent
    0 min
    Agent sends recovery email instantly

    Within five minutes of a no-show event, the agent sends a personalised re-booking message with a fresh OnceHub link and creates the follow-up task.

  • Human Resources
    7 min / week
    Interview confirmation logging

    HR coordinator manually copies candidate booking details into the hiring tracker after each confirmation — 7 minutes per booking.

    Human Resources Agent
    0 min
    Agent logs interview details automatically

    When an interview booking is confirmed, the agent writes the candidate name, role, slot, and interviewer to the hiring tracker and creates a prep document.

  • Finance
    13 min / week
    Renewal call scheduling

    Finance or CSM manually identifies expiring trials and books renewal calls by emailing back and forth — 13 minutes per renewal.

    Finance Agent
    0 min
    Agent books renewal call on expiry

    When a trial record expires, the agent retrieves available slots, schedules the renewal call, and updates the billing deal stage with zero human involvement.

  • Operations
    25 min / week
    Capacity rebalancing across reps

    Ops manager monitors rep booking loads each week and manually redistributes meetings when someone is over-capacity — 25 minutes per week.

    Operations Agent
    0 min
    Agent rebalances load automatically

    When a rep's booking count crosses threshold, the agent identifies lower-priority meetings, reschedules them to available colleagues, and logs the change.

  • Legal
    6 min / week
    Contract-review call coordination

    Legal coordinator manually checks schedules and emails back and forth to book contract review calls — 6 minutes per scheduling chain.

    Legal Agent
    0 min
    Agent books legal review slot directly

    When a contract review task is created, the agent queries OnceHub for available legal team slots and books the call without a single scheduling email.

+ 100s of other OnceHub automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 people
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on OnceHub's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug OnceHub into Actionist

Pick the connection method that suits your environment.

The fastest path — OnceHub's MCP server connects through a permissioned OAuth handshake so the agent can read bookings, manage contacts, and react to scheduling events without any token management on your end.

1
Open the Apps tab

Find OnceHub in the Apps library and click Connect. MCP is selected by default.

2
Authorise in OnceHub

You'll be redirected to OnceHub to approve the Actionist connection. Sign in with your OnceHub admin account and grant the requested scheduling and contacts permissions.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

18 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

15 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with OnceHub

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with OnceHub

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about OnceHub + Actionist

How does Actionist connect to OnceHub?
The recommended method is MCP — you authorise the connection with your OnceHub admin account via OAuth, and the agent gains permissioned access to your bookings, contacts, and event types. No tokens to manage. Alternatively, you can use a personal API token generated from OnceHub Account Settings → Integrations → API.
Which OnceHub objects can the agent read and write?
The agent can read and write bookings (schedule, cancel, reschedule, mark no-show, get details, list), contacts (find, create, update, list, get future meetings), booking pages (create, update), event types (get details, list), and availability slots. It can also react to any of the 15 webhook triggers covering the full booking and contact lifecycle.
How do I avoid triggering infinite loops when the agent updates a booking?
Two safeguards prevent loops: first, use OnceHub's idempotency — the agent should check booking status before writing a change (e.g. confirm a booking isn't already marked no-show before marking it again). Second, in your Actionist workflow, add a condition node that checks whether the triggering event was itself agent-authored by comparing the booking's last-modified-by field. If the agent modified it, skip the write — loop broken.
Can the agent respond to events on all booking pages, or only specific ones?
OnceHub webhooks are configurable at the account level and can be filtered by booking page or event type. When you connect via MCP, Actionist registers listeners for the events you select. If you want the agent to react only to enterprise demo bookings, filter the webhook subscription to that specific booking page — the agent won't fire on SMB or support pages.
What happens if the agent tries to schedule a booking when no slots are available?
The agent first calls Get Available Time Slots to confirm availability before scheduling. If no slots are returned for the requested window, the agent can either widen the search range, send a Request Reschedule to the contact, or create a follow-up task for the rep to handle manually — your workflow design controls which fallback fires. The agent never blindly calls Schedule Booking without first verifying availability.
Does connecting OnceHub give the agent access to all team members' calendars?
The MCP connection is scoped to the OnceHub account you authorise — it can access booking pages, contacts, and bookings within that account but does not touch the underlying calendar apps (Google Calendar, Outlook) directly. Calendar changes surface in OnceHub as booking updates; the agent modifies scheduling through OnceHub's API, not by writing to calendar apps directly.
How does the agent handle cancelled-and-rescheduled bookings differently from plain cancellations?
OnceHub fires distinct webhook events: Booking Canceled for a plain cancellation, and Booking Cancelled and Rescheduled when the contact immediately picks a new slot. Your agent can route these differently — a plain cancellation triggers a re-engagement email, while a cancel-and-reschedule updates the CRM deal with the new meeting time and skips the recovery sequence entirely. One webhook, two different downstream paths.
Are there rate limits I should be aware of when running high-volume booking automations?
OnceHub's API enforces rate limits on a per-account basis; the exact threshold is documented in their developer portal. For high-volume workflows — such as batch-creating bookings after a webinar — the agent should use List Bookings to retrieve existing records before creating new ones, and space write operations using a queue rather than firing them all simultaneously. If your workflow processes more than 50 bookings per minute, contact OnceHub support to confirm your plan's API limit.