How can we help?
{{docApp.searchError}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
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
Hornbill Cloud Automation to create a new PagerDuty Incident.
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 PagerDuty.
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 PagerDuty in the Type pick list;
- Give the PagerDuty KeySafe key a Title (this is the name / identifier for the PagerDuty account as you will see it when using the cloud automation node in your workflows);
- Optionally populate the Description field;
- Click the Create Key button to create your new key;
- Once the Key is created, you will need to connect to the target service, and your account, in order to authorize the connector app access to the listed operations. Click the Connect button and you will be redirected to the service provider in a popup window;
- Log in to your account, and then you will be prompted to review the options you are authorizing the Hornbill connector to be allowed to perform using the chosen account;
- Accept the review and you will be returned to your KeySafe key.
Revoking Access
If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just hit the Revoke button in the relevant KeySafe key(s).
Warning
This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked PagerDuty account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
Title | title |
string |
The Incident Title | Yes | None provided |
Service | service_id |
string |
The ID of the Service | Yes | None provided |
Priority | priority_id |
string |
The ID of the Priority | No | None provided |
Urgency | urgency_id |
string |
The Urgency of the Incident | No | High, Low |
Body | body |
string |
The Incident Description | No | None provided |
Incident Key | incident_key |
string |
A string which identifies the incident. Sending subsequent requests referencing the same service and with the same incident_key will result in those requests being rejected if an open incident matches that incident_key | No | None provided |
Assignments | assignments |
array |
Assign the incident to these assignees. Cannot be specified if an escalation policy is given | No | None provided |
Escalation Policy | escalation_policy_id |
string |
The ID of the Escalation Policy to use | No | None provided |
Conference Number | conference_number |
string |
The phone number of the conference call for the conference bridge. Phone numbers should be formatted like +1 415-555-1212,1234#, where a comma (,) represents a one-second wait and pound (#) completes access code input | No | None provided |
Conference URL | conference_url |
string |
The URL of the conference bridge | No | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Outcome | outcome |
string |
The outcome of the iBridge operation |
Error | error |
string |
Any errors returned from the iBridge operation |
Incident ID | id |
string |
None provided |
Incident Number | incident_number |
string |
None provided |
Incident Key | incident_key |
string |
None provided |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}
In This Document