Leonar
Recruiting sequencer: build, run and pause email and WhatsApp sequences, enroll candidates and read replies. Also the contacts, companies and project pipelines behind them.
Leonar is a recruiting sequencer: its sequences are your email and WhatsApp outreach campaigns. It also keeps the contacts, companies and project pipelines those sequences run on. From hyreflow you can build a sequence and its steps as a draft, push enriched candidates in and put them on a project's pipeline, and, once you approve, enroll them and start the sequence, or message someone directly. Replies come back into the same conversations.
Free on hyreflow (0 credits): runs on your own Leonar connection. You pay only for the upstream sourcing/enrichment. Leonar's own enrichment (enrich_contact) uses your Leonar enrichment credits.
Connect your Leonar
Takes about two minutes. You need a Leonar account on the V2 app with an active subscription.
Create an API key in Leonar
In the Leonar V2 app (app.leonar.app), open Settings > API and create a new API key. Pick the scopes the key may use: a read-only key is enough to look things up, but building sequences, pushing candidates, moving stages, enrolling in sequences or sending messages needs write scopes. Copy the key: it starts with leo_.
Use a V2 key, not a V1 key
Keys from the old Leonar V1 app start with pk_live_ and do not work with the API. If that is what you have, create a new key in the V2 app as above.
Paste the key into hyreflow
In hyreflow, open Integrations (recruit.hyreflow.ai/dashboard/integrations) and find the Leonar card under Sequencer. Click Connect, paste it into Leonar API key, then click Save and test. You can also run hyreflow byok set leonar.
You're connected
hyreflow checks the key against Leonar straight away by reading your tags. When the card says connected, every Leonar tool runs on your own account.
The key belongs to the Leonar user who created it. Sequence enrollments and messages go out from that user's connected email or WhatsApp accounts, and the key can only do what its scopes allow. Revoking the key in Leonar breaks the connection until you paste a new one.
Each member uses their own key. Because a Leonar key belongs to its user, the owner's key is the workspace key and every member adds their own under Add your key, so the messages they send go out from their own accounts and their notes and tasks show up under their name in Leonar. Until a member adds theirs, Leonar won't run for them. See Personal keys.
If something goes wrong
- "Leonar rejected this key" on Save and test: the key is wrong, was revoked, or is a V1
pk_live_key. Create a new key under Settings > API in the V2 app and paste it again. - A tool fails with
insufficient_scope: the key was created without the scope that tool needs (for example a read-only key trying to add a contact). Create a key with the right scopes and paste it on the Leonar card. billing_requiredorplan_upgrade_required: the Leonar workspace has no active subscription, or the feature is not in its plan. Sort it out in Leonar, then try again.- "Leonar is rate-limiting requests right now": Leonar allows 2,000 requests per hour per user, shared by all of that user's keys. Wait, then try again.
- To disconnect: on hyreflow's Integrations page, open the Leonar card's Manage menu and choose Disconnect (or Remove key), then delete the key under Settings > API in Leonar so it can't be used again.
Capabilities
| Tool | Does | Cost |
|---|---|---|
list_contacts | One page of contacts, optionally filtered (for example by search, company_id, global_status) | Free |
search_contacts | Full-text search over contacts with combined filters (title, company, location, tags, project, sequence) | Free |
get_contact | Fetch a contact with its pipeline entries and active enrollments | Free |
create_contact | Create a contact | Free |
update_contact | Update a contact: only the fields you send change | Free |
list_contact_notes | A contact's notes, optionally for one project | Free |
add_contact_note | Add a note to a contact | Free |
add_contact_tag / remove_contact_tag | Tag or untag a contact (by tag id) | Free |
enrich_contact | Find a contact's work email, personal email or phone (uses your Leonar enrichment credits) | Free on hyreflow |
get_enrichment_status | Check an enrichment you started | Free |
list_companies / get_company | Read companies | Free |
create_company | Create a company | Free |
list_projects / get_project | Read recruiting projects and their pipeline stages | Free |
list_pipeline_entries | The candidates in a project's pipeline, optionally one stage | Free |
add_to_pipeline | Put a contact on a project's pipeline, at a stage or the first one | Free |
get_pipeline_entry / update_pipeline_entry | Read a pipeline entry, or move it to another stage | Free |
list_sequences / get_sequence / list_enrollments | Read outreach sequences and who is enrolled | Free |
create_sequence | Create a sequence as a draft, optionally with its steps and linked to a project. A draft sends nothing | Free |
update_sequence | Rename a draft or paused sequence, or change its priority, owners or sending schedule | Free |
list_sequence_steps / replace_sequence_steps | Read a sequence's steps, or replace them on a draft or paused sequence (steps you leave out are deleted) | Free |
activate_sequence | Start a draft sequence: starts real outreach to everyone enrolled | Free |
pause_sequence / resume_sequence | Pause a sequence, or resume a paused one: resuming continues real outreach | Free |
get_project_sequence | A project's default sequence | Free |
link_project_sequence / set_project_sequence / unlink_project_sequence | Give a project its default sequence (an existing one or a new draft), replace it, or detach it | Free |
enroll_contacts | Enroll contacts in a sequence: starts real outreach | Free |
update_enrollment_variables | Change an enrolled contact's sequence variables (never sends by itself) | Free |
unenroll_contacts | Take contacts out of a sequence | Free |
list_conversations / list_messages | Read email and WhatsApp threads | Free |
send_message | Send an email or WhatsApp message to a contact: sends immediately | Free |
list_tasks / create_task | Read or create tasks | Free |
list_tags | The workspace's tags and their ids | Free |
create_contacts_batch | Create many contacts, paced | Free |
add_to_pipeline_batch | Put many contacts on project pipelines, paced | Free |
Guidance
- Paging: every
list_*takeslimit(1 to 100) andoffset(from 0). A largerlimitis rejected, not clamped. Keep raisingoffsetwhile the response'smeta.has_moreis true. - Search before you create: run
search_contacts(for example bynameandcompany) and update the match withupdate_contactinstead of creating a second record. - Stages are ids, not names: read a project's stages with
get_project, then pass the stage's id asstage_idtoadd_to_pipelineorupdate_pipeline_entry. Without astage_id, a contact lands in the first stage. - Draft and paused sequences send nothing. A new sequence is always a draft. Leonar only lets you edit a sequence, or replace its steps, while it is draft or paused, so pause an active one first. Replacing steps sends the whole list: any existing step you leave out is deleted.
- Sequence variables are the fixed keys
custom_variable_1tocustom_variable_5(at most 2,000 characters each). Any other key is rejected. - Enroll or unenroll at most 500 contacts per call. Leonar skips contacts marked do-not-contact, already in the sequence or active in another one, and tells you how many it skipped.
- Outreach is gated:
activate_sequence,resume_sequence,enroll_contactsandsend_messageeach reach real people from your connected accounts, so each one is refused unless the call carries"confirm": true, and none of them runs in a batch. Your agent shows you what will go out and asks first. A message that fails with a server error is not re-sent automatically, since it may already have gone out. - No delete operation is exposed for any record.
unlink_project_sequenceonly detaches the sequence from the project. - Pilot one record first: create a single contact and check it in Leonar before a bulk push.
hyreflow tools execute leonar create_contact \
--payload '{"payload":{"first_name":"Ada","last_name":"Lovelace","title":"Staff Engineer","emails":[{"email":"[email protected]","type":"work"}]}}'Enriched candidates go straight into outreach: source → enrich → verify → create_contact → add_to_pipeline → the project's sequence (create_sequence as a draft if there is none) → enroll_contacts and activate_sequence once you approve.
Rate limits & bulk writes
Leonar allows 2,000 requests per hour per user, shared by all of that user's keys, so hyreflow paces each key at 30 requests per minute. Two keys of the same Leonar user used at once share that budget and can briefly hit Leonar's limit; hyreflow waits and retries. Use create_contacts_batch and add_to_pipeline_batch for large pushes; at that pace 500 records take about 17 minutes.
See Bulk pushes to ATS / recruiting CRM.