Resource Guru

Connect AI agents to Resource Guru scheduling. Agents create bookings against resources and projects, check leave, and keep clients and project assignments current so capacity plans reflect reality.

10 actions API key available

Resource Guru website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A statement of work is approved in the CRM with a start date and estimated hours

Create Project sets up the project linked to the client, and List Resources identifies people with the required role

List Leave and List Bookings pull each candidate's absences and existing allocations for the project window

The agent computes who can actually absorb the hours without overallocation or booked leave in the window

The resourcing manager reviews the proposed allocation, the person, the dates, the hours per week, and approves or picks the alternate

Create Booking allocates the approved resource across the date range with the project attached

The schedule change posts to the staffing channel, and the CRM record gets the committed start date

What This Integration Enables

Resource Guru holds the answer to the most contested question in a services business: who is doing what, when. FlowRunner keeps that answer true. Agents mirror people, projects, and clients in from HR and CRM systems, read bookings and leave to compute real availability, and create allocations when work is approved, so the schedule stops lagging reality by a week of unmade updates. The capacity plan becomes a living system fed by the tools where staffing decisions actually originate, and the resourcing manager's role shifts from data entry clerk for the schedule to the person who rules on the allocations that deserve judgment. - Create bookings that allocate people to projects the day the work is approved, with a human confirming the allocation - Check leave and existing bookings before proposing anyone, so conflicts surface before commitments - Sync projects and clients from CRM and project tools so bookings always attribute to the right work - Report scheduled bookings by date range into utilization dashboards and planned-versus-actual reviews

Without FlowRunner

The schedule lives in one person's head Who is free in March is a question only the resourcing manager can answer, from memory, on a good day

Leave surprises the plan A project is staffed in May around someone whose approved vacation in June was in a different system

New work staffed by interruption Every signed deal triggers a hallway negotiation about who gets pulled from what

With FlowRunner

Availability is computed, not recalled Agents cross-reference bookings and leave for any window and surface who can genuinely take the work

Absences are part of the math Leave records join the capacity check automatically, so nobody gets allocated through their own vacation

Staffing proposals arrive ready to approve New work shows up as a concrete allocation with evidence, and the manager's job is judgment, not spreadsheet archaeology

Use Case Scenarios

The signed SOW that arrived staffed

A deal closes with a March start. The agent creates the project against the client record, pulls the design team's bookings and leave for March, and proposes the one designer with three open weeks, flagging that the runner-up has approved leave mid-project. The resourcing manager approves in [Slack](/integrations/slack), Create Booking commits the allocation, and the account team gets a real start date instead of "let me check with resourcing."

Planned versus actual, every Friday

An agent pulls the week's allocations with List Bookings and the same week's tracked hours from [Harvest](/integrations/harvest), then writes the variance per person and project to [Google Sheets](/integrations/google-sheets). Projects burning faster than their plan show up in week two, not at the invoice dispute. The utilization dashboard stops being a quarterly artifact and becomes the Friday agenda.

The leave report that prevents the double-booking

Every Monday, List Leave pulls the next four weeks of approved absences and posts them to the staffing channel alongside the bookings that overlap them. The month a senior engineer's parental leave was going to collide with a go-live gets caught with four weeks of runway, and the re-staffing happens as planning instead of crisis.

Human-in-Loop Highlight

Create Booking spends the only inventory a services business has: a person's days. The moment a booking lands, Resource Guru's availability math treats those hours as gone, downstream staffing decisions build on top of it, and the person's calendar fills with committed work. A wrong booking is expensive in a way that outlasts its correction, because other allocations were made around it while it stood, and unwinding a chain of staffing decisions costs more than any of the individual edits. Doubly so when the agent proposing the booking is working from a stale read or an ambiguous name match. So allocation is proposed by agents and committed by people: the workflow presents the resource, the date range, the weekly hours, and the conflicts it already checked, and the resourcing manager approves before Create Booking runs. Create Resource sits behind the same gate when an email is attached, because that field can send a real person an invitation to the account.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Resources

List Resources Lists active bookable resources, people, meeting rooms, and equipment, with limit and offset pagination. The discovery step behind every allocation proposal.
Get Resource Retrieves one resource's full profile by ID: name, email, resource type, color, and bookable status.
Create Resource Creates a resource, typically a person, with a full name and optional email. Supplying an email may send an invitation to join the account, which is why this call passes the human gate.

Projects and Clients

List Projects Lists projects, the grouping layer that links bookings to client work, paginated. Used to resolve project IDs before booking.
Create Project Creates a project, optionally linked to a client, so new work has a home before allocations begin.
List Clients Lists the clients that projects and bookings attribute to, paginated. The mapping step for CRM sync workflows.

Bookings

List Bookings Lists resource allocations within a date range, optionally scoped to one resource, with ISO 8601 dates. The read behind availability math and utilization reporting.
Get Booking Retrieves one booking's full allocation detail: resource, project, client, date range, duration, and notes.
Create Booking Allocates a resource over a date range with a duration in minutes, optionally attached to a project or client and a start time for time-specific bookings. The commitment operation this page's approval gate governs.

Leave

List Leave Lists time-off records, vacation, sick days, and other absences, filterable by date range. The input that keeps capacity plans honest about who is actually there.

Frequently Asked Questions

What can FlowRunner do with Resource Guru?

FlowRunner agents can run List Resources, Get Resource, and Create Resource in Resource Guru, plus 7 more actions.

Does connecting Resource Guru to FlowRunner require OAuth?

No. Resource Guru connects to FlowRunner with an API key, no OAuth flow required.

Can Resource Guru trigger a FlowRunner workflow automatically?

Resource Guru doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Resource Guru

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us