ConnectWise PSA (formerly Manage) provides the structure and functionality you need to run your IT department. Organize your team around a single system, enabling everyone to connect and communicate through a single pane of glass.
D3 SOAR is providing REST operations to function with ConnectWise PSA.
To connect to ConnectWise PSA from D3 SOAR, please follow this part to collect the required information below:
Parameter
Description
Example
Server URL
The URL of a specified ConnectWise PSA instance at the Domain level, which is the same as your ConnectWise PSA web UI URL.
https://na.myconnectwise.net
Company ID
The company ID obtained from ConnectWise.
company_login_id
Public Key
The public key created from ConnectWise UI.
jlyl********pBAb
Private Key
The private key created from ConnectWise UI.
K9MO********fjTD
API Version
The API Version.
3.0
Permission Requirements
Each endpoint in the ConnectWise PSA API requires a certain permission scope. All the commands for this ConnectWise PSA integration will require admin role + level 1. Please refer to Configuring ConnectWise PSA to Work with D3 SOAR for the setup details.
Different combinations of roles and levels may still allow the commands to run successfully, however the returned data will be limited under these circumstances.
Configuring ConnectWise PSA to Work with D3 SOAR
Login to ConnectWise PSA with your own credentials.
Click System > Members.
Add a New Member.
Input fields. Make sure you select Admin for the Role ID field and Corporate (Level 1) for the Level field in order to get full data returned for all the commands. Then click Save to create the member.
Find the member you just created. Navigate to tab API Keys, click + to create a new key.
Enter a description, then click save.
Save the Public Key and Private Key in the proper place. This is the only time you will be able to find your private key, please make sure you store it properly for future use.
Configuring D3 SOAR to Work with ConnectWise PSA
Log in to D3 SOAR.
Find the ConnectWise PSA integration.
Navigate to Configuration on the top header menu.
Click on the Integration icon on the left sidebar.
Type ConnectWise PSA in the search box to find the integration, then click it to select it.
Click + Connection, on the right side of the Connections section. A new connection window will appear.
Configure the following fields to create a connection to ConnectWise PSA.
Connection Name: The desired name for the connection.
Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.
Recipient site for events from connections Shared to Internal Sites: This field appears if you selected Share to Internal Sites for Site to let you select the internal site to deploy the integration connection.
Agent Name (Optional): Specifies the proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.
Description (Optional): Add your desired description for the connection.
Tenant (Optional): When configuring the connection from a master tenant site, you have the option to choose the specific tenant sites you want to share the connection with. Once you enable this setting, you can filter and select the desired tenant sites from the dropdowns to share the connection.
Configure User Permissions: Defines which users have access to the connection.
Active: Check the tick box to ensure the connection is available for use.
System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.
1. Input the Server URL. 2. Input your Company ID. The company ID will be given by ConnectWise PSA when you register the account. 3. Input your Public Key. Please refer to step 7 of Configuring ConnectWise PSA to Work with D3 SOAR to get your public key. 4. Copy the Private Key. Please refer to step 7 of Configuring ConnectWise PSA to Work with D3 SOAR to get your private key. 5. Input the API Version. The default value is 3.0.
Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Please refer to the password vault connection guide if needed.
Connection Health Check: Updates the connection status you have created. A connection health check is done by scheduling the Test Connection command of this integration. This can only be done when the connection is active. To set up a connection health check, check the Connection Health Check tickbox. You can customize the interval (minutes) for scheduling the health check. An email notification can be set up after a specified number of failed connection attempts.
Test the connection.
Click Test Connection to verify the account credentials and network connection. If the Test Connection Passed alert window appears, the test connection is successful. You will see Passed with a green checkmarkappear beside the Test Connection button. If the test connection fails, please check your connection parameters and try again.
Click OK to close the alert window.
Click +Add to create and add the configured connection.
Commands
ConnectWise PSA includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command, you can execute these commands independently for playbook troubleshooting.
The input format of time-related parameters may vary based on your account settings. As a result, the sample data provided in our commands is different from what you see. To set your preferred time format, follow these steps:
Navigate to Configuration > Application Settings. Select Date/Time Format.
Choose your desired date and time format.
After that, you will be able to view your preferred time format when configuring the DateTime input parameters for commands.
Add Ticket Notes
Adds notes to the specified tickets.
READER NOTE
The parameter Ticket IDs is required to run this command.
Run the Fetch Event command to obtain Ticket IDs. Ticket IDs can be found in the raw data at the path $.Results[*].id.
Input
Input Parameter
Required/Optional
Description
Example
Ticket IDs
Required
The ticket ID(s) used to add notes. Ticket IDs can be obtained using the Fetch Event command.
[ 541 ]
Discussion Note
Optional
The option to flag the note as a discussion (detail description) note or not. If you want to add an initial description to the ticket, set this parameter to True. If not specified, the default value is True.
True
Internal Note
Optional
The option to flag the note as an internal analysis note or not. If not specified, the default value is False.
True
Resolution Note
Optional
The option to flag the note as a resolution note or not. If not specified, the default value is False.
True
Note Text
Required
The specified note text.
initiate desc 417f
Output
Return Data
Indicates one of the possible command execution states: Successful, Partially Successful, or Failed.
The Partially Successful state only occurs when a command’s input accepts an array of items (e.g. an array of IP addresses) and one or more items within the array return an error from the API request.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Add Ticket Notes failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Ticket IDs) is invalid.
Error Sample Data
Add Ticket Notes failed.
Status Code: 400.
Message: The value for parameter (Ticket IDs) is invalid.
Create Ticket
Creates a service ticket. If you want to add an initial description onto the ticket, please use the Add Ticket Notes command.
READER NOTE
Company ID is a required parameterto run this command.
Run the List Companies command to obtain the Company ID. The Channel ID can be found in the raw data at the path $.Results[*].id.
Board Name, Status and Team are optional parameters to run this command.
Run the List Boards command to obtain the Board Name. Board Names can be found in the raw data at the path $.Results[*].name.
Run the List Board Statuses command to obtain the Status. Status can be found in the raw data at the path $.Results[*].name.
Run the List Board Teams command to obtain the Team. Teams can be found in the raw data at the path $.Results[*].name.
Input
Input Parameter
Required/Optional
Description
Example
Summary
Required
The summary for the service ticket.
test service ticket ***m
Company ID
Required
The ID of the specified company for which the ticket is created. Company ID can be obtained using the List Companies command.
26
Board Name
Optional
The name of the board in which the ticket is created. Board Name can be obtained using the List Boards command. If not specified, the default Board will be used.
Integration
Status
Optional
The status of the ticket to be created. Status can be obtained using the List Board Statuses command. If not specified, the default Board status will be used.
New
Priority
Optional
The priority of the ticket to be created. If not specified, the default Priority is Priority 3 - Normal Response.
Priority 2 - Quick Response
Urgency
Optional
The urgency of the ticket to be created. If not specified, the default Urgency is Medium.
High
Impact
Optional
The impact of the ticket to be created. If not specified, the default Impact is Medium.
High
Ticket Contact Name
Optional
The contact person’s name of the ticket to be created. If not specified, the default contact is Company Contact.
Mike *******
Ticket Contact Phone Number
Optional
The phone number of the contact person of the ticket to be created. If not specified, the default contact is Company Contact.
516-213****
Ticket Contact Email Address
Optional
The email address of the contact person of the ticket to be created. If not specified, the default contact is Company Contact.
mike.****@example.com
Team
Optional
The name of the board team of the ticket to be created. Team can be obtained using the List Board Teams command. If not specified, the default Team will be used.
Stand** Team
Additional Fields
Optional
The additional fields you want to add to the ticket.
{
"city": "LA",
"stateIdentifier": "CA",
"zip": "991**",
"source": {
"name": "email"
}
}
Output
Return Data
Indicates one of the possible command execution states: Successful or Failed.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Create Ticket failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Company ID) is invalid.
Error Sample Data
Create Ticket failed.
Status Code: 400.
Message: The value for parameter (Company ID) is invalid.
Delete Tickets
Deletes the specified service ticket(s) by ticket ID(s).
READER NOTE
The parameter Ticket IDs is required to run this command.
Run the Fetch Event command to obtain Ticket IDs. Ticket IDs can be found in the raw data at the path $.Results[*].id.
Input
Input Parameter
Required/Optional
Description
Example
Ticket IDs
Required
The ticket ID(s) to delete. Ticket IDs can be obtained using the Fetch Event command.
[ 514 ]
Output
Return Data
Indicates one of the possible command execution states: Successful, Partially Successful, or Failed.
The Partially Successful state only occurs when a command’s input accepts an array of items (e.g. an array of IP addresses) and one or more items within the array return an error from the API request.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
SAMPLE DATA
CODE
Successful
Raw Data
The primary response data from the API request.
SAMPLE DATA
CODE
{
"Results": [
{
"TicketID": 514,
"Message": "The ticket is deleted successfully"
}
]
}
Result
Provides a brief summary of outputs in an HTML formatted table.
SAMPLE DATA
Results
{'TicketID': 514, 'Message': 'The ticket is deleted successfully'}
Error Handling
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Delete Tickets failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Ticket IDs) is invalid.
Error Sample Data
Delete Tickets failed.
Status Code: 400.
Message: The value for parameter (Ticket IDs) is invalid.
Fetch Event
Returns service ticket(s) as Event(s) from the ConnectWise PSA based on specified criteria. The service tickets are sorted by updated time in descending order.
Input
Input Parameter
Required/Optional
Description
Example
Start Time
Optional
The start time of the time range to fetch service tickets by the updated time, in UTC time. If not specified, the default start time is from the beginning of the 1900s.
2024-04-15 00:00
End Time
Optional
The end time of the time range to fetch service tickets by the updated time, in UTC time. If not specified, the default end time is the current time.
2024-04-16 00:00
Number of Event(s) Fetched
Optional
The maximum number of the most recent service tickets to fetch. If not specified, all service tickets matching search criteria will be returned. Note: If the input limit value is too large, it may affect system performance when returning a large volume of results. The available number is an integer between 1 and 1000. If not specified, all service tickets matching the search conditions will be returned.
3
Status
Optional
The service tickets that are filtered by status. If not specified, service tickets in any status will be returned. Status can be obtained using the List Board Statuses command.
New (not *****)
Priority
Optional
The service tickets that are filtered by priority. If not specified, service tickets with any priority will be returned.
Priority 1 - Emergency Response
Impact
Optional
The service tickets that are filtered by impact. If not specified, service tickets with any impact will be returned.
High
Urgency
Optional
The service tickets that are filtered by urgency. If not specified, service tickets with any urgency will be returned.
Please note that Fetch Event commands require event field mapping. Field mapping plays a key role in the data normalization process part of the event pipeline. Field mapping converts the original data fields from the different providers to the D3 fields which are standardized by the D3 Model. Please refer to Event and Incident Intake Field Mapping for details.
To customize field mapping, click + Add Field and add the custom field of your choice. You can also remove built-in field mappings by clicking x. Please note that two underscore characters will automatically prefix the defined Field Name as the System Name for a custom field mapping. Additionally, if an input Field Name contains any spaces, they will automatically be replaced with underscores for the corresponding System Name.
As a system integration, the ConnectWise PSA integration has some pre-configured field mappings for default field mapping.
Default Event Source The Default Event Source is the default set of field mappings that are applied when this fetch event command is executed. For out-of-the-box integrations, you will find a set of field mapping provided by the system. Default event source provides field mappings for common fields from fetched service ticket(s). The default event source has a “Main Event JSON Path” (i.e., $.Results) that is used to extract a batch of events from the response raw data. Click Edit Event Source to view the “Main Event JSON Path”.
Main Event JSON Path: $._embedded.eventResources The Main Event JSON Path determines the root path where the system starts parsing raw response data into D3 event data. The JSON path begins with $, representing the root element. The path is formed by appending a sequence of child elements to $, each separated by a dot (.). Square brackets with nested quotation marks ([‘...’]) should be used to separate child elements in JSON arrays.
For example, the root node of a JSON Path is Results. The child node denoting the Board Name field would be board.name. Putting it together, the JSON Path expression to extract the Board Name is $.Results.board.name.
The pre-configured field mappings are detailed below:
Field Name
Source Field
Document ID
.id
Start Time
._info.dateEntered
Description
.summary
Board Name
.board.name
Event Type
.recordType
Priority
.priority.name
Impact
.impact
Urgency
.severity
Status
.status.name
Company Name
.company.name
Site Name
.site.name
Contact Name
.contact.name
Contact Email
.contactEmailAddress
Contact Phone Number
.contactPhoneNumber
Type Name
.type.name
Team Name
.team.name
Service Location
.serviceLocation.name
Source
.source.name
location
.location.name
Department
.department.name
SLA
.sla.name
SLA Status
.slaStatus
Created By
._info.enteredBy
Updated By
._info.updatedBy
Updated Time
._info.lastUpdated
Escalation Time
.escalationStartDateUTC
READER NOTE
The Unique Event Key field mapping is used to prevent duplicate event ingestions. D3 SOAR will check if the value of a selected JSON path matches any Unique Event Key of previously ingested events. If a match is found, the event will be dismissed. If no match is found, an event will be created. However, if no Unique Event Key is mapped, then the hash value from the event pending ingestion will be used to check for any matches with existing events. If no match is found, the event will be created.
Unlike most other D3 SOAR integrations, the ConnectWise PSA integration’s Fetch Event command’s Default Event Source mapping does not include Unique Event Key in order to fetch the same fetched service ticket(s) with multiple updates.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Fetch Event failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Number of Event(s) Fetched) is invalid.
Error Sample Data
Fetch Event failed.
Status Code: 400.
Message: The value for parameter (Number of Event(s) Fetched) is invalid.
Get Tickets
Retrieves service ticket(s) by ticket ID(s).
READER NOTE
The parameter Ticket IDs is required to run this command.
Run the Fetch Event command to obtain Ticket IDs. Ticket IDs can be found in the raw data at the path $.Results[*].id.
Input
Input Parameter
Required/Optional
Description
Example
Ticket IDs
Required
The ticket ID(s) specified to retrieve details. Ticket ID can be obtained using the Fetch Event command.
[ 515 ]
Output
Return Data
Indicates one of the possible command execution states: Successful, Partially Successful, or Failed.
The Partially Successful state only occurs when a command’s input accepts an array of items (e.g. an array of IP addresses) and one or more items within the array return an error from the API request.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Get Tickets failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Ticket IDs) is invalid.
Error Sample Data
Get Tickets failed.
Status Code: 400.
Message: The value for parameter (Ticket IDs) is invalid.
List Boards
Retrieves the list of boards. The returned boards are sorted alphabetically.
Input
Input Parameter
Required/Optional
Description
Example
Board Name
Optional
The full or partial name of the board to retrieve. If not specified, all boards will be returned.
Integration
Business Unit
Optional
The name of the business unit in which to retrieve boards. If not specified, boards in any business unit will be returned.
Integration
Location
Optional
The name of the location in which to retrieve boards. If not specified, boards in any location will be returned.
Tampa ******
Output
Return Data
Indicates one of the possible command execution states: Successful or Failed.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
List Boards failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 401.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: Unauthorized.
Error Sample Data
List Boards failed.
Status Code: 401.
Message: Unauthorized.
List Board Statuses
Retrieves the list of all statuses of the specified board. The returned board statuses are sorted alphabetically.
READER NOTE
Board ID is a required parameterto run this command.
Run the List Boards command to obtain the Board ID. Board ID can be found in the raw data at the path $.Results[*].id.
Input
Input Parameter
Required/Optional
Description
Example
Board ID
Required
The ID of the board to retrieve statuses. Board ID can be obtained using the List Boards command.
2
Output
Return Data
Indicates one of the possible command execution states: Successful or Failed.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
List Board Statuses failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 401.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: Unauthorized.
Error Sample Data
List Board Statuses failed.
Status Code: 401.
Message: Unauthorized.
List Board Teams
Retrieves the list of all teams of the specified board. The returned board teams are sorted alphabetically.
READER NOTE
Board ID is a required parameterto run this command.
Run the List Boards command to obtain the Board ID. Board ID can be found in the raw data at the path $.Results[*].id.
Input
Input Parameter
Required/Optional
Description
Example
Board ID
Required
The ID of the board to retrieve teams. Board ID can be obtained using the List Boards command.
2
Output
Return Data
Indicates one of the possible command execution states: Successful or Failed.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
List Board Teams failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 401.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: Unauthorized.
Error Sample Data
List Board Teams failed.
Status Code: 401.
Message: Unauthorized.
List Companies
Retrieves the list of companies. The returned companies are sorted alphabetically.
Input
Input Parameter
Required/Optional
Description
Example
Company Name
Optional
The full or partial name of the company to retrieve. If not specified, all companies will be returned.
Microsoft
Status
Optional
The status of the companies to retrieve. If not specified, companies in any status will be returned.
Active
Type
Optional
The type of the companies to retrieve. If not specified, companies of any type will be returned.
Partner
Output
Return Data
Indicates one of the possible command execution states: Successful or Failed.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
List Companies failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 401.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: Unauthorized.
Error Sample Data
List Companies failed.
Status Code: 401.
Message: Unauthorized.
Update Tickets
Updates the specified ticket(s).
READER NOTE
The parameter Ticket IDs is required to run this command.
Run the Fetch Event command to obtain Ticket IDs. Ticket IDs can be found in the raw data at the path $.Results[*].id.
Company ID, Board Name, Status and Team are optional parameters to run this command.
Run the List Companies command to obtain the Company ID. Company IDs can be found in the raw data at the path $.Results[*].id.
Run the List Boards command to obtain the Board Name. Board Names can be found in the raw data at the path $.Results[*].name.
Run the List Board Statuses command to obtain the Status. Status can be found in the raw data at the path $.Results[*].name.
Run the List Board Teams command to obtain the Team. Teams can be found in the raw data at the path $.Results[*].name.
Input
Input Parameter
Required/Optional
Description
Example
Ticket IDs
Required
The ID(s) of the service ticket(s) to update. Ticket ID can be obtained using the Fetch Event command.
[ 543 ]
Summary
Optional
The updated summary for the service ticket(s).
update service ticket 417 13:10
Company ID
Optional
The ID of the company to be updated to the ticket(s). Company ID can be obtained using the List Companies command.
26
Board Name
Optional
The Name of the board to be updated to the ticket(s). Board Name can be obtained using the List Boards command.
Integration
Status
Optional
The status to be updated to the ticket(s). Status can be obtained using the List Board Statuses command.
New
Priority
Optional
The priority to be updated to the ticket(s).
Priority 2 - Quick Response
Urgency
Optional
The urgency to be updated to the ticket(s).
High
Impact
Optional
The impact to be updated to the ticket(s).
High
Ticket Contact Name
Optional
The contact person’s name to be updated to the ticket(s).
Mike *******
Ticket Contact Phone Number
Optional
The phone number of the contact person to be updated to the ticket(s).
516-213****
Ticket Contact Email Address
Optional
The email address of the contact person to be updated to the ticket(s).
mike.****@example.com
Team
Optional
The name of the board team to be updated to the the ticket(s). Team can be obtained using the List Board Teams command.
Stand** Team
Additional Fields
Optional
The additional fields to be updated to the ticket(s).
{ "city": "LA",
"stateIdentifier": "CA",
"zip": "991**",
"source":{"name":"email"}
}
Output
Return Data
Indicates one of the possible command execution states: Successful, Partially Successful, or Failed.
The Partially Successful state only occurs when a command’s input accepts an array of items (e.g. an array of IP addresses) and one or more items within the array return an error from the API request.
The Failed state can be triggered by any of the following errors:
A connection issue with the integration
The API returned an error message
No response from the API
You can view more details about an error in the Error tab.
Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The errortab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.
Parts in Error
Description
Example
Failure Indicator
Indicates the command failure that happened at a specific input and/or API call.
Update Tickets failed.
Status Code
The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the ConnectWise PSA portal. Refer to the HTTP Status Code Registry for details.
Status Code: 400.
Message
The raw data or captured key error message from the integration API server about the API request failure.
Message: The value for parameter (Ticket IDs) is invalid.
Error Sample Data
Update Tickets failed.
Status Code: 400.
Message: The value for parameter (Ticket IDs) is invalid.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.