Stardex
Recruiting ATS/CRM reads and writes. People (candidates), client contacts, companies, jobs, pipeline stages, notes and tasks.
Use Stardex as the ATS/CRM write target at the end of a recruiting pipeline: push enriched candidates in, put them on a job and move them through its stages, and read jobs, companies and contacts back out.
Free on hyreflow (0 credits): runs on your own Stardex connection. You pay only for the upstream sourcing/enrichment.
Connect your Stardex
Takes about two minutes. Only a Stardex organization admin can create API keys.
Create an API key in Stardex
In Stardex, open Settings > Email & other integrations > API access & Webhooks and click Create key. Give it a name such as "hyreflow".
Choose its permissions
Pick Custom and tick Read and Write for People, Candidates, Jobs, Companies & contacts, Notes & activities, Tasks and Workspace metadata. hyreflow needs no Delete and no Enroll & send. Click Create key and copy it: Stardex shows it only once.
Paste the key into hyreflow
In hyreflow, open Integrations (recruit.hyreflow.ai/dashboard/integrations) and find the Stardex card under Recruiting CRM. Click Connect, paste the API key, then click Save and test. You can also run hyreflow byok set stardex.
You're connected
hyreflow checks the key against Stardex straight away. When the card says connected, every Stardex tool runs on your own account.
A Stardex key belongs to your organization, not to one person, so the whole workspace uses the same key. Notes and tasks written with it have no author unless you name a team member (team_member_id on a note about a person, owner_ids on a task). Notes on companies and jobs always have no author.
If something goes wrong
- A 401 on Save and test: the key is wrong, expired or was revoked or rolled. Create or roll a key in Stardex and paste the new one.
- A tool fails with a 403
INSUFFICIENT_SCOPE: the key lacks the permission that tool needs. Edit the key's permissions in Stardex, then try again. - To disconnect: on hyreflow's Integrations page, open the Stardex card's Manage menu and choose Disconnect (or Remove key), then revoke the key in Stardex so it can't be used again.
Capabilities
| Tool | Does | Cost |
|---|---|---|
search_persons | Find people by email, name, LinkedIn URL, job, stage, company, owner and more | Free |
get_person | Fetch a person by id, with the sections you ask for | Free |
create_person | Create a person (or match and update the one with the same LinkedIn URL) | Free |
update_person | Partial update of a person; job_id adds them to that job | Free |
create_person_activity | Add a note (or another activity type) to a person | Free |
list_person_activities | A person's activity timeline | Free |
list_client_contacts / get_client_contact | Read client contacts | Free |
create_client_contact | Make an existing person a client contact of a company | Free |
update_client_contact | Change a client contact's status or owners | Free |
search_companies / get_company | Read companies | Free |
create_company | Create a company (or return the one it matches) | Free |
update_company | Partial update of a company | Free |
create_company_activity | Add a note to a company | Free |
search_jobs / get_job | Read jobs, including a job's pipeline stages | Free |
create_job / update_job | Create or change a job | Free |
create_job_activity | Add a note to a job | Free |
list_job_candidates / search_candidates / get_candidate | Read who is on which job, at which stage | Free |
update_candidate_stage | Move a candidate to another stage | Free |
search_tasks / create_task / update_task | Read and write tasks | Free |
list_team_members, list_custom_fields, list_job_statuses, list_pipeline_stages, list_rejection_reasons, list_client_contact_statuses, list_company_statuses | Look up the ids other tools take | Free |
create_people_batch / update_candidate_stage_batch | Create many people or move many candidates, paced | Free |
Guidance
- Send a LinkedIn URL when you create a person. Stardex uses it to find an existing person and update them instead of creating a duplicate. Without it, a new person with the same name who also shares an email or phone can be merged into the existing record. Either way you get the existing person's id back.
- Putting someone on a job: pass
job_idwhen you create or update the person. Then read the job'spipeline_stageswithget_joband move them withupdate_candidate_stage, using ids rather than names. A stage move starts the Stardex automations you have set to run on API changes. - Client contacts start as people: create the person, then
create_client_contactwith their id and the company's id. A person can be a client contact of one company only. create_companyreturns the matching company when one exists (same LinkedIn URL or domain) and leaves its fields as they are. Useupdate_companyto change it.- Paging: list and search tools take
offset(from 0) andlimit(at most 100, or 200 forsearch_jobs). A larger value is rejected, not clamped. Keep raisingoffsetuntil it reachesmeta.total. - No delete operation is exposed for any record, and campaigns (which email people) are not covered.
- Pilot one record first: create a single person and check it in Stardex before a bulk push.
hyreflow tools execute stardex create_person \
--payload '{"payload":{"name":"Ada Lovelace","linkedin_url":"https://www.linkedin.com/in/ada-lovelace","work_email":"[email protected]"}}'Enriched candidates land here at the end of the pipeline: source → enrich → verify → create_person with a job_id → update_candidate_stage.
Rate limits & bulk writes
Stardex allows 60 requests per minute per API key, so hyreflow paces Stardex calls at 50 requests per minute. Use create_people_batch for large pushes.
See Bulk pushes to ATS / recruiting CRM.
Spott
Recruiting CRM/ATS: candidates, clients, client contacts, jobs, applications, notes, placements, tasks, opportunities. BYOK; free on hyreflow.
TheirStack
Tech-stack-driven company discovery and tech-filtered job search. Key gotcha: keyword slugs are kebab-case (validate first), and there is no email-provider filter.