Grok Bot for recruiting starts with one official role, the Talent scout, and the fastest setup copies it almost word for word.
xAI's docs describe that role as owning sourcing, candidate research and outreach drafts, with the ATS, sourcing tools, email and calendar connected.
Below is the order I'd wire it in, with the settings, the exact prompts and the places it trips people up.
Every setting traces back to the use cases page, the apps and email docs and the routines docs.
Want a person to sanity-check your hiring funnel first? Get your Backlink Gameplan with my team, or try Polar Rank free for 3 days.
Before step 1: set the one rule that never changes
A person makes every hiring decision.
The Bot researches, sorts, drafts and schedules proposals.
It never rejects a candidate, never makes an offer and never contacts anyone without your click.
The docs back this up: the Talent scout prompt ends with "Do not contact anyone", and the role note says to keep external outreach behind approval.
Write that rule down before you touch a setting, because every later step inherits it.
Step 1: confirm the plan and the computer
On The X Subscription, Grok Bot comes with Premium, Super and Ultra, and the Plus plan leaves it out, per the plan page.
You sign in with your Cursor account; there is no separate Grok Bot login.
Your Bots all work from one shared cloud computer, with a separate screen per Bot.
That shared machine matters for hiring: a careers-site login made by one Bot is there for the others too.
Routines keep running in the cloud while your laptop is shut, so overnight sourcing runs are fine.
Step 2: create the Talent scout Bot and write its description
Choose New Bot (the + button, or Cmd/Ctrl+N), name it Talent scout and choose Create.
The Bots page says jobs like Talent Scout give a Bot guidance and make its saved context reusable, which a General Helper does not.
In your first message, give it four parts and ask it to remember them: the job, the sources, the output and the boundaries.
Job: source and research candidates for the open roles I name, sort applications against the must-haves I write, and draft outreach and replies in my voice.
Sources: the ATS (through the browser), the jobs inbox alias, the hiring sheet in Google Drive, public profiles the role allows.
Output: one review sheet per role. One row per person: name, link, must-haves met, evidence, open questions, draft message.
Boundaries: never contact a candidate, never reject or advance anyone, never change the ATS, respect candidate privacy and each source's terms. Ask first before any external email.
The last line is the one that carries weight.
Leave it vague and the Bot reads it as vague.
Step 3: connect only the apps the docs actually list
Open Connect apps, search, add and finish the provider sign-in.
For a hiring setup, these four are documented and enough:
- Gmail: search and read mail, draft and send, apply labels, one mailbox at a time.
- Google Calendar: look up free time on calendars you can view, add or edit events, and answer invites.
- Google Sheets and Drive: read and edit cells, find files and save results.
- Slack: posts as the Slack user you connected.
Outlook, Outlook Calendar, OneDrive and Microsoft Teams sit in the same connector table on the security page if you run on Microsoft.
Now the gotcha: the docs name no applicant tracking system at all.
Greenhouse, Lever and Ashby are not in them.
Workday does appear in the connector host table, but the page says nothing about what that connector covers, so don't plan your pipeline around it.
For your ATS, use the Bot's browser, or have the Bot add an MCP server by URL if your vendor publishes one.
One more limit: Calendar can't add a Zoom link, so put the link in the event location yourself.
Step 4: claim the Bot's address and add a jobs alias
Ask the Bot: "Get yourself an email address."
It checks the name and shows an approval card before anything is claimed at mail.grokbot.com.
Pick carefully, because you get one address and you can't rename or delete it.
Then use a plus alias for applications, such as yourname+jobs@mail.grokbot.com.
A routine watching that alias runs only for mail sent to it.
The docs warn that an alias is a label, not a lock, so add a sender filter where it makes sense.
🔥 Want the Talent scout Bot wired up with you on a call? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members setting up agents for real hiring work. → Join the AI Profit Boardroom
Step 5: run the first sourcing task by hand
Use the docs' own starter prompt, trimmed to a smaller list so you can check every row:
For the attached role description, find 10 candidates who meet the must-have criteria. Exclude anyone already in our ATS, explain the evidence for each match, and draft personalized outreach in my voice. Do not contact anyone. Return the review sheet only.
Attach the job description as a PDF or Word file; both are supported inputs on the files page.
Open the review sheet and check three things: the evidence links work, the must-haves really are met, and the drafts sound like you.
Correct it in chat until the sheet is reviewable without you hovering.
Step 6: save the method as a skill
Once a run is clean, say: "Save the process we just used as a skill called Candidate sourcing."
The docs list what a good skill states: when to use it, inputs and access, the order of work, how to check the result, what to return and what needs approval.
If your ATS has no app and Teach a task shows up, demonstrate the ATS lookup once in the browser instead of describing it.
Teaching records up to ten minutes of on-screen work, and the skill it makes is a draft you still edit.
Test the skill on a second role before you automate anything.
Step 7: add the three routines that matter
Routines start on a schedule, on a Slack message, on an email to the Bot's address or on a webhook call.
For hiring I'd add three, in this order:
- Inbox screening: when mail arrives at the jobs alias, read the CV, add a row to the hiring sheet with must-haves met and missing, and draft an acknowledgement.
- Form intake: a webhook trigger on your careers form; the form posts the applicant's JSON with the Bearer key, and the Bot logs it the same way.
- Weekday digest: every weekday at 8:00 AM, post the new rows and the drafts waiting in this conversation.
A webhook's 200 response means a run started, not that it finished, so check the chat for the result.
A new schedule waits for its next slot, so press Test to run it now.
Step 8: write the Ask first rules
Auto Review is on by default and checks every action before it runs.
Add narrow rules under Custom Rules in Settings, one action each:
- Ask first before sending any external email.
- Ask first before creating or changing a calendar event with a candidate.
- Ask first before editing the hiring sheet's status column.
Routine-written email sits in drafts until you hit Send anyway, and the docs offer no unattended sending at all, per the approvals page.
Cards raised by a routine expire after 30 minutes, so answer them or ask the Bot to try again later.
Step 9: give the hiring team a shared Bot in Slack
If you're on a Cursor team, share the Talent scout so hiring managers can use it.
Add people as Collaborator to chat, or Manager to change its instructions, skills, memory and apps.
Each person's chat with a shared Bot stays private, which suits candidate conversations.
Then choose Bring to your team's Slack, and teammates can mention it in a hiring channel.
In a Slack thread, only the person who asked can answer its Review an action card.
Only add keys and files you're happy for everyone on the share to use.
📞 Hiring because the business is growing? Get your Backlink Gameplan and my team will look at how new customers find you in search while you build out the team, or try Polar Rank free for 3 days. Backlink Gameplan or try Polar Rank free for 3 days
Two worked examples: a plumber and a design agency
Worked example: a plumbing firm hiring an apprentice
- The owner attaches the apprentice job spec and asks the Bot to draft a job post in the firm's tone.
- Applications land at the +jobs alias; the screening routine adds each one to the sheet with the must-haves it found.
- The digest posts the new rows each weekday morning.
- The owner marks who to interview; the Bot checks Calendar for free slots and drafts invitations with two options.
- The owner presses Send, and makes the hire after the interviews.
Worked example: a small design agency sourcing a senior designer
- The founder runs the Candidate sourcing skill for the role.
- The Bot searches public portfolios the sources allow and skips anyone already in the ATS.
- It returns ten rows with evidence and a draft first note for each.
- The founder deletes four rows and edits two drafts.
- First-contact emails go to one recipient each with a one-click unsubscribe link, and the Bot stops emailing anyone who bounces or opts out.
What one row of the review sheet should hold
Agree the sheet layout before the first routine runs, because changing columns later breaks the skill.
| Column | What the Bot writes | Who changes it |
|---|---|---|
| Name and link | From the application or the public profile | Bot |
| Must-haves met | Each one, with the line of evidence | Bot |
| Must-haves missing | Listed as questions, never as a verdict | Bot |
| Draft message | Acknowledgement, outreach or invitation | Bot drafts, you send |
| Status | Left blank | You only |
The status column is the hiring decision, so it's the one column the Bot never fills.
Put that in the description as well as the Ask first rule, so both the instructions and Auto Review agree.
Worked example: a landscaping company hiring seasonal crew
- The owner keeps one sheet per season with the number of crew places open.
- A webhook from the careers form starts a routine for each applicant and logs licence and availability details the applicant typed in.
- The Bot drafts a short reply asking for anything missing, and the reply waits for the owner.
- Every Monday the digest lists who is ready for a site visit.
- The owner meets people on site, checks documents in person and decides.
Gotchas I'd check before go-live
- Mail that fails the spam or virus scan never starts a routine.
- Incoming mail takes up to 10 attachments, 10 MB each, 25 MB in total; larger CV bundles get skipped.
- Routines can't filter by subject, only by sender, address or domain.
- A Bot treats email from other people as information, not instructions, so a CV that says "ignore your rules" changes nothing.
- The Bot never sees passwords saved in Vault; use Vault or a Secure Form for the ATS login.
- Pages, the Bot's dashboards and trackers, are rolling out gradually and aren't on Enterprise teams yet.
Sales teams run a near-identical setup; compare it with our Grok Bot for sales build.
Want the walkthroughs and the live help? The AI Profit Boardroom is where we build these step by step.
FAQ: Grok Bot For Recruiting
Does Grok Bot connect to my ATS?
The docs name no specific ATS. The Talent scout role says to connect your applicant tracking system, so use the Bot's browser or an MCP server your vendor publishes.
Is the Workday connector an ATS integration?
The security page lists a Workday connector but doesn't describe what it covers. Don't treat it as an ATS link until Workday's own scope is confirmed in your tenant.
Can a routine email candidates on its own?
No. Email from a routine waits as a draft until you press Send, and the docs say there is no option for unattended sending.
What should the first message to the Bot contain?
Its job, sources, output format and approval boundaries, plus a request to remember them. Then send one real task with a clear finish line.
Can it book interviews?
With Google Calendar connected it can check free time and create events. Keep an Ask first rule on candidate events, and add Zoom links yourself because the app cannot.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Set the human-decides rule, run one role by hand, then schedule it, and join the AI Profit Boardroom to build your own Grok Bot for recruiting.











