Email Notification Action

The Email Notification action sends an email to the specified email address.

You can send up to 10 emails per hour per Soracom account. Each recipient email address specified in the To, CC, and BCC fields counts as one email, so the count is based on the total number of recipient email addresses rather than the number of times the action runs. This hourly limit is shared with the Email Notification Action (Advanced) and calculated separately for each coverage type. For each coverage type, the one-hour period starts when the first email is sent using either action. On the Developer plan, you can also send up to 100 emails per month. If you exceed these limits, an error will be returned. If you need to send more than 100 emails per month, please use the Standard plan. See Plans for details. The monthly rate limit is counted per coverage type, starting from the date and time of the first email sent via the Email Notification Action. It is not based on a calendar month (e.g. resetting on the 1st of each month).

Configuration

In the Action Condition input field, you can specify the conditions under which the action will be executed using the values (Message or Context) from the event source to the channel. For details on supported expressions, refer to Use Expressions in Actions.

Configuring Email Notification Action

The Subject and Body fields support expressions.

To: Enter the recipient's email address.
CC: Enter the email address to add as a CC recipient.
BCC: Enter the email address to add as a BCC recipient.
Subject: Enter the email subject.
Body: Enter the email body.

Notifications are sent only to email addresses whose deliverability has been verified. Send a verification email to any unverified address to verify its deliverability. For details, refer to Verifying Email Address Deliverability.
You can save the action while unverified addresses remain, but no notification is sent to those addresses until verification is complete. If every recipient is unverified, sending the notification fails.

Output

Set up how the action's output data will be processed. Refer to Enable Republishing of Action Output for more details.

Verifying Email Address Deliverability

When you enter an unverified email address as a recipient, a message Deliverability verification is required is displayed. Verify the deliverability as follows:

Click Send verification email.

A verification email is sent to the address, and Waiting for verification is displayed. If the email does not arrive, click Send verification email again.
Click the link in the verification email within 24 hours of sending it.

The deliverability is verified, and a check mark is displayed to the right of the email address. If the link has expired, send the verification email again.

The verification email has the subject "Verify your email address for Soracom Flux" and is sent from no-reply@soracom.io. If it does not arrive, check your spam folder and your email filtering settings.

Switching an Existing Email Notification Action to Direct Entry

An Email Notification Action that has not been switched to direct entry selects its recipients from the email addresses added to the Soracom account. In this mode, only the root user can set the recipients, and only email addresses that have already been added to the account are available. For details on adding an email address to a Soracom account, refer to Adding an Email Address.

After you switch to entering email addresses directly, SAM users can also set the recipients.

In the action's configuration, click Switch to entering email addresses directly.

The current recipients are carried over, and the deliverability of each email address is checked.
Verify the deliverability of every address shown as unverified.

For the procedure, refer to Verifying Email Address Deliverability.
Save the action settings.

Switching alone does not save the action settings.

Output Data of the Action

When the Email Notification Action successfully sends an email, a response is returned containing the recipients and usage information. For example:

{
  "sent": {
    "to": ["user@example.com"]
  },
  "usage": [
    {
      "curr": 4,
      "limit": 10,
      "resetAt": "2026-03-02T10:20:37Z"
    },
    {
      "curr": 30,
      "limit": 100,
      "resetAt": "2026-03-12T09:10:53Z"
    }
  ]
}

If CC or BCC recipients are included, they also appear in the response:

{
  "sent": {
    "to": ["user@example.com"],
    "cc": ["another@example.com"]
  },
  "usage": [
    {
      "curr": 4,
      "limit": 10,
      "resetAt": "2026-03-02T10:20:37Z"
    },
    {
      "curr": 30,
      "limit": 100,
      "resetAt": "2026-03-12T09:10:53Z"
    }
  ]
}

The usage array contains rate limit information for the action. Depending on your plan, this array may include one or more limit periods (such as hourly and monthly):

Field	Description
`curr`	The number of emails sent in the current period.
`limit`	The maximum number of emails allowed in the period.
`resetAt`	The time (in UTC) when the counter resets.

This response confirms that the email was sent, but does not confirm receipt of the email by the recipient.