Triage HR Tickets

Open

How it works

• Get the information for triaging hr tickets.

• Add the file in the output meta for the same.

• Now add the conditions on the SQL client and send the mail to the respective person through Gmail.

• After completing based on the condition post a message through the Slack channel.

Following are the steps that will help to configure the automation:

Steps to configure

1. Click on start and the below form will appear on the screen.

2. Now add the name “start”, describe “starting node, select webhook from the configuration.

   Open

   

3. Now add a URL into the input field. A webhook is a lightweight API that powers one-way data sharing triggered by events. Together, they enable applications to share data and functionality and turn the web into something greater than the sum of its parts. APIs and webhooks both allow different software systems to sync up and share information.

4. Add the output meta for fetching the details of issues. Output metadata is the type resolution for the result of a component. Each component can provide either static or dynamic metadata for the payload and attributes, isolated from each other. Click on browse, and add the metafile in a JSON format in the file name.

5. Now, add the conditions with the help of conditional branching for SQL client and Slack. Conditional branching is the term used to describe the set of operations such as 'if <condition> do <something> else do <something else>' and the various case and switch statements in conventional imperative languages such as C, PERL, and Java.

6. The conditions can be found from the condition expression.

7. The condition expression format is mentioned below.

8. Click on SQL client and the below form will appear on the right side of the screen.

9. Add the connection. Create an OAuth2.0 connection using https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585 template or use the pre-defined connection.

10. Add the query type as an insert. They are five types of queries, i.e., select queries, action queries, parameter queries, crosstab queries, and SQL queries.

11. Provide a formula for detailed information related to the query, in the query field.

12. Add the key as Jira key, and provide the value.

13. You can add multiple key and values based on the requirements. A key is a field, or combination of fields, in a database table used to retrieve and sort rows in the table based on certain requirements. On the other hand, value is the information and formula field of automation.

14. Connect the SQL client with Gmail. After selecting Gmail the below form will appear on the screen.

15. Add the connection as “Gmail Google Rest Oauth connection”. Create an OAuth2.0 connection using https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585 template or use the pre-defined connection.

16. Provide an action as “send mail”. Actions enable users to interact with your product or service right inside Gmail. Actions can be declared in two ways: in-app actions or as go-to actions.

17. Now, mention the email id in the to address field. An email address identifies an email box to which messages are delivered.

18. Provide a subject for creating the tickets through Jira. The subject field is a brief description of the message. It displays in the recipient's inbox before they open the message.

19. Add a message for “creating the ticket” in the message field.

20. Now, add Gmail with Slack for posting notifications in the channel.

21. After you select Slack, the below form will appear on the screen.

22. Add the connection as Slack. Create an OAuth2.0 connection using https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585 template or use the pre-defined connection.

23. Now, add an action as “send message to channel”. An action appears on the home page, of the Salesforce account in the chatter tab. It’s recorded in chatter groups, and on record detail pages. It’s just as object record pages have page layouts that can be customized, actions have action layouts that can be customized.

24. Provide a channel name. A channel's name lets people know what it's used for. If the purpose of a channel changes at any point in time, it can be renamed.

25. Now, add the message for creating the new tickets.

26. Add the aggregator and end the process.

27. Now, save the automation for future use.