ConnectWise CPQ (Sell) icon

ConnectWise CPQ (Sell)

Interact with ConnectWise CPQ (Sell) API

Actions24

Overview

This node integrates with the ConnectWise CPQ (Sell) API, enabling users to query and manipulate various resources related to sales quoting and configuration. It supports multiple resource types such as quotes, quote items, customers, tabs, terms, recurring revenue, tax codes, templates, and users.

Typical use cases include:

  • Retrieving filtered lists of quotes or quote items based on complex conditions.
  • Managing customer data linked to quotes.
  • Accessing and modifying quote-related metadata like tabs, terms, and templates.
  • Handling recurring revenue and tax code information for financial accuracy.
  • Querying user information within the ConnectWise CPQ system.

For example, a user might want to fetch all quotes updated after a certain date that contain specific products or belong to particular customers, using advanced filtering conditions.

Properties

Name Meaning
Conditions Advanced raw condition string to filter results. Supports operators like <, <=, =, !=, >, >=, contains, like, in, not. Multiple conditions can be joined with and/or. Strings must be quoted; datetimes in brackets.
Condition Builder Visual builder for creating multiple filter conditions. Each condition includes: Field (name or expression path), Operator (e.g., =, !=, contains), optional Reference Subfield, Value(s), and Value Type (Boolean, Datetime, Integer, List, String). All conditions are joined by the selected Logic.
Logic How to join multiple conditions from the Condition Builder: AND or OR.
Include Field Names Select which fields to include in the output. Options are dynamically loaded based on the chosen resource. Users can also specify field names via expressions.
Show All Versions Boolean flag indicating whether to include all versions of records, including deleted or archived ones, where supported by the API.
Return All Boolean flag to return all matching results without limiting the number.
Limit Maximum number of results to return when Return All is false. Minimum value is 1. Default is 50.
Page Size Number of results per page fetched from the API. Auto-managed based on Limit and Return All settings but can be set manually between 1 and 1000.

Output

The node outputs JSON data representing the queried or manipulated ConnectWise CPQ resources. The structure depends on the selected resource and operation but generally includes arrays of objects corresponding to entities like quotes, quote items, customers, etc.

  • The json output contains the main data retrieved or affected.
  • If errors occur during processing individual items and "Continue On Fail" is enabled, error details are included in the output paired with the respective input item.
  • The node does not explicitly output binary data.

Dependencies

  • Requires an API key credential for authenticating with the ConnectWise CPQ (Sell) API.
  • The node relies on the external ConnectWise CPQ API service.
  • No additional environment variables or configurations beyond the API credential are indicated.

Troubleshooting

  • Unsupported Resource Error: If a resource other than the predefined ones (quotes, quoteItems, quoteCustomers, quoteTabs, quoteTerms, recurringRevenue, taxCodes, templates, user) is specified, the node throws an error. Ensure the resource name is valid.
  • Condition Syntax Errors: When using the raw conditions string, improper syntax (e.g., missing quotes around strings, incorrect datetime format) may cause API errors or no results. Use the Condition Builder for safer condition creation.
  • API Limits and Pagination: Setting very high limits or page sizes may lead to timeouts or rate limiting by the API. Adjust Return All, Limit, and Page Size accordingly.
  • Field Inclusion Issues: Selecting invalid or unsupported fields in "Include Field Names" may result in incomplete or failed responses. Use the dynamic loader to pick valid fields.
  • Error Handling: Enable "Continue On Fail" to allow the node to process subsequent items even if some fail, capturing error messages in the output.

Links and References

Discussion