> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/teamdynamix.md).

# TeamDynamix

Connect to TeamDynamix to create, read, and search tickets, and to trigger workflows when tickets are received.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector   | Authentication |
| ----------- | -------------- |
| TeamDynamix | Credentials    |

### TeamDynamix

Connect to TeamDynamix with an admin service account (BEID + Web Services Key) to create, read, and search tickets, and to trigger workflows from ticket webhooks. Each customer runs their own instance URL.

#### Set up in TeamDynamix

1. Prepare the TeamDynamix account or service that the workflow will access. Grant access to the required resources and operations.
2. **BEID:** The organization's BEID from TDAdmin > Organization Settings. Requires key-based web services to be enabled.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **TeamDynamix**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field    | Required | What to enter                                                                                                                 |
| ---------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Instance URL     | Yes      | Your TeamDynamix Web API base URL, including the /TDWebApi segment. Each TeamDynamix customer runs their own instance domain. |
| BEID             | Yes      | The organization's BEID from TDAdmin > Organization Settings. Requires key-based web services to be enabled.                  |
| Web Services Key | Yes      | The organization's Web Services Key, shown alongside the BEID in TDAdmin.                                                     |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **TeamDynamix** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create Ticket

Create a ticket in TeamDynamix.

#### Inputs

| Field                      | Type            | Required | Description                                                                                                                     |
| -------------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Ticketing Application      | select (string) | Yes      | The TeamDynamix ticketing application to create the ticket in. Options load from the selected connection.                       |
| Title                      | string          | Yes      | The ticket title.                                                                                                               |
| Requestor (UID or Email)   | string          | Yes      | The person the ticket is for: a TeamDynamix person UID (GUID) or an email address to look up.                                   |
| Responsible (UID or Email) | string          | No       | Optionally assign the ticket to a specific person (UID or email). Leave empty to let the ticket type's routing rules assign it. |
| Responsible Group ID       | string          | No       | Optionally assign the ticket to a TeamDynamix group by ID.                                                                      |
| Ticket Type                | select (string) | Yes      | The ticket type for the selected application. Options load from the selected connection.                                        |
| Status                     | select (string) | Yes      | The initial ticket status. Options load from the selected connection.                                                           |
| Priority                   | select (string) | Yes      | The ticket priority. Options load from the selected connection.                                                                 |
| Description                | textarea        | No       | Optional detailed description of the ticket. Default: .                                                                         |
| Account/Department ID      | string          | No       | Optional account/department ID to associate with the ticket.                                                                    |
| Notify Requestor           | boolean         | No       | Send the requestor a notification about the new ticket. Default: false.                                                         |
| Notify Responsible         | boolean         | No       | Send the responsible party a notification about the new ticket. Default: false.                                                 |
| Apply Form Defaults        | boolean         | No       | Apply the ticket form's default field values. Default: true.                                                                    |

#### Outputs

| Field      | Type    | Description                                       |
| ---------- | ------- | ------------------------------------------------- |
| Ticket     | object  | The created ticket as returned by TeamDynamix.    |
| Ticket ID  | integer | The ID of the created ticket.                     |
| Ticket URL | string  | Direct TDNext link to the ticket, when derivable. |

### Get Ticket

Get a TeamDynamix ticket by ID.

#### Inputs

| Field                 | Type            | Required | Description                                                                                             |
| --------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------- |
| Ticketing Application | select (string) | Yes      | The TeamDynamix ticketing application the ticket belongs to. Options load from the selected connection. |
| Ticket ID             | integer         | Yes      | The ID of the ticket to fetch.                                                                          |

#### Outputs

| Field      | Type   | Description                                       |
| ---------- | ------ | ------------------------------------------------- |
| Ticket     | object | The full ticket as returned by TeamDynamix.       |
| Title      | string | The ticket title.                                 |
| Status     | string | The ticket's current status name.                 |
| Ticket URL | string | Direct TDNext link to the ticket, when derivable. |

### Search Tickets

Search tickets in TeamDynamix.

#### Inputs

| Field                 | Type                      | Required | Description                                                                                         |
| --------------------- | ------------------------- | -------- | --------------------------------------------------------------------------------------------------- |
| Ticketing Application | select (string)           | Yes      | The TeamDynamix ticketing application to search in. Options load from the selected connection.      |
| Search Text           | string                    | No       | Free-text search over ticket content. Default: .                                                    |
| Statuses              | multiple\_select (string) | No       | Only return tickets in these statuses. Options load from the selected connection. Default: \[].     |
| Priorities            | multiple\_select (string) | No       | Only return tickets with these priorities. Options load from the selected connection. Default: \[]. |
| Ticket Types          | multiple\_select (string) | No       | Only return tickets of these types. Options load from the selected connection. Default: \[].        |
| Created From          | datetime                  | No       | Only return tickets created on or after this time.                                                  |
| Created To            | datetime                  | No       | Only return tickets created on or before this time.                                                 |
| Modified From         | datetime                  | No       | Only return tickets last modified on or after this time.                                            |
| Modified To           | datetime                  | No       | Only return tickets last modified on or before this time.                                           |
| Max Results           | integer                   | No       | Maximum number of tickets to return. Default: 50.                                                   |

#### Outputs

| Field   | Type          | Description                                            |
| ------- | ------------- | ------------------------------------------------------ |
| Tickets | object\_array | Matching tickets (partial listings, not full records). |
| Count   | integer       | Number of tickets returned.                            |

## Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

### On Ticket Created

Trigger a workflow every time a ticket is created in a TeamDynamix ticketing application. Requires a webhook configured manually in TDAdmin.

In TDAdmin, open Applications, then your ticketing application, then Webhooks, and click New. Set the webhook URL to: {{webhook\_url}} Set a Secret on the TDAdmin webhook and paste the same value into the Webhook Secret field in the node Configuration. Only ticket Created events start this workflow.

#### Configuration

| Field                 | Type            | Required | Description                                                                                                            |
| --------------------- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| Ticketing Application | select (string) | Yes      | The TeamDynamix ticketing application whose webhook points at this trigger. Options load from the selected connection. |
| Webhook Secret        | secret          | No       | Secret used to verify deliveries; leave blank to accept unsigned posts.                                                |

#### Event inputs

| Field       | Type     | Required | Description                                                    |
| ----------- | -------- | -------- | -------------------------------------------------------------- |
| Ticket ID   | integer  | Yes      | ID of the created ticket.                                      |
| Change Type | string   | Yes      | The TeamDynamix change type (always Created for this trigger). |
| Ticket      | object   | Yes      | The ticket data from the webhook payload.                      |
| Raw Payload | textarea | Yes      | Raw JSON body TeamDynamix posted to the webhook.               |

#### Outputs

| Field       | Type     | Description                                                    |
| ----------- | -------- | -------------------------------------------------------------- |
| Ticket ID   | integer  | ID of the created ticket.                                      |
| Change Type | string   | The TeamDynamix change type (always Created for this trigger). |
| Ticket      | dict     | The ticket data from the webhook payload.                      |
| Raw Payload | textarea | Raw JSON body TeamDynamix posted to the webhook.               |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/teamdynamix.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.
