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
Adds a task to a ticket in Freshservice.
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 Freshservice.
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 Freshservice in the Type pick list;
- Give the Freshservice KeySafe key a Title (this is the name / identifier for the Freshservice 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 Freshservice account: https://subdomain.freshservice.com |
API Key | string |
Freshservice 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 Freshservice account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
ID | id |
integer |
Ticket ID | Yes | None provided |
Description | description |
string |
The description of the task | No | None provided |
Title | title |
string |
The title/summary of the task | Yes | None provided |
Due Date | due_date |
string |
The due date of the task, in the following format: 2022-10-27T17:00:00+01:00 | No | None provided |
Group ID | group_id |
integer |
The ID of the group the task should be assigned to | No | None provided |
Notify Before | notify_before |
integer |
The number of seconds before the task is due for a notification to be sent | No | None provided |
Status | status |
string |
The status of the task | No | Open, In Progress, Completed |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Status | status |
string |
Operation Response Status (ok/failed) |
Error | error |
string |
Any error returned from Freshservice |
Task ID | id |
integer |
Task ID |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}
In This Document