AES-256-GCM Secure Encryption
All private keys submitted to the Providers endpoint are encrypted in transit and stored encrypted in the database using AES-256-GCM encryption. The encryption key is derived from the server’s privatePROVIDER_ENCRYPTION_KEY. Stored values are only decrypted in memory on workers during active worker dispatches.
Endpoints
1. List Provider Configs
- Method & Path:
GET /api/v1/providers - Auth: Bearer Token (Dashboard)
re_••••••1234) to prevent exposing raw keys in the dashboard.
2. Save Provider Config
- Method & Path:
POST /api/v1/providers - Auth: Bearer Token (Dashboard)
Request Body (Email/Resend)
3. Test Connection
- Method & Path:
POST /api/v1/providers/:channel/test - Auth: Bearer Token (Dashboard)
Response
4. Delete Provider Config
- Method & Path:
DELETE /api/v1/providers/:channel - Auth: Bearer Token (Dashboard)
Resend Integration Walkthrough
Follow these steps to set up Resend as your email provider:1
Generate Resend API Key
Log into your Resend account, navigate to API Keys, and generate a new key.
2
Verify Your Domain (Recommended)
By default, unverified free accounts can only send from
onboarding@resend.dev and can only send to the email address that registered the account. To send to arbitrary recipients, navigate to Domains on Resend and verify your custom domain.3
Configure on Notifyflow
Under Providers in the dashboard, select Email Delivery -> Resend and save your key:
apiKey: your Resend API Key.fromEmail: set toalerts@yourdomain.com(must be a subdomain or domain verified in Resend) oronboarding@resend.devif testing in sandbox mode.fromName: name shown on emails (e.g.,Acme Corp).
4
Run a Connection Test
Click the Play icon to test the connection. This immediately delivers a test email to your registered account email.