RobotAgentz Docs

Appearance

Send a Simple Email with no Attachments ​

This task block is used to send a simple email with no attachments. Just add the email address to the "Send to" configuration item, a subject to the Subject configuration item and some text to the Body configuration item.

There is a configuration item for "Email Server" which if left blank tells the mission to just use the default RobotAgentz email server. If you want to use your own email server you can create an email server contract and reference that contract here.


If the input to the delay block is triggered this task block will attempt to send an email to the email address. If the email succeeds the output "Success" will be triggered, else the "Failed" will be triggered.

Note: ​

You can use multiple email addresses by separating them by a comma.

darth@deathstar.com,papapalpatine@sithlounge.com,maul@halfsies.com

Examples ​

Here is a simple example of a mission that uses a simple email send.

Use Cases ​

This task block has unlimited use cases. A big part of automation is to send emails for alerting, information updates, or requests for action. There are several different types of email task blocks where this one is the simplest.

Copy / Settings / Docs ​

Each task block has three buttons named Copy, Settings, and Help.

  • Copy: This will duplicate the task block with all the current settings.
  • Settings: Settings will show a dialog that allows some added configuration for the block
    • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
    • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
    • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.

Other ​