Qubitro Documentation
SupportLog inSign Up
  • Documentation
  • Guides
  • Developers
  • Welcome
  • Data Sources
    • No-Code Integrations
      • Onomondo
      • Notehub
      • The Things Stack
      • Soracom
      • Loriot
      • 1NCE
      • Golioth
      • AWS IoT Core LoRaWAN
      • Actility ThingPark
      • Chirpstack
      • Particle
    • MQTT
    • HTTP
  • Platform
    • Project
      • Settings
      • Access Management
      • Roles & Permissions
    • Device
      • Settings
    • Storage
      • Time Series Storage
    • Functions
      • Decoder Function
        • LoRaWAN Device Template Decoder
        • LoRaWAN Custom Decoder
        • Hex Payload Decoder
      • Transformation Function
      • Rule Function
        • Send Email
        • Webhooks
        • Slack
        • Twilio
        • Mailgun
        • SendGrid
      • Storage Function
        • AWS Redshift
        • Google BigQuery
        • MQTT Publish
        • MongoDB Time Series
      • Scheduled Function
        • HTTP
      • Function Settings
      • Function Templates
        • Settings
    • Monitoring
      • Dashboards
        • Setup & Configuration
        • Widgets
          • Chart
          • State Timeline
          • Gauge
          • Stat
          • Headline
          • Aggregated Chart
          • Map
          • Battery
          • Image
          • Image Map
          • Table
          • Storage Table
          • Iframe
          • Blob Storage
        • Settings
        • Access Management
        • Roles & Permission
      • Blueprints
        • Setup & Configuration
        • Settings
    • Credentials
      • API Keys
      • External Credentials
        • Slack
        • Mailgun
        • SendGrid
        • Twilio
        • AWS Redshift
        • MQTT
        • MongoDB
        • The Things Stack
      • Webhook Signing Key
  • Add-Ons
    • Storage Views
    • Aggregated View
    • Archived Views
    • Blob Storage
    • Managed Email
    • Audit Log
    • MCP Server
  • Organizations
    • Overview
    • General
    • Groups
    • Members & Roles
      • Read Only
      • Read/Write
      • Admin
    • Custom Roles
    • Add-Ons
    • Billing
    • Invoices
    • White-Label
  • Account Management
    • Personal Accounts
Powered by GitBook
On this page
  • When to Use
  • Configuration
  • Common Errors & Troubleshooting
Export as PDF
  1. Platform
  2. Functions
  3. Rule Function

Send Email

The Send Email action in Qubitro Rule Functions allows you to trigger emails based on data conditions from your devices.

PreviousRule FunctionNextWebhooks

Last updated 2 months ago

The Send Email action in allows you to trigger emails based on data conditions from your devices. This feature is helpful for real-time alerts, notifications, and status updates.

Send Email is a fully-managed service and supports multiple recipients

The Send Email action requires the to be enabled in your organization's

When to Use

  • Send alerts based on threshold breaches (e.g., temperature too high).

  • Notify team members or customers about device statuses.

  • Provide regular device data updates automatically.

Configuration

1

Configure Basics Settings

  • Set Debounce period (optional): Choose a time frame during which repeated triggers will be ignored. This prevents excessive emails.

  • Enter Name: Enter a unique, descriptive name for your function.

  • Provide Description: Add details that help your team quickly understand the purpose of the function.

2

Configure Email Template

Create dynamic email content using available placeholders:

  • Message: Craft your email body using available placeholders:

    • "${{data_key}}": Inserts the value from your device data (e.g., temperature, humidity).

    • <%device_name%>: Inserts the name of the triggering device.

    • <%last_seen%>: Inserts the last-seen timestamp of the device.

Example message:

Alert: Last value from sensor: ${{temperature}}

Device: "<%device_name%>"

Qubitro Team
  • Subject: Enter the email subject line clearly indicating the alert type.

  • Title: Provide a short, clear title summarizing the email content.

  • Recipient: Add one or more email addresses to receive the notification.

3

Condition Configuration

  • Condition type: Select or to configure condition.

Example:

function run(){
  let temperature = "${{temperature}}";

  if (temperature > 30){
    trigger();
  }
};

This logic sends an email if the temperature value exceeds 30.

Common Errors & Troubleshooting

Email not triggering
  • Check JavaScript conditions for syntax errors.

  • Verify that the debounce period isn't unintentionally blocking emails.

Incorrect data in emails
  • Ensure placeholders exactly match your device's data keys.

  • Confirm the data keys exist in your device's data payload.

Rule Functions
Managed Email Add-On
add-on settings.
JavaScript Logic Builder
Visual Condition Builder