Getting started

Connect a channel

Connections are your own accounts, not a sending service. Mail leaves your mailbox and lands in your Sent folder.

Two consequences follow, and both are structural. Deliverability is yours, because the sending reputation is your domain’s. And a send has no marginal vendor cost to meter, because connections are billed per account rather than per message — which is why connections are a separate line item on every plan.

Google and Microsoft

Both go to their own consent screens, driven by our OAuth client. The only third-party page you see belongs to the company whose mailbox you are handing over. There is no vendor-hosted wizard, and not as a fallback either: a provider we cannot run consent for is not offered, and the mailbox connects over IMAP instead.

A credential form inside the product. LinkedIn offers no OAuth, so the password passes through our servers — forwarded within one request, never persisted, never logged. Connecting LinkedIn is what makes sourcing possible: it is both the search surface and the send surface.

IMAP and SMTP

Every field is required on every request — the connection API has no autodetection. Presets cover the common hosts; there is no “advanced” toggle hiding the rest.

Fields

json

{
  "imap_host": "imap.fastmail.com",
  "imap_port": 993,
  "imap_user": "you@example.com",
  "imap_password": "<app password>",
  "smtp_host": "smtp.fastmail.com",
  "smtp_port": 465,
  "smtp_user": "you@example.com",
  "smtp_password": "<app password>"
}