[REWST - TASK] Connectwise PSA: Create Ticket

This workflow automates the full ticket creation process in ConnectWise PSA, handling contact validation, agreement selection, and ticket formatting. MSPs can use it to standardize ticket creation across use cases like alert-to-ticket automation, onboarding, or external system triggers. It pulls agreement info, checks contact details, formats the ticket, and adds metadata—making it a reliable, reusable component that speeds up building more complex automations.

This workflow contains 14 tasks.

Inputs

• board - string

• summary - string

• company_id - string

• contact_id - string

• category_one - string

• category_two - string

• category_four - string

• child_company - string

• contact_email - string

• category_three - string

• ticket_item_id - string

• ticket_type_id - string

• ticket_priority - string

• ticket_subtype_id - string

• initial_description - string

• default_status_override - string

Outputs

• automation_log: Standardized Rewst automation log

• success: Boolean; States if workflow was successful.

• ticket_id: Returns the ticket ID of the created ticket.

• ticket_data: Return the ticket object of the created ticket.

Key tasks

• list_agreements: ConnectWise PSA integration: List Agreements

• check_contact_id_or_email: Validation/verification

• summary_length_check: Validation/verification

• failed: Core integration: noop

• create_service_ticket_with_agreement: Creation/initialisation

Jinja examples

Example 1

{{ CTX.contact_email|d }}

Used in the contact_email provided transition condition to check if the contact needs resolved by email.

Expression 2: Contact ID Check

Example 2

{{ CTX.contact_id|d }}

This expression retrieves a contact ID from the workflow context, typically used in transition conditions to determine if a valid contact was found in a previous step. It includes a default filter (|d) to gracefully handle cases where the contact ID doesn't exist, preventing workflow errors.