From a search result to a candidate, without a copy paste
Sourcing on GitHub and tracking in an ATS are two tools that rarely talk. The gap is usually filled by hand: open the profile, copy the name, the email, the GitHub link, paste them into a new candidate, then try to remember why this person looked good.
StarHunt puts an Ashby button on every profile card. One click creates the candidate, attaches the evidence, and leaves you in the search you were running.
Two minutes, once
Create an API key in Ashby
Open Admin, then API Keys. Create a key, name it StarHunt, and grant candidatesWrite.
Then add read on jobs, interview plans and hiring process metadata. Those three let you file a profile under a role, at the stage you choose, credited to StarHunt. Skip them and the integration still works, candidates simply arrive unassigned.
Copy the key. Ashby shows it once.
Paste it into StarHunt
In StarHunt, open Settings and find Ashby under Integrations. Paste the key and press Connect.
The key is checked against Ashby before it is saved. If a permission is missing, Ashby says which one, and the message is shown to you word for word.
Send someone
Run a search. Every card now carries an Ashby button. One click creates the candidate. If your key can read jobs, the chevron next to it lists your open roles.
Once sent, the button turns into a link to the candidate in Ashby.
One permission is enough
| Permission | Needed | What it allows |
|---|---|---|
candidatesWrite | Required | Create the candidate, attach the evidence note, add them to a job. |
| Jobs, read | Recommended | Lists your open roles, so a profile can be filed under one instead of landing in a common bin. |
| Interview plans, read | Recommended | Lists the stages of that role's funnel, so you choose where the person enters. |
| Hiring process metadata, read | Recommended | Lists your sources, so the candidate is credited to StarHunt and shows up in your reporting. |
Nothing else is requested, and nothing else would be used. Note what is not in that list: no read permission on candidates. The three reads cover your hiring configuration, never the people in it.
What StarHunt can and cannot see
| Action | StarHunt |
|---|---|
| Create a candidate | Yes |
| Attach a note to that candidate | Yes |
| Add that candidate to a job you pick | Yes |
| List your open jobs and their stages | Only if you grant it |
| List your sources, to credit itself | Only if you grant it |
| Read your existing candidates | Never |
| Read applications, pipelines or feedback | Never |
| Change or delete anything you already have | Never |
The line is not read against write, it is configuration against people. StarHunt reads how your hiring is set up, your roles, their stages, your sources, so it can put someone in the right place. It reads none of the people in it, and every write creates something new rather than touching what was already there.
What lands in Ashby
The candidate carries their name, the public email if they published one, and their GitHub and LinkedIn as social links. Attached to them, a note with the evidence:
- The languages they actually ship in, read from their own repositories, not from a skills list they wrote about themselves.
- Their most starred project, linked, with its star count.
- The reference repositories they contribute to, linked.
- Their last push, so you know whether you are looking at someone active or someone who stopped four years ago.
- Whether they signal open to work on GitHub.
Everything in that note is public GitHub data, and every claim is a link someone can check.
Ashby integration, answered
Can StarHunt read my Ashby candidates?
No. StarHunt reads how your hiring is configured, your open roles, their stages and your source list, so it can file someone in the right place. It never reads the people: no candidate, no application, no interview feedback. And every write creates something new, none touches what was already there.
What permissions does the API key need?
candidatesWrite is the only one that is strictly required. Read on jobs, interview plans and hiring process metadata is recommended: it is what lets you file a profile under a role, at the stage you pick, credited to StarHunt. None of the four can read a candidate.
Where is my Ashby key stored?
Encrypted before it reaches the database, and never sent back to a browser. StarHunt shows only the last four characters, enough to recognise the right key and not enough to use it. You can revoke it from Ashby at any time and the integration stops immediately.
What does the candidate look like in Ashby?
Name, public email if the person published one, GitHub and LinkedIn as social links, and a note carrying the evidence: the languages they ship in, their most starred project, the reference repositories they contribute to, their last push and whether they signal open to work.
Do I need a paid StarHunt plan?
No. The Ashby integration works on the free plan. The free plan limit is on searches, not on what you do with the profiles you find.
Does it work with Greenhouse or Lever?
Ashby is the first ATS StarHunt connects to. The next ones work the same way, so tell us which one you use and we will prioritise it.
Connect Ashby
Free to start, no card. Find an engineer, send them to your ATS, keep going.
Open StarHunt →