Reply.io

Install corsair and @corsair-dev/replyio, add the Reply.io plugin, and connect with an API key. Then call methods like corsair.replyio.api.contactLists.list() from your app. Corsair keeps each tenant isolated.

Yes. Reply.io requires an API key from your Reply.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Reply.io, GitHub, Notion, Stripe, and the rest. Trigger Reply.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for ai-powered sales engagement platform for contacts, multichannel sequences, email accounts, and sending schedules. Common builds include sync jobs, admin tooling, and agents that call Reply.io APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Reply.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/replyio in the open repo. When Reply.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Reply.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Reply.io data on your behalf.