Resource Guru logo Resource Guru automation · runs weekly

Confirm or delete tentative Resource Guru bookings

Pencilled bookings pile up while pitches are open. When a deal closes, someone has to find each pencilled booking on the Schedule and confirm or delete it.

Cotlet does it in your own Resource Guru account with list_bookings, update_booking and delete_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 bulk confirm for tentative bookings (checked 23 Oct 2026). Its official MCP server can list them but is read-only, and the blog post for it uses exactly this task as an example prompt: find the people with tentative bookings, then confirm or delete them yourself. The public API can update bookings, but you build the OAuth app and the tool.

How you do it in Resource Guru today

  1. Tentative bookings show on the Schedule as a white container with a coloured outline; with no project they are grey.
  2. Open each booking and switch the Tentative setting off to confirm it, or delete the booking.
  3. If the Approval Workflow is on and a non-approver confirms a tentative booking, the booking then goes to approvers as pending.
  4. A tentative booking is invisible on the Dashboard of the booked person, so nobody but the booker notices a forgotten one.

How to confirm or delete tentative Resource Guru bookings

Prompt

List everyone with tentative bookings next week. Confirm the ones for projects marked won in this list, delete the ones for lost projects and leave the rest for me.
  1. 01

    Collect next week's bookings

    list_bookings returns bookings in the date range with a tentative flag. The agent keeps the ones where tentative is true and groups them by project and by person.

  2. 02

    Match projects to your list

    Each tentative booking is matched to the won and lost lists in your prompt by project name. A booking with no project, or a project in neither list, stays untouched and goes on your list.

  3. 03

    Confirm the won ones

    update_booking sets tentative to false. After this the booked person sees it on their Dashboard, so the call waits for your OK by default.

  4. 04

    Delete the lost ones

    delete_booking removes a booking for a lost project. It also waits for your OK, and the agent never deletes a booking that has other resources on it without saying so.

  5. 05

    Check for approvals

    If the account uses the Approval Workflow, a confirmed booking may come back as pending. The agent reports it as waiting for an approver instead of calling it confirmed.

What you get back

Example data

Tentative bookings next week: 7
Confirmed 3 (Website Redesign, Acme)
Deleted 2 (Brand Refresh, lost)
Left for you 2: Pitch Prep (no project), Q4 Retainer (not in your list)
Pending approval: 1

Other ways to ask

  • Every Friday, list tentative bookings for the next two weeks grouped by project, and change nothing.
  • Delete tentative bookings for Brand Refresh across all of November.
  • Confirm all tentative bookings booked by me for the Acme client this month.

What Resource Guru allows, and what to know first

  • A tentative booking does not take up availability, so it never causes a clash until it is confirmed.
  • On the Dashboard a tentative booking is shown only to the booker, and a confirmed one to both the booker and the booked person.
  • Tentative bookings do not require approval, but a non-approver who confirms one sends it to the approvers.
  • Tentative is different from the waiting list: a waiting list booking is confirmed work that has not found free time.

update_booking and delete_booking ask for your OK by default. To run it weekly without you, switch confirmation off for those tools in your dashboard.

Sources: Resource Guru Help: Create Bookings · Resource Guru blog: Introducing our MCP server · Resource Guru API documentation: Create booking

Call update_booking from a script

curl

curl -X PATCH https://cotlet.dev/api/v1/resource-guru/bookings/48213021 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tentative":false}'

Example response

{
  "id": 48213021,
  "resource_ids": [
    18211,
    18214
  ],
  "start_date": "2026-11-02",
  "end_date": "2026-11-06",
  "minutes_per_day": 240,
  "project_id": 703110,
  "tentative": false,
  "approval_state": "approved",
  "waiting": false
}

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

Schedule it in n8n, Make, Zapier or cron

Resource Guru tools this automation uses

Cotlet Resource Guru tools used to confirm or delete tentative Resource Guru bookings
Tool Parameters
list_bookings start_date, end_date, resource_ids, approval_state, waiting
update_booking booking_id, start_date, end_date, minutes_per_day, resource_ids, project_id, tentative, clash_resolution
delete_booking booking_id
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