Skip to Content
IntegrationsEmail

Email

The Email integration is built into TinyOps and always available. No setup or API keys are needed. Powered by Resend, it delivers transactional emails for rule notifications, alerts, and reports directly to any recipient.

Setup

No Configuration Required

The Email integration is enabled by default for all TinyOps workspaces. There is nothing to connect or authorize.

Verify Sender Address

All emails are sent from notifications@tinyops.cc. Ensure this address is allowlisted in your organization’s email filters if you use strict spam policies.

Start Using in Rules

You can immediately reference the email provider in any rule action. No integration setup page is needed.

Email delivery is powered by Resend and does not count against any third-party quota. All TinyOps plans include unlimited email notifications.

Available Checks

The Email integration does not provide any checks. It is an action-only provider used for delivering notifications.

Available Actions

MethodParamsDescription
sendto (required), subject (required), body (required)Sends an email to the specified recipient. Template variables are supported in all params.

Template variables can be used in to, subject, and body fields. For example, {{pr.author.email}} dynamically inserts the PR author’s email address.

Example Rules

Weekly Summary Report

Send a weekly summary of repository health metrics every Monday morning.

weekly-summary.yaml
name: Weekly Summary Report
trigger:
  schedule: "0 9 * * 1"
  provider: github
conditions:
  - check: repo.open_prs
    operator: gt
    value: 0
actions:
  - method: send
    provider: email
    params:
      to: "team@tinyops.cc"
      subject: "Weekly Repo Summary — {{repo.open_prs}} open PRs, {{repo.open_issues}} open issues"
      body: |
        Here is your weekly repository health summary:
 
        Open Pull Requests: {{repo.open_prs}}
        Open Issues: {{repo.open_issues}}
 
        Review stale PRs and close resolved issues to keep the backlog clean.

Deploy Failure Notification

Email the on-call engineer when a production deploy fails.

deploy-failure-email.yaml
name: Deploy Failure Email
trigger:
  event: deployment.status_changed
  provider: vercel
conditions:
  - check: deployment.status
    operator: eq
    value: ERROR
actions:
  - method: send
    provider: email
    params:
      to: "oncall@tinyops.cc"
      subject: "ALERT: Production deploy failed"
      body: |
        A production deployment has failed.
 
        Project: tinyops-web
        Status: {{deployment.status}}
        Domain: {{deployment.domain}}
 
        Please investigate immediately and trigger a rollback if necessary.

Cost Threshold Alert

Notify the billing admin when Vercel costs exceed a defined budget.

cost-threshold-email.yaml
name: Cost Threshold Alert
trigger:
  schedule: "0 8 * * *"
  provider: vercel
conditions:
  - check: billing.projected
    operator: gt
    value: 75
actions:
  - method: send
    provider: email
    params:
      to: "billing@tinyops.cc"
      subject: "Vercel cost alert: projected ${{billing.projected}} this month"
      body: |
        Your projected Vercel spend for this month is ${{billing.projected}}, which exceeds the $75 budget threshold.
 
        Current month-to-date spend: ${{billing.mtd}}
 
        Review usage at https://vercel.com/dashboard and consider optimizing serverless functions or bandwidth usage.

Troubleshooting

Common issues:

  • Email not received: Check your spam or junk folder. Add notifications@tinyops.cc to your contacts or allowlist.
  • Invalid to address: The to param must be a valid email address. Template variables that resolve to non-email strings will cause delivery failure.
  • Body formatting: Email bodies are sent as plain text. HTML tags in the body will be displayed as raw text, not rendered.
  • Rate limits: TinyOps allows up to 100 emails per rule execution. If a rule targets more recipients, split them across multiple rules or use a mailing list address.
SlackPR Health Pack