Revelation helpdesk
The Revelation helpdesk connector allows you to create and update items in your helpdesk such as tickets, clients, users and assets by connecting to the Revelation helpdesk API using OAuth authentication. You can also take advantage of the extensive list of triggers allowing you to integrate your business processes based on events that occur in Revelation helpdesk
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Yellowfish Support |
| URL | https://revelationhelpdesk.com |
| support@yellowfishsoftware.com |
| Connector Metadata | |
|---|---|
| Publisher | Yellowfish Software |
| Website | https://revelationhelpdesk.com |
| Privacy policy | https://revelationhelpdesk.com/privacypolicy |
| Categories | IT Operations;Productivity |
Revelation helpdesk is a web-based helpdesk ticketing application available as a cloud hosted solution or as an on-premises platform. This connector allows you to create and update items in your Revelation helpdesk ticketing system such as tickets, clients, users and assets by connecting to the Revelation helpdesk API using OAuth authentication. New Tickets can be logged, action notes added and you can reassign or change the priority / status of existing tickets. You can also take advantage of the extensive list of triggers allowing you to integrate your business processes based on events that occur in Revelation helpdesk.
You will need a Revelation helpdesk account in order to use this connector. If you are not yet signed up for Revelation helpdesk you can get a free 30 day trial here.
To use the connector you will need the URL to your Revelation helpdesk instance and you will need a super admin account. If you have signed up for a Trial the URL will be 'https://trial.revelationhelpdesk.com' and your super admin username will be the email address you used to sign up with. You will be promped to change your default password the first time you sign in to your trial account through the web interface.
To start using the Revelation helpdesk connector create a new flow and add a new step. Then search for "Revelation helpdesk" and select any of the available actions.
The first step when adding a new action or trigger is to create a connection to your instance of Revelation helpdesk. When prompted, enter your Revelation helpdesk URL and make sure to enter a secure URL (HTTPS://) and the url does not end with '/'
After you enter your Revelation helpdesk URL click 'Sign In' and you will see a popup login form. Enter your Revelation URL again and your Revelation username and password.
Once you have signed in successfully you will be able to interact with the chosen action.
Here is a simple example of how to log a new ticket using the 'Log a new Ticket' action. Simply select the Client, Project, End User, enter a Ticket description and choose a ticket status. When the flow runs it will create a new ticket for this end user and assign it to the selected project.
Here is an advanced scenario where we log a new ticket from an email. When a new email arrives it will trigger the flow and use the 'Find a user' action to find the user in Revelation helpdesk by the email's FROM address. The 'Log a new Ticket' action then logs a ticket to the End User using the output (The User Id) from the previous step. The ticket description will be the subject line of the email and the Client and Project fields can be left blank because these will get set automatically based on the end user of the ticket. Next we will use the "Add an Action" action to add a note to the newly logged ticket in the previous step. The 'Ticket Id' is the ID of the ticket logged in the previous step and the Notes are set to be the body of the email.
The ticket that is logged in Revelation helpdesk will look similar to this
A common scenario for using triggers would be to alert a team or manager when a ticket is due or at risk. In the following example we've added the "When a Ticket is Due" trigger which would start the flow as soon as any open ticket reaches its due date.
A conditional step has been added to check the Department name for the ticket, if it is for HR it will continue, if not it will terminate the flow. This is just an example of the type of logic statements that can occur based on ticket data.
Finally the last step is set to post a new message in a Teams Channel which includes a message that the ticket is due and also includes the Ticket # and Ticket description in the message body
- Actions and Trigger names in the connector don't reflect the phrases configured in Revelation helpdesk however, the field names for all the actions and triggers will reflect the custom phrases. For example the word "Ticket" can be changed to "Issue" but the action name "Log a new Ticket" won't change. The field names in that action like "Client", "Project" and "End User" will be updated dynamically based on your Revelation helpdesk phrase configuration.
- This connector only support Revelation helpdesk V22.3 (Cloud) and Revelation server 2022 (On-Premise). There are further requirements in order to use the connector with the on-premise version of Revelation helpdesk.
Please see our help guide for more details on Revelation helpdesk functionality or for further assistence and support please contact support@revelationhelpdesk.com
The connector supports the following authentication types:
| Default | Parameters for creating connection. | All regions | Not shareable |
Applicable: All regions
Parameters for creating connection.
This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.
| Name | Type | Description | Required |
|---|---|---|---|
| Revelation URL | string | Your Revelation site URL (Example: https://support.yourdomain.com) | True |
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
| Add an action |
Add an action to an existing ticket in Revelation helpdesk |
| Create Asset |
Create a new Asset |
| Create Client |
Create a new Client (Company) in Revelation helpdesk |
| Create Office |
Create a new Office in Revelation helpdesk |
| Create User |
Create a new User |
| Find a user |
Find a single User in Revelation helpdesk |
| Get an existing Asset |
Get an existing Asset in Revelation helpdesk |
| Get an existing Ticket |
Get an existing Ticket by ID in Revelation helpdesk |
| Log a new Ticket |
Log a new Ticket in Revelation helpdesk |
| Reassign a Ticket |
Reassign a ticket in Revelation helpdesk |
| Search for Assets |
Search for existing Assets in Revelation helpdesk |
| Set Ticket Priority |
Set the Priority of an existing Ticket |
| Set Ticket Status |
Change the Status of a Ticket in Revelation helpdesk |
| Set Ticket Type |
Sets the Ticket Type of an existing Ticket |
| Update Asset |
Update an existing Asset |
Add an action to an existing ticket in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
- response
- boolean
Create a new Asset
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Create a new Client (Company) in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Create a new Office in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Create a new User
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Find a single User in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Get an existing Asset in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Asset Id
|
id | True | integer |
Asset Id |
Returns
Get an existing Ticket by ID in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Ticket #
|
id | True | integer |
Ticket # |
Returns
Log a new Ticket in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Reassign a ticket in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
- response
- boolean
Search for existing Assets in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
Set the Priority of an existing Ticket
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
- response
- boolean
Change the Status of a Ticket in Revelation helpdesk
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
- response
- boolean
Sets the Ticket Type of an existing Ticket
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
Returns
- response
- boolean
Update an existing Asset
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
body
|
body | dynamic |
| When a Asset is created |
This operation is triggered when an Asset is created |
| When a Asset is updated |
This operation is triggered when an Asset is updated |
| When a Client is created |
This operation is triggered when a Client is created |
| When a Client is updated |
This operation is triggered when a Client is updated |
| When a Office is created |
This operation is triggered when an Office is created |
| When a Office is updated |
This operation is triggered when an Office is updated |
| When a Ticket is at risk |
This operation is triggered when a Ticket is at risk |
| When a Ticket is closed |
This operation is triggered when a Ticket is closed |
| When a Ticket is deleted |
This operation is triggered when a Ticket is deleted |
| When a Ticket is due |
This operation is triggered when a Ticket is due |
| When a Ticket is logged |
This operation is triggered when a Ticket is logged. |
| When a Ticket is reopened |
This operation is triggered when a Ticket is reopened |
| When a Ticket is updated |
This operation is triggered when a Ticket is updated (action added). |
| When a User is created |
This operation is triggered when an User is created |
| When a User is updated |
This operation is triggered when an User is updated |
This operation is triggered when an Asset is created
Returns
This operation is triggered when an Asset is updated
Returns
This operation is triggered when a Client is created
Returns
This operation is triggered when a Client is updated
Returns
This operation is triggered when an Office is created
Returns
This operation is triggered when an Office is updated
Returns
This operation is triggered when a Ticket is at risk
Returns
This operation is triggered when a Ticket is closed
Returns
This operation is triggered when a Ticket is deleted
Returns
This operation is triggered when a Ticket is due
Returns
This operation is triggered when a Ticket is logged.
Returns
This operation is triggered when a Ticket is reopened
Returns
This operation is triggered when a Ticket is updated (action added).
Returns
This operation is triggered when an User is created
Returns
This operation is triggered when an User is updated
Returns
This is the basic data type 'boolean'.