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 Ashby

Connect Ashby to start joining playbooks from accepted offers, 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 Ashby" in my Shuffl workspace.

1. Read the guide: https://shuffl.ai/docs/markdown/ashby
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 Ashby 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 Ashby does in Shuffl

Ashby is where recruiting happens. Connect it and an accepted offer brings the new hire into People before day one, with their job and start date, and their joining playbook starts on its own.

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

Connect Ashby to People

  1. In Shuffl, open People, then the Sync tab. Under Add a source, choose Connect on Ashby.
  2. In Ashby, open Admin → Integrations → API keys and create a key named Shuffl.
  3. Give it read access to candidates, jobs and offers. Shuffl never reads pay, feedback or scorecards.
  4. For instant updates, open Admin → Integrations → Webhooks, add the webhook address Shuffl shows for Candidate hired and Offer updated, with a secret token.
  5. Paste the key and secret into Shuffl. Shuffl reads your offers before saving anything.
  6. Choose Connect and sync. Accepted offers with a start date in the last two weeks or ahead come in as people who haven’t started.

What comes in

Applicants, rejected candidates and past hires never reach Shuffl. A hire joins someone already in People only when that person hasn’t started yet.

From Ashby into Shuffl

  • Hires from accepted offers, with their personal email
  • Job titles and start dates
  • The hiring manager, recruiter and interviewers
  • Withdrawn offers

From Shuffl into Ashby, when you turn it on

  • A short note when the joining playbook starts, a buddy is set and on day one
  • An “Onboarding in Shuffl” tag on the candidate
  • The offer’s start date, when HR chooses Update on a hire

What it does for HR

In Shuffl

  • The joining playbook starts on its own from the offer’s start date, and moves if the date changes.
  • A withdrawn offer stops the playbook and tells HR. Nothing is sent to the candidate.
  • People the hiring team named become “met while hiring” ties, so intros and buddies start from someone familiar.

Good to know

Shuffl reads offers, applications and candidates only. It never reads pay, feedback, scorecards or interview notes.

Recruiter notes are off until you turn on Write notes in Ashby. The key then needs candidatesWrite, and offersWrite to update a start date.

With your other systems

Connect your HR system too. A hire starts in People from the hiring system; once your HR system lists them, it takes over their record and nobody is listed twice.

If it stops working

When a card reads Needs attention, Ashby refused Shuffl’s key or sign-in. Create a new one in Ashby 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?