Sling
HRConnect AI agents to Sling by Toast, an employee shift scheduling and workforce management platform. Agents look up users and schedules, pull roster reports, and create and publish shifts so staffing gaps get filled without spreadsheet juggling.
What This Integration Enables
Sling, now part of Toast, is built for hourly shift work in restaurants, retail, and other places where the schedule is the operation. The connector's most important design detail is one that most scheduling APIs do not bother with. Create Shift produces a draft. Nobody sees it. Publish Shift is a separate call, and publishing is what makes the shift visible to assigned staff and what fires Sling's notifications. The gap between those two calls is where a human belongs, and Sling built it for you.
FlowRunner agents work with four kinds of object here. Users are the employees, returned by List Users with name, email, role, and status, or by Get Directory when you only need identifiers to resolve names to IDs. Groups are how Sling models locations, positions, and departments, all in one list distinguished by a type field, which is where the location and position IDs required by Create Shift come from. Get Organization returns the organization's own configuration including its time zone, which matters more than it sounds when every scheduling call takes ISO 8601 timestamps. And the schedule itself is read two ways: Get User Calendar for one person's shifts and events over a range, and Get Roster Report for who is scheduled across the organization over a range.
Two setup facts are worth stating plainly rather than discovering later. First, the authorization token is harvested from your browser. Sling's login endpoint is protected by CAPTCHA, so the practical method is to sign in at the Sling web app, open the network tab in your browser developer tools, and copy the entire Authorization header value from a request to the Sling API. Browser tokens typically stay valid for weeks or months, which means this connection will eventually need re-establishing, and a flow that quietly stops filling shifts is worse than one that fails loudly. Build the alert. Second, the token inherits the permissions of the account it came from. An administrator token sees the whole organization and an employee token sees only their own data, so the connection you create decides the blast radius before any human-in-the-loop step does.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The 6am Callout
Someone calls out two hours before opening. The agent reads Get Roster Report for the day to see the shape of the shift and who is already on it, resolves the position and location IDs with List Groups, and builds a candidate list from List Users. For each candidate it runs Get User Calendar across the week to rule out anyone already working that day and to count the hours they are scheduled for. It creates the replacement shift with Create Shift, which Sling holds as a draft, and puts the whole picture in front of the manager in Slack: the gap, the ranked candidates, each one's scheduled hours this week, and who was excluded and why. The manager picks. The agent publishes. What used to be twenty minutes of phone calls becomes one decision.
Next Week Built as a Draft
Forecast demand arrives from the point of sale system on a weekly cadence. The agent reads the current plan with Get Roster Report, resolves every location and position with List Groups, and lays the week out with Create Shift, leaving high volume slots unassigned as open shifts that employees can claim. None of it is visible yet. The scheduling manager reviews the draft week, adjusts, and approves. A second pass runs Publish Shift across the approved shifts and the roster is mirrored into Google Sheets for the labor cost review. The draft state means an incorrect plan is corrected quietly rather than retracted publicly.
Roster Exported Where Payroll Can Read It
At the end of each pay period the agent runs Get Roster Report across the range, joins each scheduled shift to a person with Get Directory, and writes the result to the payroll workbook alongside the actual hours from the time system. Discrepancies between scheduled and worked hours are flagged for a person rather than resolved automatically, because a scheduled shift and a worked shift differing is a fact about what happened, not an error to be corrected. Sling exposes no webhooks, so this runs on a schedule, as does any change detection built on Get User Calendar or Get Roster Report.
Human-in-Loop Highlight
Publish Shift is the only irreversible thing this connector does, and it is irreversible in a very specific way: there is no unpublish or delete operation in the action list. Once published, the shift is visible to the assigned employee and Sling has sent its notification. A person has now been told they are working Saturday. Undoing that means a manager writing a message, not an API call. So the agent stops at the draft. The message reads: "Sunday 11:00 to 19:00, Line Cook, Downtown. Alex Rivera is available and would be at 32 hours for the week. Dana Cole is available and would be at 41. Priya Shah is already on Sunday morning. Publish to Alex, publish as an open shift, or hold?" The manager taps one. The agent publishes exactly that. This is what Orchestration as a Service means at the level of a single shift: the agent does the gathering, the ranking, and the writing, and the one call that reaches a person's weekend waits for a person to make it.
Agent Capabilities
8 actionsUsers and Groups
3- List Users Return every user in the organization with name, email, role, and status. Results are scoped to the authenticated account's permissions, so an administrator token sees all users and an employee token sees a limited view.
- Get Directory Return a concise list of users and groups with just IDs, names, and types. Used when you only need to resolve names to IDs rather than pull full records.
- List Groups Return all groups. Sling models locations, positions, and departments as groups distinguished by a type field, and this is where the IDs required by Create Shift come from.
Organization
1- Get Organization Return organization details including name, time zone, and configuration. Worth reading once per flow, because every scheduling call works in ISO 8601 timestamps.
Scheduling
3- Get User Calendar Return one user's shifts and calendar events across a date range, including both published and unpublished shifts visible to the authenticated account. Used to check conflicts and count already scheduled hours.
- Create Shift Create a shift for a location and position, optionally assigned to a user, or left unassigned to create an open shift employees can claim. New shifts are created as drafts.
- Publish Shift Publish an existing shift so it becomes visible to assigned staff and triggers Sling's notifications. This is the call that reaches a person, and there is no unpublish operation to reverse it.
Reporting
1- Get Roster Report Return the roster of scheduled shifts across the organization for a date range. Used for coverage checks, payroll exports, and summarizing who is scheduled to work.
Frequently Asked Questions
What can FlowRunner do with Sling?
FlowRunner agents can run List Users, Get Directory, and List Groups in Sling, plus 5 more actions.
Does connecting Sling to FlowRunner require OAuth?
No. Sling connects to FlowRunner with an API key, no OAuth flow required.
Can Sling trigger a FlowRunner workflow automatically?
Sling doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Sling
$100 in credits. No card required. Connect in minutes.