Skip to main content

Create ConnectWise Ticket (API)

The Create ConnectWise Ticket action creates a new service ticket in ConnectWise Manage. This is a low-level API action that makes a single API call with the exact parameters you specify.

Single API Call Action

This is a single API call action. You must supply the company, contact, and all other parameters directly. Learn more about the difference between workflow actions and single API call actions.

When to Use This Action

Use this action when:

  • You've already looked up the Company and Contact using query actions
  • You need precise control over ticket field values
  • You're building a custom workflow with specific ticket creation logic

For email-based ticket creation with automatic company/contact lookup, consider using the workflow action Create ConnectWise Ticket instead.

Configuration

Connection

FieldDescription
ConnectWise ConnectionSelect the ConnectWise connection to use.

Basic Information

FieldDescription
SummaryThe ticket summary/title (max 100 characters). Supports template variables.
Initial DescriptionThe initial ticket description that appears in the first note. Supports template variables.

Company & Contact

FieldDescription
CompanyThe ConnectWise Company for the ticket. Required. Lock to select from dropdown, or unlock for dynamic values.
ContactThe ConnectWise Contact for the ticket. Optional.

Classification

FieldDescription
Service BoardThe service board for the ticket. Required.
StatusInitial ticket status. Uses board default if not specified.
TypeService type classification.
Sub-TypeService sub-type (depends on Type).
ItemService item (depends on Board).
PriorityTicket priority level.
SourceHow the ticket was received.

Severity & Impact

FieldDescription
SeveritySeverity level: Low, Medium, or High.
ImpactImpact level: Low, Medium, or High.
Budget HoursBudgeted hours for this ticket.

Error Handling

FieldDescription
Error HandlingAction to take if ticket creation fails.
OptionBehavior
ExceptionStop processing and report the error
BounceReturn the email to the sender
ContinueContinue to the next action
StopStop this rule but allow other rules to process
Stop AllStop all processing for this message

Returned Variables

When you configure Store the results in Variable, the created ticket becomes available:

PropertyTypeDescription
idnumberThe created ticket ID
summarystringTicket summary
recordTypestringRecord type
boardobjectService board (id, name)
statusobjectStatus (id, name)
companyobjectCompany (id, identifier, name)
contactobjectContact (id, name)
priorityobjectPriority (id, name)
typeobjectType (id, name)
subTypeobjectSub-type (id, name)
itemobjectItem (id, name)
sourceobjectSource (id, name)
severitystringSeverity level
impactstringImpact level
budgetHoursnumberBudgeted hours
dateEnteredstringCreation timestamp

Example usage: {{custom.newTicket.id}}

Example Use Cases

Create Ticket After Company Lookup

After using Query ConnectWise Companies:

SettingValue
Company{{custom.company.id}} (unlocked)
Summary{{email.subject}}
Initial Description{{email.body}}
Service Board(Select from dropdown)

Create Ticket with Specific Classification

For a specific workflow:

SettingValue
Company(Select from dropdown)
Service BoardService Desk
TypeBreak/Fix
PriorityPriority 3 - Normal
SourceEmail

Create High-Priority Ticket

For escalated issues:

SettingValue
Company{{custom.company.id}}
Summary[URGENT] {{email.subject}}
Service BoardService Desk
PriorityPriority 1 - Critical
SeverityHigh
ImpactHigh

FAQs

What fields are required?

At minimum:

  • ConnectWise Connection
  • Summary
  • Company
  • Service Board

How do I use dynamic values for Company?

  1. First, use Query ConnectWise Companies to find the company
  2. Store the result in a variable (e.g., custom.company)
  3. In this action, unlock the Company field and enter {{custom.company.id}}

Can I set custom fields?

Custom fields are not directly supported in this action. Use the ConnectWise API action for full custom field control.

What's the difference from the workflow action?

FeatureAPI ActionWorkflow Action
Company lookupManual (use query first)Automatic from email
Contact lookupManualAutomatic from email
AttachmentsNot includedBuilt-in options
Best forCustom workflowsStandard email-to-ticket