> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/subworkflows/rewst-process-psa-create-ticket.md).

# \[REWST - PROCESS] PSA: Create Ticket

This workflow acts as a universal ticket creation tool that routes requests to the correct PSA system. It’s great for MSPs who need consistent ticketing across different triggers without hardcoding PSA-specific logic. It identifies the right platform, hands off the request to a matching subworkflow, and returns a standard response, making your automations flexible and vendor-agnostic even if your PSA changes later.

This workflow contains 12 tasks.

### Inputs

* **psa** - string
  * Ability to override PSA. Set to organization varilable `default_psa` is not supplied
* **board** - string
  * PSA Board ID
* **summary** - string
  * Summary
* **company\_id** - string
  * PSA Company ID
* **contact\_id** - string
  * PSA Contact ID
* **category\_one** - string
  * Set category 1 for Halo PSA
* **category\_two** - string
  * Set category 2 for Halo PSA
* **category\_four** - string
  * Set category 4 for Halo PSA
* **child\_company** - string
  * Child Company ID
* **contact\_email** - string
  * Contact Email
* **category\_three** - string
  * Set category 3 for Halo PSA
* **ticket\_item\_id** - string
  * Item ID to attach ticket to
* **ticket\_type\_id** - string
  * Ticket Type ID
* **ticket\_priority** - string
  * Ticket Priority
* **ticket\_subtype\_id** - string
  * TIcket Subtype ID
* **initial\_description** - string
  * Initial description on ticket
* **default\_status\_override** - string
  * Override Ticket Status ID

### Outputs

* **automation\_log**: Standardized Rewst automation log
* **ticket\_id**: Ticket ID of the created ticket.
* ticket\_data: Ticket object turned from the PSA

### Key tasks

* **kaseya\_bms\_create\_ticket**: Creation/initialisation
* **determine\_provider**: Core integration: noop
* **begin**: Core integration: noop
* **freshdesk\_create\_ticket**: Creation/initialisation
* **cwpsa\_create\_ticket**: Creation/initialisation

### Jinja examples

#### Example 1

```jinja
{{ - CTX.board - }}
```

Used in input parameter 'board'

#### Example 2

```jinja
{{ - CTX.summary - }}
```

Used in input parameter 'summary'


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/documentation/automations/subworkflows/rewst-process-psa-create-ticket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.