# Modules
As mentioned in the previous page, a ticket is created by the user first going thru a "pipeline" of modules defined by you. These modules are ran in order from top to bottom and culminates in a ticket being created!
Modules can be configured with conditions to only run under certain circumstances using "conditionals". If you've ever dabbled with code you can see this as `if statements`. If you've never dabbled with code you can see this as `if this has happened, do this` .
This conditional setup will only run the module if the user initiating the ticket is me (family friendly)
Most (but not all) modules export `variables` that can be used elsewhere. These variables are accessed by typing `{{variable_name}}`. These variables can be used in these conditional statements, and clicking the blue variable icon to the left of the text box will show you a list of all the variables that are accessible to that specific module.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.threadwatcher.xyz/features/tickets/modules.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.