The “Ticket created” trigger node lets you automatically start a Flow Builder workflow when a new ticket is created in SleekFlow.

Use this trigger when you want a workflow to run follow-up actions immediately after ticket creation. For example, you can use it to:

• Send new ticket data to an external system
• Notify an internal support team
• Route tickets based on ticket type, status, priority, or requester details
• Use ticket data in Webhook, API request, message, or condition nodes

Please note that the “Ticket created” trigger node only starts a workflow when a new ticket is successfully created. It does not run when an existing ticket is viewed, edited, or updated.

Before you begin

Before using the “Ticket created” trigger node, make sure:

• You have access to Flow Builder
• Your workspace has access to the Tickets feature
• You know where new tickets are created in SleekFlow
• If you want to send ticket data to an external system, you have prepared the API endpoint, authentication method, and expected payload format

Set up the “Ticket created” trigger node

Click on the “Ticket created” trigger node to open up its node form, which will appear on the right side of the screen

The node form contains the following field for you to set up the trigger:

• Filter tab
  • Enrollment conditions: When toggled on, you can set specific conditions at the “Filter” tab that the customer must meet in order to be enrolled into the flow. 

The “Ticket created” trigger starts the workflow when a new ticket is successfully created in SleekFlow.

The workflow triggers when:

• A new ticket is created in SleekFlow
• Ticket creation is completed successfully
• The trigger runs with no noticeable delay

The workflow does not trigger when:

• No new ticket is created
• Ticket creation fails
• An existing ticket is only viewed, edited, or updated

Use ticket variables in later nodes

After the workflow starts, you can use ticket variables in later nodes, such as Webhook, API request, message, condition branch, or internal notification nodes.

Ticket variables allow the workflow to use the actual data from the newly created ticket and pass that data into other workflow steps or external systems.

The following ticket variables are available:

When the flow runs, the variable values will match the data from the newly created ticket.

You can use these variables in:

• Messages
• Conditions
• Webhook or API request payloads
• Internal notifications
• Data recording or syncing scenarios

Send ticket data via Webhook or API

You can add a Webhook or API request node after the “Ticket created” trigger node to send new ticket data to an external system.

In the Webhook or API request node, insert ticket variables into the request body.

Example payload:

{
  "ticket_id": "{{ticket.id}}",
  "subject": "{{ticket.subject}}",
  "description": "{{ticket.description}}",
  "type": "{{ticket.type}}",
  "status": "{{ticket.status}}",
  "priority": "{{ticket.priority}}",
  "requester_name": "{{ticket.requester.name}}",
  "requester_email": "{{ticket.requester.email}}",
  "requester_phone": "{{ticket.requester.phone}}"
}

When a new ticket is created:

• The workflow starts automatically
• The Webhook or API request node runs after the trigger
• The variables in the request payload are rendered with the corresponding ticket data
• The external system receives the new ticket details

What happens when the flow runs

When a new ticket is successfully created, SleekFlow starts the workflow from the “Ticket created” trigger node.

The workflow can then use the new ticket’s data in later nodes. For example, it can send ticket details to an external system, notify an internal team, or route the ticket based on ticket fields.

The “Ticket created” trigger node only starts a workflow for new tickets. It does not create tickets, update tickets, or run when existing tickets are changed.

Best practices

• Use this trigger only for new ticket creation: Use the “Ticket created” trigger when the workflow should start after a new ticket is created. It will not run for existing ticket updates.
• Use ticket variables from the trigger: Use variables from the “Ticket created” trigger whenever possible. This helps make sure the workflow uses the correct ticket data.
• Prepare external API details before setup: If you want to send ticket data to an external system, prepare the endpoint, authentication method, and expected payload format before building the workflow.
• Test the flow before publishing: Create a test ticket before publishing the workflow. Check that the workflow starts correctly and that ticket variables are rendered as expected.