Skip to content
Explore integrations

Planyo Online Booking integration researchA little less busywork with Planyo Online Booking.

Research only. Grunt is prelaunch, live service is paused, and live provider connections and outcomes remain unverified. The operations and examples below are not confirmed live Grunt features or approved supplier commitments.

Explore possible Planyo Online Booking workflows with Grunt. Documented operations include Reservations: Add reservation payment; Reservations: Check reservation possibility; Reservations: Delete reservation. Actions on this page are research candidates from public integration definitions, not confirmation that Grunt support is live.

Exploratory scope only: these candidates come from public integration definitions and are not confirmed as live Grunt features.

Planyo Online Booking
“Explore whether a Grunt integration could add reservation payment, then check reservation possibility in Planyo Online Booking. Show me the result and wait for my approval before changing anything.”
A workflow idea to explore.

Illustrative steps and outcome; no real work is performed here.

  1. 01Reservations: Add reservation payment
  2. 02Reservations: Check reservation possibility
  3. 03Review the result before anything changes

A clearer next step, with the final say still yours.

Explore possibilities with Planyo Online Booking.

Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.

95 researched capabilities across 31 groups

  • Add reservation payment

    Adds a payment for a reservation.

  • Check reservation possibility

    Returns true if reservation can be made or false if it's not possible.

  • Delete reservation

    Permanently deletes a reservation.

  • Perform reservation action

    Call to perform an administrative action (such as confirmation or cancellation) on a reservation.

  • Get promotable reservations

    Lists all waiting list requests which can be promoted to a valid reservation.

  • List reservations

    Lists all reservations that either start within given time period or that were entered into the system within given time period.

  • Make reservation

    Enters a new reservation into the system.

  • Modify reservation

    Make modifications to an existing reservation.

  • List reservation payments

    List payments made for a reservation, including coupon usage.

  • Get reservation data

    This method returns details of a reservation.

  • Get reservation payment amount

    This method returns payment information for given reservation.

  • Search reservations by form item

    Finds all reservations whose form item has the specified value.

  • Set reservation notes

    Set new user and/or admin notes for a reservation.

  • Set reservation price

    Set a custom price for a reservation.

Proposed setup considerations

The research notes below describe a possible setup. They are not instructions for an available Grunt connection; actual steps depend on supported operations and provider approval.

  1. 01

    Start with a small, useful task.

    Describe a routine step involving Planyo Online Booking. Keep a first version easy to review and change.

  2. 02

    Plan the account access.

    Check which Planyo Online Booking account, data, and permissions a safe connection would need. Start with the least access that can do the job.

  3. 03

    Test the details together.

    Validate a sample against a disposable account. Confirm which records are read, what could change, and how errors or duplicates are handled.

  4. 04

    Keep the say-so.

    Decide which steps could run on their own and which would need your review. Expand access only when the workflow needs it.

RESEARCH NOTES

Questions about the concept.

These notes describe possible uses. Customer availability remains unverified.

What could a Grunt integration do with Planyo Online Booking?

The documented operations include Reservations: Add reservation payment; Reservations: Check reservation possibility; Reservations: Delete reservation; Reservations: Perform reservation action. These are research candidates from public integration definitions and need validation and Grunt implementation before they can be treated as supported capabilities.

Could I keep a workflow read-only?

The research candidates do not confirm an implemented Planyo Online Booking connection or a read-only access mode. If built, verify least-privilege scopes and reject writes at the app API boundary.

Will every action run automatically?

If a connection is built, choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in Planyo Online Booking?

A future integration should let you decide which work could run on its own and which steps need your review.

There’s a Grunt for that

A little less busywork.
A little more you.

Read the current prelaunch status and confirmed prices.

View pricing status Explore the simulation