How-to guide
Use Shuffl with Rippling
Connect Rippling to keep People current and sign everyone in, 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 promptHide the prompt
Help me with "Use Shuffl with Rippling" in my Shuffl workspace. 1. Read the guide: https://shuffl.ai/docs/markdown/rippling 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 Rippling to People; Sign in with Rippling. 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 Rippling does in Shuffl
Rippling runs HR, IT and payroll in one place. Connect a token to keep People current and let Mello tell each person their time-off balance. People can sign in with Rippling too.
You need to be a Shuffl workspace administrator, with an administrator in Rippling for the steps there.
Connect Rippling to People
- In Shuffl, open People, then the Sync tab. Under Add a source, choose Connect on Rippling.
- In Rippling, open Tools → Developer → API Tokens and create a token.
- Select the read scopes companies.read, departments.read, teams.read, users.read, workers.read and finish creating it.
- Paste the token into Shuffl. Shuffl checks it against your company and workers before saving it. Rippling expires a token unused for 30 days, so keep syncing on.
- Choose Connect and sync. The first sync runs straight away and says how many people were new or linked.
- Review the new people in People and enable access for those who should use Shuffl. A sync never turns access on.
What comes in
Shuffl reads Rippling once a day. Sync now on its card reads it at once. Shuffl only reads; it never changes anything in Rippling.
Rippling’s values replace People’s on every read, so fix a wrong title or manager in Rippling. A blank keeps what People has.
From Rippling into Shuffl
- Everyone, with names and work emails
- Job titles
- Managers
- Departments
- Teams and groups, the ones you choose
- Start dates
- Leavers
- Each person’s own time-off balances
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.
- Teams you bring in become synced groups for Pulse questions, automations, Connections and messages.
- 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 Rippling’s policy names.
- Mello knows each person’s title, manager and department when it answers.
Sign in with Rippling
- In Shuffl, open Settings → Workspace → Integrations → Single sign-on, choose Add connection and pick SAML. Keep the values it shows open.
- In Rippling, open App Shop, choose Create New App, and set it up with SAML single sign-on.
- Paste the ACS URL and entity ID. Under advanced settings, turn on SP-initiated login and paste the login URL, so people can start from Shuffl and from Rippling.
- Send the work email as the NameID, sign the assertion with SHA-256, then give the app to the people or groups who should sign in.
- Copy the IdP metadata XML and paste it into Shuffl.
- Add the DNS TXT record the connection shows at your DNS provider, then choose Check DNS record until it reads Verified.
- In a private window, choose Sign in with SSO with a work email that is in People with access enabled.
Single sign-on proves who someone is; People still decides who gets in. Set up People first, and password sign-in keeps working while you test.
Good to know
Rippling expires a token unused for 30 days. Keep Sync connected; the daily read keeps it alive.
Add leave-balances.read to the token if you want Mello to answer time-off balance questions.
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, Rippling refused Shuffl’s key or sign-in. Create a new one in Rippling 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.