Gusto, reviewed before payroll runs.
Ask what the next payroll looks like, who is on it and what changed since last time, and Cedric proposes the correction or the submission before a person confirms it.
$50 in free credits when you sign up. No card needed.
- Payroll is a deadline with a lot of small questions in front of it, and Gusto holds the answers to all of them.
- Ask in plain words: the pay schedule, the employees and contractors on it with titles and compensation, the hours submitted this period.
- Cedric reviews a payroll run, gross and net pay, taxes and deductions, and pulls past results and payment receipts when someone asks for one.
- New employees or contractors are added and their personal, job and pay information updated from the thread, with the change shown first.
- Submitting payroll or changing pay is confirmed by a person every time, and Gusto's rate limits apply.
What can a Gusto AI agent do?
A Gusto AI agent reads the company record from the conversation. Cedric retrieves company details, locations, departments and pay schedules, and lists employees and contractors with their job titles, compensation and hire or termination dates. It tracks time-off policies, balances and requests, plus submitted hours and time entries, so "has everyone submitted hours for this period" is one question. It also looks up benefits enrollments, deductions and garnishments tied to each worker when a payslip question comes in.
Payroll itself is reviewed before it is touched. Cedric reviews payroll runs, including the pay period, gross and net pay, taxes and deductions, and it can prepare a payroll for submission or pull past payroll results and payment receipts. Submitting a payroll moves real money, so that step, like any change to pay, is confirmed by a person first. It is the finance half of what an operations assistant handles for a small company.
Records change the same way. Cedric adds new employees or contractors and updates their personal, job and pay information, proposing each change before saving. It can also set up notifications so changes to employees, payrolls or company data are reported to the thread automatically. Two things to know: API access to Gusto requires an approved partner or developer arrangement, and requests are rate limited.
Two days before payroll
The run reviewed, one missing timesheet, one correction proposed.
Hannah Lindqvist9:14 AM
@Cedric review the payroll for the period ending 15 September. Is anyone's hours missing, and did Omar's raise from 1 September make it in?
CedricAPP9:15 AM
Payroll for 1 to 15 September, pay date 20 September, 18 employees and 2 contractors, not yet submitted. Hours: 17 of 18 submitted; Lucas Ferreira has no time entries for the period. Omar Haddad's compensation still shows the old annual amount (CHF 84,000), so the raise to CHF 90,000 effective 1 September is not reflected. Proposed: update Omar's compensation to CHF 90,000 effective 1 September so the run recalculates. I have not prepared or submitted the payroll; Lucas's hours need to come in first.
Listed
Employees and contractors with titles, compensation and hire dates, plus locations, departments and pay schedules.
Reviewed
A payroll run's pay period, gross and net pay, taxes and deductions, and past results or payment receipts when asked.
Updated
A worker added or their personal, job or pay information changed, and a payroll prepared for submission, confirmed by a person first.
Connect Gusto in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Gusto from the dashboard
Open the Integrations page and sign in with Gusto on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what does the next payroll run look like?". You describe the outcome; Cedric picks the Gusto actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Gusto into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
Payroll from Gusto and collected revenue from Stripe are the two lines a small company checks together. Ask Cedric for both for the month and it can put them in a Google Sheets tab, which is where the weekly report reads from.
A new hire's paperwork arrives through Gmail and the start date sits in Google Calendar. Ask Cedric to add the employee to Gusto with the title, compensation and start date from the thread, and it proposes the record with every field shown before saving.
Where the limits are
Gusto is a catalog connection, not a built-in playbook. Cedric works from what the Gusto connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
Submitting payroll and changing pay are confirmed by a person. Cedric prepares the run or the correction and shows the worker, the amount and the effective date; nothing moves until someone says yes.
Access depends on Gusto's partner arrangement. API access requires an approved partner or developer arrangement on Gusto's side, and requests are rate limited, so a long history is paged rather than pulled in one go.
Cedric sees what the Gusto connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. Gusto is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on Gusto's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
No. It can review the run, find what is missing or wrong, and prepare it for submission, but submitting a payroll is confirmed by a person every time. The same applies to any change to someone's pay.
It can read the payroll result for that person, including gross and net pay, taxes, deductions and any benefits enrollment or garnishment behind a line, and pull the payment receipt. It sees what the connected account can see in Gusto, and no more.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect Gusto in a minute.
Ask what the next payroll looks like, then see what it catches before you submit.
100K credits ($50) on sign up. No card needed.