Mail

Embedding Forms in Dashboards

The email sending feature in Gaio DataOS allows you to configure email service providers and automate deliveries directly from your data flows. This functionality can be used for operational communications (reports, alerts, notifications) as well as for business process integrations.

How to Use

1. Add the Mail to the Flow

  • Add a Table to your flow and choose the dataset you want to work with.

  • The Report task will only become available once a table is selected.

  • In the Studio, go to the Tasks panel.

  • Go to Delivery > Mail in the task menu.

2. Message Tab

This tab defines the message content:

  • To (email): Select the column in the table that contains recipients' email addresses.

  • Subject: Enter the email subject.

  • Message editor: Create the email body using HTML, plain text, or table variables.

  • Available columns: On the left panel, you can drag variables (such as name and email) to personalize the message.

3. Settings Tab

This tab configures the sending provider:

  • Service provider: Available options:

    • SMTP

    • Resend

    • AWS SES

    • SendGrid

  • Configuration fields:

    • Host / Port: Address and port of the SMTP server (when applicable).

    • User / Password: Service authentication credentials.

    • Sender name: Display name of the sender.

    • Sender email: Sender's email address.

    • Log Table: Table where sending logs will be stored.

    • Table log ID column: Unique identifier column for logs (optional).

    • How many days to keep logs?: Log retention time (in days).

    • Time in milliseconds to wait between sends: Interval between sends (in ms).

    • TLS and Office365/Microsoft: Additional options for secure authentication.

4. Preview Tab

  • Allows you to preview the message before sending.

  • Useful to validate personalization (e.g., user name, dynamic email).

5. Extra Data Tab

  • Space to include table additional that can be used in the email body.

6. Best Practices

  • Logs: Enable the log table to track sends and errors.

  • Interval between sends: For large-volume campaigns, configure a delay to avoid provider blocking.

  • Testing: Always test with a staging email before sending mass communications.

PreviousMapNextParams

Last updated