> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Add Ticket Tag

> Automatically tag tickets based on smart action results or apply tags to all workflow tickets

This action adds tags to tickets in your Autotask system. You can tag tickets conditionally based on smart action results (like marking reoccurring issues) or apply tags to all tickets in a workflow unconditionally.

<Tip>
  Automatically categorize and flag tickets for better organization, filtering, and reporting. Smart actions can trigger conditional tagging, while you can also apply tags broadly across all workflow tickets for consistent labeling.
</Tip>

<Info>
  This action is available only for **Autotask**.
</Info>

## How it works

### Conditional Tagging Mode (Default)

When smart actions like "Check Recurring Issue" identify tickets that meet specific criteria, they automatically generate field updates that include tagging instructions. The Add Ticket Tag action picks up these instructions and applies the appropriate tags.

### Unconditional Tagging Mode

When you enable "Add tag to ALL tickets," the action applies your specified tag to every ticket in the workflow, regardless of previous action results.

### Step-by-Step Process

1. **Determine Tagging Mode:** Check if unconditional tagging is enabled or if there are conditional tag instructions from previous actions
2. **Tag Identification:** Look up the tag by label in Autotask (matched case-insensitively, ignoring leading/trailing spaces). If no tag with that label exists, Neo **creates a new tag** with that exact label rather than failing — see the warning below.
3. **Tag Application:** Apply the tag to the appropriate tickets based on the mode
4. **Confirmation:** Output success messages to the Event History

<Warning>
  Neo does not reject unknown tag labels — if the label you configure doesn't already exist in Autotask, Neo **creates it**. A typo (e.g. `Recuring Issue`) becomes a brand-new tag rather than an error. To avoid cluttering Autotask with unintended tags, create the exact tag you want in Autotask first, then reference that label. Note that in conditional mode Neo never invents the tag *name* — the label always comes from the fixed **Tag name** you configure on the smart action (e.g. "Check Recurring Issue"); the AI only decides which tickets qualify.
</Warning>

## Configuration options

### Add Tag to ALL Tickets

**Enable this option** to tag every ticket in the workflow unconditionally, regardless of previous action results.

### Tag Name

**Required when "Add tag to ALL tickets" is enabled.** The exact label of the tag as it appears in Autotask.

### Smart Action Integration

**Automatic when enabled.** The action automatically picks up tagging instructions from smart actions like "Check Recurring Issue" that determine which tickets should be tagged based on their analysis.

## What you'll get

After the action runs, you'll see:

* **Event History:** Confirmation messages showing which tickets were tagged successfully
* **Tagged Tickets:** Your specified tags applied to the appropriate tickets in Autotask
* **Zero Credits:** This action doesn't consume any credits

## Common use cases

### Conditional Tagging Based on Smart Actions

<Accordion title="Mark Reoccurring Issues">
  **When:** Using "Check Recurring Issue" action to analyze ticket patterns
  **What it does:** Automatically tags tickets identified as reoccurring issues
  **Result:** Tickets with recurring patterns get tagged for special handling or escalation
</Accordion>

<Accordion title="Flag High-Risk Tickets">
  **When:** Using sentiment analysis or triage actions that identify problematic tickets
  **What it does:** Tags tickets that meet specific risk criteria
  **Result:** Problem tickets are automatically flagged for priority attention
</Accordion>

### Unconditional Tagging for Workflow Organization

<Accordion title="Mark All Tickets from Specific Sources">
  **When:** Processing tickets from a particular integration or channel
  **What it does:** Applies a source tag to every ticket in the workflow
  **Result:** Easy filtering and reporting by ticket source
</Accordion>

<Accordion title="Track Workflow Processing">
  **When:** Running any automated workflow on tickets
  **What it does:** Tags all processed tickets with "Auto-Processed" or similar
  **Result:** Clear visibility into which tickets have been through automation
</Accordion>

## Best practices

### Choose the Right Tagging Mode

**Use Conditional Tagging:** When you want tags applied only to tickets that meet specific criteria (recommended for most scenarios)
**Use Unconditional Tagging:** When you want to tag all tickets in a workflow for organizational purposes

### Tag Management

**Pre-create Your Tags:** Neo does not fail on an unknown label — it creates a new tag if one with that label doesn't already exist. Create the tags you intend to use in Autotask first and reference their exact labels, so a mistyped label doesn't silently add an unwanted tag.
**Use Descriptive Tags:** Choose clear, meaningful tag names that help with filtering and reporting
**Plan Your Tagging Strategy:** Decide on consistent tagging conventions before implementing workflows

### Smart Action Integration

**Combine with Analysis Actions:** Use with "Check Recurring Issue," sentiment analysis, or triage actions for intelligent tagging
**Let Smart Actions Drive Tags:** Allow analysis results to determine which tickets get tagged rather than tagging everything

### Monitoring and Troubleshooting

**Check Event History:** Monitor successful tag applications and troubleshoot any failures
**Test with Small Sets:** Start with limited ticket sets to verify tagging works as expected
**Review Tag Application:** Periodically check that tags are being applied correctly in Autotask