How can we help?
{{docApp.searchError}}
{{product.name}}
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Operation Information
Updates the details of an Incident in Freshstatus.
This is a Premium Integration.
Authentication
This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type Freshstatus.
To create a key of this type:
- In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
- Click on the + Create New Key button;
- On the resulting Create New Key form, choose Freshstatus in the Type pick list;
- Give the Freshstatus KeySafe key a Title (this is the name / identifier for the Freshstatus account as you will see it when using the cloud automation node in your workflows);
- Optionally populate the Description field;
- Populate the following fields accordingly, then click the Create Key button to create your new key:
Name | Type | Description |
---|---|---|
Domain | string |
The subdomain value for your Freshstatus account: https://subdomain.freshstatus.io |
API Key | string |
Freshstatus Account API Key |
Revoking Access
If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.
Warning
This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked Freshstatus account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
Incident ID | id |
integer |
The Incident ID | Yes | None provided |
Incident Title | title |
string |
The incident title | No | None provided |
Incident Description | description |
string |
The incident description | No | None provided |
Incident Start Time | startTime |
string |
The incident start date/time in the following format: YYYY-MM-DDTHH:MM:SSZ | No | None provided |
Incident End Time | endTime |
string |
The incident end date/time in the following format: YYYY-MM-DDTHH:MM:SSZ | No | None provided |
Enable Incident Privacy | isPrivate |
boolean |
Is The Incident Private | No | None provided |
Incident Source ID | source |
integer |
The ID of your incdient source, this can be found within fresh status. | No | None provided |
Enable Incident Notifictions | sendNotfication |
boolean |
Enable Incident Notification Alerts | No | None provided |
Affected Components | affected_components |
array |
Any affected components | No | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Error Message | error |
string |
Any errors returned by the Freshstatus API |
Status Code | status |
string |
The status of the operation: ok / failed |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}
In This Document