ConnectWise PSA integration
Last updated
Was this helpful?
Last updated
Was this helpful?
Our ConnectWise PSA integration enables the automation of PSA tasks. Use the ConnectWise PSA API within Rewst workflows to perform actions such as managing agreements, contacts, and tickets.
Here’s just a taste of what you can automate with relevant Crates, after you've set up your ConnectWise PSA integration:
Add your child organizations, also known as customers, to Rewst.
User onboarding and offboarding
Categorize tickets using OpenAI
Rewst has a number of tasks that can be performed using the ConnectWise Manage API, all of which require different permissions. You can review the for more information.
Create a security role in ConnectWise PSA
Navigate to System > Security Roles.
Click the + in the top left of your screen.
Name the Security Role Rewst API.
Click the save icon.
Set your permission as per this document.
Create an API account
Note that you'll need to be signed in to ConnectWise to view the documentation.
Create an API member
Navigate to System > Members > API Members in ConnectWise PSA.
Click + to create a new API member.
Enter a Member ID and Member Name. We suggest naming each of these Rewst.
Select Rewst API as your Role ID.
Select your highest Level, such as Corporate (Level 1).
Select a Location, Department, Name, and Default Territory, as per your company guidelines.
Click the Save icon at the top.
Click on the Rewst API member.
Click API Keys +.
Add a new API Key.
Add Rewst API as the Description.
Click Save.
Copy and save the public and private key in a secure location. You'll need these to move on to the rest of the setup steps in Rewst.
Navigate to Configuration > Integrations in the left side menu of your Rewst platform.
Click on the integration tile to launch the configuration setup page.
In the Configuration form, enter the following into the relevant fields:
The copied API Member ID
The company ID used when logging into ConnectWise PSA
The Hostname for ConnectWise PSA
The Private & Public API Key.
Optionally, change the Company Query Conditions to filter what companies are returned by the API
Click Save Configuration.
Other Configurations
Note that this form asks for information about your RMM / M365 settings as well. While this form can be completed again separately, we recommend that you also set up the integration for Microsoft Graph and your RMM at this same time.
Pod Authorization
Note that pods do not allow the use of the fat client due to authorization pass-through issues. This means that you can use the web client to access pods.
To configure the connection between your pods and Rewst, follow the below steps.
Login to ConnectWise Manage as a user that has access to the Setup Tables. This is likely an admin account.
Click the System icon on the bottom left of the ConnectWise Manage UI.
Click on the Setup Tables menu that appears.
Enter \*api\
in the table filter. Your returned result should be Manage Hosted API.
Click Add and use the below settings:
Description - Enter Rewst
Screen - For our example, we use Service Tickets
Select Pod.
Update the URL
You will need to add your own org_id
to the URL above. This can be obtained by going to Rewst and looking at the URL. [cw_id]
should be left as-is.
Click the Settings icon in the top right corner of your screen.
Select Pod Configuration.
Move the Rewst pods to the Displayed table.
Firefox Dynamic State Partitioning
An issue arises with Firefox's Dynamic State Partitioning where the default network.cookie.cookieBehavior
value of 5 rejects (known) trackers and partitions third-party storage, hindering the authentication process and causing a logged GraphQL error. This issue also occurs with embedded forms.
Firefox users must set network.cookie.cookieBehavior
to 4 for successful pod authentication.
You'll have a workflow called [Rewst Master v3] Pods: Technician Toolbox
within your organization.
Let's imagine you have a ticket that has had its associated pod workflow execution expire (or fail for one reason or another). If you attempt to view the pod in the ticket you'll see something along the lines of:
To execute a new instance of the pod, click on the Links dropdown in the ticket and choose Rewst - Start Pod on this Ticket.
After you have used this button, a web page will open and close. This will send a request to the Live Link trigger and start a new execution for that ticket. Allow some time to pass for the ticket to update. You should see the pod populate once the execution has gone through.
Query string parameters and conditions allow you to filter results in ConnectWise PSA Actions. By using specific symbols and expressions, you can pinpoint the data you need.
=
: Matches exactly
!=
: Does not match
<, <=, >, >=
: Relational operators
contains, like, in, not
: Specific condition operators
Learn how to apply query string parameters and conditions in real-world scenarios.
Action: List Companies
Query Condition: name="Test Rewst"
Explanation: Easily locate companies by name.
Action: List Service Tickets
Query Condition: board/name="Integration"
Explanation: Organize tickets by board names for efficient processing.
Action: List Contacts
Child Condition: communicationItems/value like "john@Outlook.com" AND communicationItems/communicationType="Email"
Explanation: Target contacts based on communication preferences.
Accessing data within nested objects requires a specific approach.
Syntax: Use a forward slash /
Example: communicationItems/value
Use Case: When you need to extract specific attributes from nested entities, such as communication items within contacts.
Different conditions serve different purposes. Mastering these conditions enables you to build complex and tailored queries.
Strings: Match text patterns (Summary = "string"
)
Integers: Locate numerical values (Board/Id = 123
)
Boolean: Filter by true/false conditions (ClosedFlag = True
)
Datetimes: Sort by date and time (LastUpdated = [2016-08-20T18:04:26Z]
)
Operators: Define relational/logical conditions (Summary Not Contains "Low Priority"
)
Logic Operators: Combine multiple conditions (AND, OR
)
Reference Conditions: Access fields within referenced objects (manufacturer/name
)
Log in to ConnectWise PSA.
Navigate to System > Members.
Click API Members. Here, you'll find settings specific to API interactions and configurations.
Under the API Members tab, locate and select the user associated with Rewst's integration.
After selecting the Rewst user:
Navigate to the API Logs tab.
Click Start Debug Mode.
In the Debug Mode dialog:
Enter length of time (e.g. 5
) in the Minutes field. This will capture logs for the specified duration.
Click Ok.
Replicate the issue or process you are troubleshooting
Return to the API Logs tab.
Click Download Logs. Once downloaded, you can review these logs, and provide to the ROC for troubleshooting assistance.
This can be done by following .
In the integrations page, search for ConnectWise PSA
.
Rewst will do a quick validation of your input. Once completed, you'll see a new section beneath the configuration form for. Complete your mapping as desired.
Once the integration has been configured within Rewst, we can use the Rewst Crate: Configure Organization Variables to configure your own custom settings and how Rewst should interact with ConnectWise PSA. Our Guide for that Crate can be found here:
Origin -
URL -
Consult the official Firefox documentation for more information: .\
The following tables outline the various actions the ConnectWise PSA integration can take within Rewst, grouped by their security roles in ConnectWise, and each of their required permission levels to be able to execute them in workflows. We also have a generic request action, that will require any relevant scopes for what it’s being used for. For more information on the ConnectWise API and its required permissions, please refer to the .