[REWST - TASK] Halo PSA: Create Ticket

This workflow serves as a fundamental building block that automates ticket creation in Halo PSA, enabling MSPs to programmatically generate tickets from external triggers or as part of larger process chains. MSPs will find this particularly valuable for scenarios like auto-generating tickets from monitoring alerts, customer portal submissions, email-to-ticket conversion, or integrating with other platforms like RMMs that lack native Halo PSA connections. Technically, the workflow first retrieves team and user information from Halo PSA to ensure proper ticket routing, then dynamically creates tickets with appropriate assignments based on input parameters, allowing for consistent ticket creation with standardized fields and categorization that maintains your service desk workflow integrity.

This workflow contains 9 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

• BEGIN: Core integration: noop

• format_output: Core integration: noop

• check_for_team_match: Validation/verification

• halo_list_teams: HaloPSA integration: List Teams

• failure_catch: Core integration: noop

Jinja examples

Example 1

{{- CTX.halo_psa_ticket.id | d -}}

Used in publishing 'ticket_id'

Example 2

{{- CTX.halo_psa_ticket | d -}}

Used in publishing 'ticket_data'