hyreflow docshyreflow docsDocumentation
Integrations

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

ToolDoesCost
search_personsFind people by email, name, LinkedIn URL, job, stage, company, owner and moreFree
get_personFetch a person by id, with the sections you ask forFree
create_personCreate a person (or match and update the one with the same LinkedIn URL)Free
update_personPartial update of a person; job_id adds them to that jobFree
create_person_activityAdd a note (or another activity type) to a personFree
list_person_activitiesA person's activity timelineFree
list_client_contacts / get_client_contactRead client contactsFree
create_client_contactMake an existing person a client contact of a companyFree
update_client_contactChange a client contact's status or ownersFree
search_companies / get_companyRead companiesFree
create_companyCreate a company (or return the one it matches)Free
update_companyPartial update of a companyFree
create_company_activityAdd a note to a companyFree
search_jobs / get_jobRead jobs, including a job's pipeline stagesFree
create_job / update_jobCreate or change a jobFree
create_job_activityAdd a note to a jobFree
list_job_candidates / search_candidates / get_candidateRead who is on which job, at which stageFree
update_candidate_stageMove a candidate to another stageFree
search_tasks / create_task / update_taskRead and write tasksFree
list_team_members, list_custom_fields, list_job_statuses, list_pipeline_stages, list_rejection_reasons, list_client_contact_statuses, list_company_statusesLook up the ids other tools takeFree
create_people_batch / update_candidate_stage_batchCreate many people or move many candidates, pacedFree

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_id when you create or update the person. Then read the job's pipeline_stages with get_job and move them with update_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_contact with their id and the company's id. A person can be a client contact of one company only.
  • create_company returns the matching company when one exists (same LinkedIn URL or domain) and leaves its fields as they are. Use update_company to change it.
  • Paging: list and search tools take offset (from 0) and limit (at most 100, or 200 for search_jobs). A larger value is rejected, not clamped. Keep raising offset until it reaches meta.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.