Skip to content

Start building

Integration · HR and recruiting

AI agents for Homebase

Read Homebase schedules and time: list locations and their employees, list scheduled and open shifts, read timecards.

Actions
7
Read
7
Write
0

Actions

What your agents can do in Homebase

Read Homebase schedules and time: list locations and their employees, list scheduled and open shifts, read timecards (clock-ins and breaks), labor totals by employee and who is clocked in, with the company's Homebase API key. Read only: Homebase's public API does not add or change shifts or time off.

Read 7

Look things up. Nothing changes.

  • List locations

    Lists the account's locations, each with uuid (what the other actions take), name, address fields, phone, time_zone and partner_merchant_id.

  • List a location's employees

    Lists the employees of a location, optionally with archived ones.

  • List shifts

    Lists a location's shifts that start (or end, or were created or changed) between two times, optionally only open shifts.

  • Get a shift

    Reads one shift of a location by ID, optionally with its note, with the same fields as "List shifts".

  • List timecards

    Lists a location's timecards (clock-in to clock-out) between two times, by clock-in time unless another is chosen.

  • Get labor totals by employee

    Totals each employee's labor at a location between two times.

  • Check whether someone is clocked in

    Reads the current time clock status of one employee's job (the job.id from "List a location's employees").

Write 0

Create, change or send.

This tool only reads, so nothing in it changes.

Read only

Every action here only reads, so an agent can look things up in Homebase but cannot change anything there.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Homebase account.

What you enter

  • API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Homebase data

    Ask a question in plain words. The agent can list locations, list a location's employees or list shifts in Homebase, then answers with what it found.

  • 02

    Share what it finds in Slack

    Give one agent Homebase and Slack: it can list locations in Homebase and post a summary to a Slack channel in the same run.

  • 03

    Run it as a workflow step

    Add "List locations" to a workflow, and it runs in Homebase the same way every time, with or without an agent.

FAQ

Homebase and MyDeepAgents

Can MyDeepAgents connect to Homebase?

Yes. The Homebase connector has 7 actions, all of which only read. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Homebase?

Paste an API key from your Homebase account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Homebase without asking?

No. Every Homebase action only reads, so an agent can look things up there but cannot change anything.

Can I use Homebase in workflows as well as agents?

Yes. Every Homebase action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Homebase to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.