Skip to main content

Notifications

A notification node is used to compose and send the data from previous nodes in your CloudFlow to email or Slack. For example, you may have a CloudFlow that retrieves a list of active cost anomalies. You can add a notification node to send the list to the relevant stakeholders, enabling efficient identification and faster resolution. Furthermore, you may have a CloudFlow used solely for sharing information. This is useful for sending both on-demand or scheduled information, outside the context of a specific action or event. For example, a daily CloudFlow that sends a summary of key performance indicators to the leadership team or a scheduled CloudFlow that reminds team members of an approaching deadline.

Notification configuration

Tip

Select Don't send notifications if no results to ensure that notifications are only sent when results are found, preventing unnecessary messages.

Configure provider-specific fields​

Once you select a notification provider, the relevant configuration fields appear.

Slack​

To notify the approver via Slack, you must create a shared Slack channel with DoiT. In Slack channel, select the Slack channel that needs to be notified.

Email​

To notify an approver via email, configure the following fields:

  • Email Address: The Email address of the intended recipient. By default, the Email Address is automatically prefilled with your own email address.

  • Email Subject: A short description of the email. Select the plus icon (+) to search for the fields you want to add to the subject.

Configure the Message field​

You must configure the message that you want to send to your approvers.

Select the plus icon (+) to search for fields from previous nodes to add to your message. When the message is created, the data from the field is displayed in the message. This is useful because it provides recipients with the details they need to make decisions without having to navigate to the system and manually search for the relevant information.

You can present the output as:

  • An array of fields. An array of fields are displayed as a comma-separated list. For example, Instance ID: i-123,i-466.

  • An image.

  • A list.

  • A table.

<image> tag​

Use the CloudFlow custom <image> tag to add an image to your notification message.

  • Images render inline at the tag's location.

  • The <image> tag works by referencing a hosted image via an http or https URL. It does not embed the image file directly in the message. Since the image is not embedded, the URL must be publicly accessible.

  • You can specify a width for the image within the schema. Enter a numeric value, for example, 600. The width is applied in pixels. If width is provided, the height is automatically set to auto to preserve the aspect ratio.

  • You can specify alternative text for an image using alt.

  • Images cannot be nested within another <image>, <list> or <table> tag.

  • The schema for an image is:

    <image width="600" alt="Monthly cloud spend chart">https://.../chart.png</image>.

    image tag example

Below is an example of the output.

table tag example

<list> tag​

Use the CloudFlow custom <list> tag to present output as a list of items.

  • A <list> tag can be nested within other <list> tags.

  • A <list> tag does not require a specific syntax.

    list tag example

Below is an example of the output.

list tag example

<table> tag​

Use the CloudFlow custom <table> tag to format output as a table.

  • A <table> tag cannot be nested within another <list> or <table> tag.

  • Each line within a <table> tag represents a column.

  • The schema for a column is ColumnName: value where value can be static text, one or more referenced fields from a previous node, or a combination of both.

    table tag example

Below is an example of the output.

table tag example

Last updated on