Actions
Last updated
Last updated
After a trigger activates, actions execute predefined tasks that automate responses, such as notifying stakeholders, creating issue tickets, or managing processes.
Core actions are designed to help you control how workflows progress, introducing delays or conditions that guide the next steps in the process.
The Delay action allows you to introduce a waiting period before executing the next step in a workflow. You can set the delay period based on:
Hours
Days
Weeks
Months
Years
With the Conditional action, you can set logic-based conditions that determine how a workflow progresses. Based on predefined parameters, workflows can take different paths, enabling flexible automation.
You can configure conditions based on the following attributes:
Ticket Attributes – Status, Category
Recommendation Details – Potential Savings, Effort Required
Resource Information – Name, Account, Region, Service, Tags
Cost Center Details – Cost Center, Category
Policy Information – Name, Category
By setting these conditions, you control when a workflow moves forward.
Issue actions allow you to automate ticket creation and integration with external issue management systems like Jira.
The Jira action enables you to automatically create an issue in Jira when a workflow is triggered. To set it up, you'll need to provide the following information:
Connection Type – Choose the Jira connection that OneLens will use.
Project – Select the Jira project where the issue should be created.
Epic – Choose the Jira epic under which the issue should be categorized.
Assignee Name – Assign the issue to a specific user in Jira.
Prerequisite: To use this action, Jira must be integrated with OneLens. If it's not yet integrated, refer to the [Jira Integration] for setup instructions.
Messaging actions let you automate notifications, ensuring that your team or stakeholders are informed of relevant events or updates. You can use different channels, such as Slack or email, to communicate efficiently.
The Slack action sends notifications to either a user or a channel.
User Notifications:
Select the Slack connection.
Choose the user who will receive the notification.
Optionally, add a message to provide additional context.
Channel Notifications:
Select the Slack connection.
Choose the channel where the alert will be posted.
Optionally, include a message with relevant details.
Prerequisite: Slack must be integrated with OneLens to use this action. If not already set up, follow the [Integration Documentation] for guidance.
The Email action sends an automated email to selected recipients. When setting up the email action, you will:
Choose the recipients who will receive the email.
Optionally, add additional recipients in CC or BCC.
Define the subject of the email.
Optionally, include a message to provide further context.
Note: Email notifications can only be sent to users who have OneLens access.
You can combine multiple actions within a workflow, and depending on your needs, they can be executed in series, parallel, or hybrid execution types, offering flexibility to handle even complex automation scenarios.
