Cireson Portal

Installation Guide: Power Automate Setup

Prerequisites

  • Your Cireson Service Manager Portal must be public facing for Microsoft Power Automate to communicate with it
    • Power Automate communicates with the /platform/api endpoint of the portal

Read the release announcement here to learn more about the features of the Power Automate integration.

Generate an Authentication Token/API Key

In order to make use of the Power Automate integration, you must generate an API key to be used. This can be done by an SMP Administrator by clicking on your name in the top right hand corner of the portal, selecting Authentication Token, and generating a new token. Give it a name and expiration date. Copy the token that is generated as we'll need it to configure the connection to Power Automate. More information on Authentication Tokens can be found here.

 

Use the Token in Power Automate

Once you've signed into Power Automate, let's Create a New Flow to establish our connection. For the purposes of this knowledge article, we're going to start with an "Automated Cloud Flow"

 

On the window that appears, we'll select "Skip"

 

Then search "Cireson", you'll see a Triggers you can use to start a flow.

Selecting either one of the available Triggers will then require you to define a connection to your respective portal

  • Enter a friendly name for the connection
  • The portal URL should be entered such as https://portal.domain.tld/
  • Paste in the Authentication Token/API Key you generated earlier

Click Create and you're done!

 

 

Triggers and Actions

The next section covers the available Triggers and Actions available for use in Power Automate with the Cireson Service Manager Portal

Triggers 

  • When a New Comment is Added
    • This event occurs anytime a comment is added to any Work Item. You can filter this event to either Analyst Comments or End User Comments
    • This Trigger returns the Comment, who left the comment, the date the comment was entered, whether or not it is a private comment, the Comment itself, and the Work Item ID the comment is related to
  • When a New Work Item is Created
    • This event occurs anytime a Work Item is created. You can filter this event to either Incident, Service Request, Change Request, Problem, or Release Record
    • This Trigger returns properties about the Work Item such as the Title, Description, Affected User, Assigned User, etc.

Actions

  • Create an Incident, Service Request, Change Request, Problem, or Release Record
    • Allows you to create any of the core Work Item types along with their respective properties
    • Assigned To/Affected User can be either selected from the list or set via an email address
  • Update an Incident, Service Request, Change Request, Problem, or Release Record
    • Allows you to update any of the core Work Item types along with their respective properties
    • Assigned To/Affected User can be either selected from the list or set via an email address
  • Delete Work Item
    • Permanently removes a Work Item from Service Manager
  • Get Work Item
    • Retrieves a Work Item and its properties from Service Manager
  • Add Comment to Work Item
    • Allows you to leave a Comment on the Work Item's Action Log. Provide the Work Item ID for either an Incident, Service Request, Change Request, Problem, or Release Record, who the Comment is Added By, whether or not it is Private, and whether or not it is an Analyst/End User Comment
    • NOTE: While it is possible to select it, it is impossible to leave an End User Comment that is Private. If you do this, the Comment will simply be marked as an End User Comment.

 

 

Â