Skip to content
shuffl
Get started

Searches the public product guides only. Nothing from a workspace is read, and questions are not saved.

How-to guide

Use Shuffl with HiBob

Connect HiBob to keep People current, and see what Shuffl does with it.

For HR and IT administrators

Have your agent do thisPaste the prompt into Claude Code, Cursor or another agent. It follows this guide over MCP and asks before it changes anything others will see.Show the prompt
Help me with "Use Shuffl with HiBob" in my Shuffl workspace.

1. Read the guide: https://shuffl.ai/docs/markdown/hibob
2. Add Shuffl's MCP server: https://shuffl.ai/api/mcp
   Claude Code: claude mcp add --transport http shuffl https://shuffl.ai/api/mcp
   When the browser opens, choose my workspace and allow the access the guide needs.
3. Work through the steps in order: Connect HiBob to People. Do what you can over MCP and tell me which steps only I can do in the browser or in Slack.

Show me what you will change and who it affects, and wait for my yes before publishing, inviting or sending anything.
On this page

App links open your signed-in workspace. Check the selected workspace before making changes.

What HiBob does in Shuffl

HiBob (Bob) holds your people data. Connect a service user and People follows Bob, with changes as they happen once you add a webhook. Mello can tell each person their time-off balance.

You need to be a Shuffl workspace administrator, with an administrator in HiBob for the steps there.

Connect HiBob to People

  1. In Shuffl, open People, then the Sync tab. Under Add a source, choose Connect on HiBob.
  2. In Bob, open Settings → Integrations → Service users and create one named Shuffl.
  3. Give it a permission group that can view Basic info, Work and Lifecycle for all employees, including former ones.
  4. For instant updates, open Settings → Integrations → Automation → Webhooks, add the webhook address Shuffl shows with the employee events and copy its secret.
  5. Paste the ID, token and secret into Shuffl. Shuffl reads your employees before saving anything.
  6. Choose Connect and sync. The first sync runs straight away and says how many people were new or linked.
  7. Automatic access is on by default, so eligible active people can use Shuffl after syncing. To approve people yourself, turn it off in the Connect dialog or on the card.

What comes in

Changes arrive as they happen, and Shuffl also reads HiBob once a day. The one thing Shuffl writes to HiBob is a time-off request a person runs from Mello’s card; its Let Mello file requests switch turns that off.

HiBob’s values replace People’s on every read, so fix a wrong title or manager in HiBob. A blank keeps what People has.

From HiBob into Shuffl

  • Everyone, with names and work emails
  • Job titles
  • Managers
  • Departments
  • Start dates
  • Leavers
  • Each person’s own time-off balances
  • Approved time off for Who’s out, dates only

What it does for HR

In Shuffl

  • Start dates start onboarding playbooks on their own, put new hires on Home and drive work anniversaries.
  • Managers fill the org chart, so playbook meet steps, manager to-dos and 30/60/90 plans reach the right person.
  • Departments become department groups, so Pulse, eNPS and Culture compare teams without exposing anyone.
  • Leavers lose access when they leave, and a termination date sets their last day, which can start a leaving playbook.
  • Mello tells each employee their own time-off balance in a private chat, in HiBob’s policy names.
  • Mello files a person’s own time-off request in HiBob as pending, from a card they run; HiBob’s approval flow decides.
  • The approver HiBob names hears about it in Slack, with a link to decide in HiBob.
  • Approved time off in HiBob shows in Who’s out on People and Home, dates only, never the leave type.
  • Mello knows each person’s title, manager and department when it answers.

Good to know

For live changes, add the webhook address Shuffl shows under Automation → Webhooks in Bob and paste Bob’s secret into Webhook secret. Without it Shuffl reads once a day.

An inactive Bob account has its Shuffl access suspended. A termination date sets the person’s last day.

With your other systems

Connect your HR system before an identity provider such as Okta, so it owns start dates, managers and departments. Slack and single sign-on keep names and emails.

If it stops working

When a card reads Needs attention, HiBob refused Shuffl’s key or sign-in. Create a new one in HiBob and connect again; Shuffl replaces the stored one. A failed run changes nobody.

Disconnect stops syncing and deletes the stored key. Everyone stays in People to edit by hand.

Was this guide helpful?