Resource Guru logo Resource Guru automation · runs daily

Approve or decline Resource Guru booking requests

With the Approval Workflow on, every confirmed booking for your people waits for you. The queue fills while you are in meetings, and the person who booked is waiting for an answer.

Cotlet does it in your own Resource Guru account with list_bookings and resolve_booking, called by your AI agent, an n8n workflow or a script.

Sign up free All Resource Guru tools

Hosted · nothing to install or maintain

Can Resource Guru do this on its own?

Resource Guru has no rule-based approval (checked 23 Oct 2026). The Approval Workflow is part of the Master plan, approvers act one booking at a time, and the official MCP server is read-only. The public API has a resolve call for approve and decline, which you would wire to your own OAuth app.

How you do it in Resource Guru today

  1. An approver opens the Dashboard and reviews booking requests there, or opens a pending booking on the Schedule.
  2. The green thumbs up approves a booking, and the red thumbs down declines it with an optional reason.
  3. For a multi-resource booking, each booked person is approved or declined on their own.
  4. Once a booking is resolved, Resource Guru emails the booker, with the reason if one was given.
  5. A booker can send a reminder to approvers from the booking menu, which means a slow queue produces more email.

How to approve or decline Resource Guru booking requests

Prompt

List bookings waiting for my approval. Approve the ones inside the person's normal hours and decline any over 8 hours a day with the reason "Over daily limit".
  1. 01

    Read the queue

    list_bookings runs with approval_state set to pending. The agent gets each booking with its people, days, hours per day and project.

  2. 02

    Apply your rule

    Each booking is checked against the rule in your prompt, for example hours per day or a project that needs a second look. The agent states which rule each decision rests on.

  3. 03

    Approve what fits

    resolve_booking with approved runs for every resource on the booking that passes. The call waits for your OK by default.

  4. 04

    Decline with a reason

    resolve_booking with declined carries your reason text, which Resource Guru puts in the email to the booker. Declined bookings stop taking up availability.

  5. 05

    Stay inside your role

    A booking you are not an approver for returns a permission error. The agent lists it and moves on without retrying.

What you get back

Example data

Pending bookings: 9
Approved 6
Declined 2 ("Over daily limit"): Sam Okafor 10h on 4 Nov, Lena Ortiz 9h on 5 Nov
Not mine to approve: 1 (approver is Dana)

Other ways to ask

  • Approve everything booked by the account managers and list the rest for me.
  • Show pending bookings older than two days and send the approvers a reminder, but approve nothing.
  • Decline pending bookings for the Brand Refresh project with the reason "Project on hold".

What Resource Guru allows, and what to know first

  • The Approval Workflow is part of the Master plan, and an Administrator turns it on under Settings > Approval Workflow.
  • Declined bookings do not take up availability, and they show on the Schedule struck through.
  • Anyone can be an approver, including people with Dashboard-only access, and a person can approve their own bookings.
  • An approver is set per person or resource, with optional default approvers for new ones.

resolve_booking asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: Resource Guru Help: Set up of Approvers and Approving Bookings · Resource Guru Help: Enabling and Disabling the Approval Workflow · Resource Guru Help: Create Bookings · Resource Guru API documentation: Approve/Decline a booking

Call resolve_booking from a script

curl

curl -X POST https://cotlet.dev/api/v1/resource-guru/bookings/48213107/resolve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resolution":"declined","resource_ids":[18214],"reason":"Over daily limit"}'

Example response

{
  "booking_id": 48213107,
  "resolution": "declined",
  "resource_ids": [
    18214
  ],
  "reason": "Over daily limit"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is resource_guru_write → resolve_booking. Example data.

Schedule it in n8n, Make, Zapier or cron

Resource Guru tools this automation uses

Cotlet Resource Guru tools used to approve or decline Resource Guru booking requests
Tool Parameters
list_bookings start_date, end_date, resource_ids, approval_state, waiting
resolve_booking booking_id, resolution, resource_ids, reason
All 13 Resource Guru tools with descriptions

Frequently asked questions

Is it safe to connect Resource Guru to Cotlet?

Yes. You sign in to Resource Guru yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Resource Guru once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Give your agent access to Resource Guru.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Resource Guru.

Sign up free