The email channel — SMTP, Amazon SES and Resend providers, sender domain verification, content fields (MJML/HTML, Liquid), open/click tracking, List-Unsubscribe and inbound feedback webhooks.
The email channel sends transactional and marketing email through the same POST /v1/notifications, campaign and journey flows. For the drag-and-drop editor, see the email editor; to stay out of spam, see deliverability.
Providers
| Provider | Fields (secret ones in italics) | Validation |
|---|---|---|
smtp | host, port, secure (465 TLS / STARTTLS), username, password, sender fields | SMTP EHLO + authentication (verify); private network addresses are rejected and the IP is pinned (SSRF) |
ses | region, access_key_id, secret_access_key, configuration_set, sender fields | GET /v2/email/account (SigV4) |
resend | api_key, webhook_secret (whsec_…, optional), sender fields | GET /domains |
mock | optional from_address, from_name | always valid (simulation) |
Sender fields: from_address (required), from_name, reply_to, postal_address (physical address shown in the footer). API: PUT /v1/apps/{app_id}/channels/email + POST …/validate (admin).
Domain verification: verify your sender domain with the provider; add the provider's include: value to your SPF record, add the CNAME/TXT records it gives you for DKIM, and publish at least a v=DMARC1; p=none DMARC record. Dashboard Channels → Email → Domain (GET /v1/apps/{app_id}/email-deliverability) shows SPF/DKIM/DMARC status live; for the warm-up plan and reputation, see deliverability.
Content fields
| Field | Description |
|---|---|
email_subject | Subject (Liquid). Falls back to headings if missing. |
email_mjml | MJML source (Liquid → MJML compilation). mj-include file access is disabled. |
email_body | Ready-made HTML (Liquid). Used when there is no MJML. |
email_preheader | Inbox preview text (hidden preheader). |
email_from_name, email_from_address, email_reply_to_address | Override the channel defaults. |
disable_email_click_tracking | Links are not rewritten into redirects. |
contents | Becomes the body in a plain template when there is no MJML/HTML. |
template_id | Versioned template; the email_* fields come from the template. |
include_unsubscribed | Transactional email only: unsubscribed addresses are also targeted (bounce/complaint/STOP suppressions still apply). |
For an email-only message, contents is not required; email_subject + email_mjml/email_body is enough. Liquid output in the HTML body is HTML-escaped; for intentional raw HTML, use {{ value | raw }}. {{ unsubscribe_url }} is the delivery-specific unsubscribe link. Preview: POST /v1/apps/{app_id}/templates/{id}/render (channel: "email" → subject, preheader, html, text).
Direct addresses: target.email_to: ["ayse@pushizo.com"] sends to an address without a subscription; an anonymous user + subscription is created.
Tracking and unsubscribe
Every email gets delivery-specific, signed URLs (under the API_URL base):
| URL | Behavior |
|---|---|
GET /t/o/{dlv} | 1×1 GIF; opened on the first request |
GET /t/c/{dlv}?u= | The signature covers the target URL; clicked + 302 (no open redirect) |
GET /t/u/{dlv} | Confirmation page (tr/en, light/dark); GET does not unsubscribe |
POST /t/u/{dlv} | RFC 8058 one-click (List-Unsubscribe=One-Click) and the confirmation form → subscription unsubscribed, suppression unsubscribe_link |
Headers: List-Unsubscribe, List-Unsubscribe-Post: List-Unsubscribe=One-Click, X-HS-Delivery-Id. The plain-text version is generated from the HTML.
Inbound feedback (bounce, complaint, delivery)
URL: Channels → Email → Webhook URL (contains a secret token; rotate it with Regenerate). Format: {API_URL}/hooks/email/{ses|resend|smtp|mock}/{token}.
| Provider | Setup | Verification | Events |
|---|---|---|---|
| SES | Configuration set → SNS topic → HTTPS subscription to this URL | SNS signature, TopicArn region must match the channel region; the subscription is confirmed automatically | Bounce (Permanent → bounce, others soft), Complaint, Delivery, Open, Click, Reject |
| Resend | Webhooks → endpoint = this URL; signing secret → webhook_secret | Svix signature (5 min tolerance) | email.delivered/bounced/complained/opened/clicked/failed |
Generic (smtp, mock) | JSON POST from your own ESP/MTA | URL token | { "type": "delivered|bounced|soft_bounced|complained|opened|clicked|failed|unsubscribed", "delivery_id"?, "provider_message_id"?, "address"?, "url"?, "error_code"?, "error_message"? } |
Effects: bounce → delivery bounced, subscription invalid, suppression bounce, webhook delivery.bounced (+ delivery.failed with error_code: bounced for backward compatibility) and subscription.invalidated; complaint → suppression complaint, subscription unsubscribed, delivery.complained. A synchronous SMTP 550 also writes a bounce suppression. Repeats of the same event do not increment counters a second time.
Local development
Mailpit (smtp://localhost:1025, UI at http://localhost:8025): save the channel as smtp, host localhost, port 1025, secure: false, then click Validate. With mock email, addresses whose local part starts with invalid/bounce → permanent rejection, transient, rate, auth, fail, open (opened after 5 s) simulate the corresponding behavior.
Metrics
/metrics: messaging_feedback_total{source,type} and suppression_entries_total{channel,reason}; open/click/bounce/complaint rates appear in analytics reports (Analytics).
Geofences
Start journeys when users who share their location enter or leave an area you define. Decision record: ADR-0064. You need to enable location sharing first.
Email deliverability: warm-up, address validation and archive copy
Sending high-volume email from a new sender domain or IP damages your reputation and lands you in the spam folder. For this, Pushizo offers warm-up plans, pre-send address validation and a BCC/archive copy…