hyreflow
Integrations

Reply.io

Multichannel outreach: email plus LinkedIn steps and calls in one sequence, with an AI-SDR layer. Key gotcha: scope model gates writes, and start_sequence is approval-gated.

Use Reply.io for multichannel outreach activation: resolve or create a sequence, link sending mailboxes, create or import contacts, enroll them, then start sending and monitor results.

Free on hyreflow (0 credits): runs on your own connected Reply.io account. You pay only for the enrichment that fed the contacts.

Capabilities

ToolDoesCost
reply_io_list_sequencesList sequences (resolve a stable sequence ID)Free
reply_io_create_sequenceCreate a sequence (needs a name + at least one step)Free
reply_io_link_email_account_to_sequenceAttach a sending mailbox to a sequenceFree
reply_io_create_contactCreate a contactFree
reply_io_search_contactsFilter contacts by rule, list, or sequenceFree
reply_io_add_contacts_to_sequenceEnroll contacts (batches ≤ 10,000)Free
reply_io_start_sequenceBegin real outbound sendingFree
reply_io_pause_sequencePause a running sequenceFree
reply_io_get_sequence_statsSequence performance for a date windowFree
reply_io_set_contacts_repliedMark a contact replied (finishes them in the sequence)Free
reply_io_list_email_accountsList sending mailboxesFree
reply_io_whoamiConfirm the connected accountFree

Guidance

  • Gate activation behind enrichment/verification: only enroll contacts that have been validated. start_sequence triggers real outbound; confirm mailboxes, sequence content, and contact list first.
  • Resolve sequence IDs from reply_io_list_sequences before any write, or create one — a name-only create_sequence is rejected, it needs at least one step too.
  • Scope model: API keys are scoped domain:verb (e.g. sequences:operate). A key missing that scope can read sequences but can't enroll or start — the most common confusing 403.
  • Bulk caps are hard caps: add_contacts_to_sequence/remove_contacts_from_sequence allow up to 10,000 contact ids; set_contacts_status_in_sequence/set_contacts_replied allow up to 100. Over the cap is rejected, not trimmed.
  • Pagination: top maxes at 1000 and is rejected (not clamped) above that — page with skip.
  • update_contact is PATCH: omitted fields keep their existing value.
  • Stats window is either/or: pass a dateRangePreset or an explicit from/to, never both.
  • Rate limit: stay at/below 100 requests/minute and 3,000 requests/hour per user; reporting/stats endpoints are stricter.
hyreflow tools execute reply_io reply_io_add_contacts_to_sequence \
  --payload '{"sequence_id":777,"contact_ids":[12345,12346]}'

Building a sequence and enrolling contacts is free; start_sequence is the irreversible step. Keep it behind an explicit approval gate, see Campaign Plays.

On this page