Connect an AI assistant
Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.
The catalog did not load. Refresh the page to try again.
Loading…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown.
Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Cases / Delete
- Article
- 2 minutes to read
Operation Information
This operation will delete the Case specified.
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 oAuth 2.0.
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 oAuth 2.0 in the Type pick list;
- Give the oAuth 2.0 KeySafe key a Title (this is the name / identifier for the oAuth 2.0 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 |
|---|---|---|
| Client Id | string |
Application Client Id |
| Client Secret | string |
Application Client Secret |
| oAuth Scope | string |
Application oAuth Scope |
| Authorize URL | string |
Application Authorize URL |
| Access URL | string |
Application Access UR |
| Response Type | string |
Application Response Type |
| Additional Params | string |
Application Additional Params |
| Additional Access Token Params | string |
Application Additional Access Token Request Params |
| Grant Type | string |
Application Grant Type |
| Refresh URL | string |
Application Refresh URL |
| Refresh Grant Type | string |
Application Refresh Grant Type |
| Refresh Body | string |
Application Refresh Body |
| Revoke URL | string |
Token Revoke URL |
| Token | string |
Authentication Token |
| Refresh Token | string |
Refresh Token |
| API Endpoint | string |
Optional API Endpoint |
Tip
In order for the Authorization to go through correctly the 'API Endpoint' field must be filled in with the URL from your Dynamics instance for example: 'https://[YOUR ORG NUMBER].crm11.dynamics.com'.
- The Authorize URL should be set to 'https://login.microsoftonline.com/common/oauth2/v2.0/authorize'.
- The Access URL and Refresh URL should be set to: 'https://login.microsoftonline.com/common/oauth2/v2.0/token'.
- Set the scope to 'https://org4f1ec541.crm11.dynamics.com/.default offline_access'.
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 oAuth 2.0 account, so you will need to manage these workflows accordingly.
Input Parameters
| Display Name | ID | Type | Description | Required | Supported Values |
|---|---|---|---|---|---|
| Case ID | incidentId |
string |
The Case ID | No | None provided |
| Case ID Lookup | caseIdLookup |
string |
If the ID is not know this field will present a list of available Cases. | No | None provided |
Output Parameters
| Display Name | ID | Type | Description |
|---|---|---|---|
| Status | status |
string |
Status of the operation |
| Error | error |
string |
Error returned by the Teams operation |
| Ticket Number | ticketNumber |
string |
The Case Ticket Number |
| Title | title |
string |
The Title assocaited with the Case |
| Case Email Address | email |
string |
The Email Address assocaited with the Case |
| Case Priority | priorityCode |
string |
Case Priority Code |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}