Finocket sends outreach on its own included accounts out of the box, with nothing to set up. If you'd rather send from your own provider accounts (your sender identity, your reputation, your provider bill), add your keys under Outreach sending, which Settings → Connected keys links to (it is not a settings row of its own). Consent checks are unchanged either way.
Which providers are ready today?
- Email (ready): Resend and ZeptoMail. Each needs an API key/token and a verified from sender or domain at the provider.
- Your own mailbox over SMTP (ready): send straight from the address you already use, with no email-provider account and no domain to verify. You need your mail server (Gmail and Workspace use
smtp.gmail.comon port 465), your address, and an app password. Your normal password will not work. Google issues one under Security → App passwords, and only after 2-Step Verification is on. Finocket makes a real connection and logs in before saving, so a wrong password is caught on the form rather than when a customer doesn't get an email. - What sending from your own mailbox costs you: your mailbox can't tell Finocket when a message bounces or when someone marks it as spam. The safeguard that pauses sending after a spike in complaints therefore has nothing to watch on this route, so an empty warnings screen means it isn't being measured, not that nothing is wrong. Mailbox providers also cap you: Gmail and Workspace stop somewhere around 2,000 recipients a day. Good for reminders, statements and low-volume follow-ups; use a dedicated email provider for a large campaign.
- Email (listed but coming soon): Amazon SES and SendGrid appear in the list, but they are not wired yet. You can't rely on them for sending today; use Resend, ZeptoMail, your own mailbox, or the included sender.
- WhatsApp (ready): Meta Cloud API (phone-number ID + permanent access token) and 360dialog (API key). Business-initiated messages must use a Meta-approved template.
- SMS (ready): MSG91, Fast2SMS, Twilio and Plivo. Indian routes need a DLT-registered sender ID and template IDs; US routes on Twilio need approved A2P 10DLC registration. Until those are in place, SMS stays queued and is never fired unregistered.
What's the difference between a company key and a personal key?
A company credential, which only the workspace owner can set, applies to everyone in the workspace. A personal credential, which any member can set, overrides the company one for that member's own sending. Set neither and Finocket's included sending applies. This lets a business run one official sender while a field salesperson sends from their own account.
What does bringing a key change, and what doesn't it?
A key only swaps the transport: the account a message physically leaves from. Everything that decides whether a message may go (consent, suppression, quiet hours, template class, jurisdiction rules) runs exactly as before through the single send checkpoint. Your own key never bypasses compliance.
How are my keys protected?
Every credential is encrypted per workspace before it's stored. Plaintext never lands in the database, and a saved key is never shown again. The screen only shows which provider is configured and whether it's verified. To rotate a key, paste a new one over it. When you save, use Save & send test email (email) or Save & verify (WhatsApp/SMS). Only verified credentials are used for real outreach, so a bad key can't silently swallow a campaign.
Related: Email, campaigns and consent, Sending & deliverability.