Why use it
Some teams already pay an email provider and don’t want two send systems in the app. BYOK connects that provider to the workspace: you still call the Notifique API (/v1/...), and the platform decides who delivers, your external account or internal fallback.
Analogy: you use the same building entrance (Notifique API), but the delivery badge can be from your carrier.
When to use
How it works in practice
- Register the external provider in the workspace (order and activation per channel).
- On send, Notifique tries the external path first (your credentials).
- If it fails → fallback to internal providers (per configuration).
- Telemetry records
EXTERNALvsINTERNAL, sanitized response, and external ID.
Billing
- Every email enqueued on Notifique (BYOK or internal) consumes 1 email credit (or the prepaid email price).
- You still pay the external provider (Resend/SES) for delivery on your account.
- Internal failover does not double-charge the same send (debit already happened at enqueue).
Security
- Credentials encrypted; after saving, API does not return secret in plain text.
- Update = rotate (replace), not “read back”.
Up to two external integrations per channel (limit may evolve, check the product).