Action steps reference

Action steps define what happens when a workflow fires. You can chain multiple steps in sequence and use template variables to include dynamic data.

Messaging steps

Send email

Send an email to one or more recipients.

• Recipients: static email addresses, a field from the trigger data, the action's assigned user, or specific team members
• Mode: write the email inline, or use a pre-built email template
• Subject and body: support template variables like {{metric_value}}, {{dimension_value}}, {{action_name}}

Slack message

Post a message to a Slack channel.

• Requires a Slack connection (set up in Setup > Connectors)
• Choose the channel to post in
• Write a message template with variables

Teams message

Post to a Microsoft Teams channel.

• Use a webhook URL or a configured Teams connection
• Supports title and message body with template variables

Discord message

Post to a Discord channel via webhook.

• Configure a webhook URL or use a Discord connection
• Supports title and message body

Google Chat message

Post to a Google Chat space.

• Use a webhook URL or configured connection

Other messaging channels

Genuics also supports: Mattermost, Webex, Telegram, ntfy, and PagerDuty (for incident alerting). Each works similarly - configure a connection or webhook URL and write a message template.

Zapier

Send data to a Zapier Catch Hook URL, allowing you to trigger any of Zapier's 5,000+ integrations.

Task creation steps

Create action

Automatically create an action (follow-up task) when the workflow fires.

• Name template: e.g., "Investigate NPS drop in "
• Description template: pre-fill with trigger context
• Priority: low, medium, high, or urgent
• Category: choose from your configured categories
• Assigned to: a specific user or team
• Team: assign to a specific team/LoB

Send notification

Send an in-app Genuics notification.

• Recipients: specific users, a team, or users with a specific role
• Title and message templates with dynamic variables

Control flow steps

Delay

Pause the workflow for a specified number of minutes before proceeding to the next step.

Example: "Wait 30 minutes after sending a Slack message, then check if the action has been assigned."

Condition

Add if/then logic based on data values. Conditions use the same filter builder as dashboards - AND/OR groups with field comparisons.

See Conditional branching for details.

Webhook step

Webhook call

Make an HTTP request to an external URL.

• Method: POST or PUT
• URL: the endpoint to call
• Headers: custom headers (e.g., Authorization)
• Body template: JSON body with template variables

Example: "POST to your internal ticketing system API when a high-priority action is created."

Template variables

Most steps support template variables in their text fields. Common variables include:

Variable	Description
{{metric_value}}	The metric value that triggered the workflow
{{dimension_value}}	The dimension value associated with the trigger
{{action_name}}	The name of the related action
{{action_status}}	The action's current status
{{action_assignee}}	The name of the assigned user
{{dataset_name}}	The dataset that triggered the event

Next steps

• Learn how to create a workflow end to end
• Add conditional branching for complex logic
• Set up digest mode to batch notifications