Action Sequences

Action Sequences are similar to triggers, but they run sequentially and can share context with actions. For example, when there are multiple actions configured, the output from the first action can be used by the subsequent actions. In addition, Action Sequences can function as actions themselves and are conveniently accessible under the Custom Actions tab within triggers.

Supported Modules: Requests and Changes

To create an action sequence,

 

Use Case

The following use case automates the creation of a Jira issue when a request is submitted. It then adds a note to the same request in SDPCloud with the generated Jira Issue ID for reference.

To achieve this, when a new request is created, a trigger needs to be initiated with an Action Sequence containing two Zoho Flow actions:

  1. Jira - Create Issue: To automatically create a corresponding issue in Jira.

  2. SDPCloud - Create Request Note: To add a note to the current request (${request.id}) in SDPCloud, embedding the Jira Issue ID (${flows.create_jira_issue.id}) generated from the first action.

Use Case For Changes

Zylker’s IT team uses Azure DevOps to manage implementation activities related to ITSM changes. When a change request is approved in ServiceDesk Plus Cloud, an Azure DevOps work item is automatically created and linked to the relevant ongoing project. Key work item details, such as ID, status, assignee, priority, and URL, are synchronized back to the corresponding change request in ServiceDesk Plus Cloud. This enables development and operations teams to efficiently track and complete implementation tasks within their existing DevOps workflows.

You can achieve this by executing an action sequence containing two Zoho Flow actions via Trigger.

Create an action sequence with two Zoho Flow actions:


Action Sequence Configuration with the Zoho Flow Actions