[PROD - TASK] Datto PSA: Create Ticket
This workflow functions as a reusable building block that creates tickets in Datto Autotask PSA with proper contact association, enabling MSPs to programmatically generate standardized tickets across various automation scenarios. It's particularly valuable for integrating monitoring alerts with ticket creation, automating customer request handling, standardizing ticket generation across technicians, and incorporating ticket creation into complex workflows like onboarding/offboarding processes. Technically, the workflow first validates contact information by searching Datto PSA's contact database, then creates a properly formatted ticket with all required fields and associations, making it a reliable foundation for any automation that requires ticket generation within your PSA.
This workflow contains 8 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
create_ticket: Creation/initialisation
format_output: Core integration: noop
failed: Core integration: noop
find_contact_id: Datto Autotask PSA integration: List Contacts by Search v2
Jinja examples
Example 1
{{ (CTX.child_company|d) or (CTX.company_id|d) or (ORG.VARIABLES.datto_company_id|d) }}
Task: set_variables | Context: Used in publishing 'company_id'
Example 2
{ - CTX.ticket_type_id|d or ORG.VARIABLES.psa_datto_default_issue_type | d or ORG.VARIABLES.psa_new_user_ticket_type | d - }
Task: set_variables | Context: Used in publishing 'issue_type_id'
Last updated
Was this helpful?