Skip to main content

​
Email

Email is the quiet integration. Use it for compliance distribution lists, off-hours summaries, and anyone who’d rather a single morning digest than a stream of Slack pings.

​
Two modes

Roboticks supports two email cadences per recipient: A recipient can mix modes — e.g., per-event for evidence_pack.generation_failed, daily digest for everything else.

​
Set up

1

Add an email connector

Settings → Integrations → Email → Add. Name it for the audience (e.g., compliance-officers).
2

Recipients

Comma-separated mailboxes:
Distribution lists work fine — DL members each apply their own per-recipient preferences if they have a Roboticks account.
3

Default cadence

Pick per-event or daily digest as the connector default. Recipients with Roboticks accounts can override per event type.
4

Pick event types

Toggle the events to route. Defaults are conservative: evidence_pack.generated and evidence_pack.generation_failed on, the rest off.
5

Send test

Hit Send test email. A sample arrives within seconds.

​
Per-recipient preferences

Anyone with a Roboticks account at app.roboticks.io → Profile → Notifications can override the connector defaults for events that involve them:
  • Project they’re a member of
  • Requirement they authored
  • Test run they triggered
These preferences override connector-level routing for the recipient’s own mailbox only — they don’t affect the rest of a distribution list.

​
Sample emails

​
Per-event — test run failed

​
Daily digest

​
Calendar-aware digests

Daily digests respect:
  • The recipient’s profile timezone (UTC by default)
  • A quiet-hours window (default 22:00–07:00 local) — events that would page during quiet hours queue for the morning digest
  • A weekend mode (off by default) — Saturday/Sunday digests can be suppressed for non-on-call roles
Configure at app.roboticks.io → Profile → Notifications → Digest schedule.

​
Deliverability

If your gateway is aggressive, allowlist notify.roboticks.io and noreply@roboticks.io. The bounce rate from us is sub-0.1%, so deliverability issues are almost always at the receiver end.

​
Multiple connectors

You’ll often want several email connectors:

​
Troubleshooting

Check the delivery log at Settings → Integrations → Email → Delivery log. Status bounced means the recipient’s mailbox rejected; dropped means our pre-send checks (SPF, DKIM) flagged the recipient domain.
Switch them to daily digest via Profile → Notifications, or remove them from the connector’s distribution list and have them subscribe per-recipient.
DL members who unsubscribe only mute their own delivery — the DL itself is unaffected for everyone else. Use individual mailboxes if you need DL members to opt out without affecting peers.

​
Best practice

  • Reserve per-event for the events that actually need real-time attention.
  • Use distribution lists, not individual mailboxes — survives team changes.
  • Wire one connector to evidence_pack.generated and route it to the auditor’s mailbox; that’s the most common use of email in regulated shops.