> 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/zenduty.md).

# Zenduty

Incident management and on-call alerting.

## Connectors

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

| Connector | Authentication |
| --------- | -------------- |
| Zenduty   | API key        |

### Zenduty

Connect Zenduty with an account API key to manage incidents and on-call alerting.

#### Set up in Zenduty

1. Prepare the Zenduty account or service that the workflow will access. Grant access to the required resources and operations.
2. **API key:** Create a key in Zenduty under Account > API Keys. Only an account Owner or Admin can create one, and the key is shown once, so copy it immediately. Only US-region accounts ([www.zenduty.com](http://www.zenduty.com)) are supported; EU-region accounts use a different host.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Zenduty**.
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                                                                                                                                                                                                                                                                                                                                       |
| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API key       | Yes      | Create a key in Zenduty under Account > API Keys. Only an account Owner or Admin can create one, and the key is shown once, so copy it immediately. Only US-region accounts ([www.zenduty.com](http://www.zenduty.com)) are supported; EU-region accounts use a different host. [Provider instructions](https://www.xurrent.com/imr-help/api-keys). |

### 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 **Zenduty** 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

### List Services

List the Zenduty services in one team, or in every team when Team is blank, with each service's id and default escalation policy.

#### Inputs

| Field | Type            | Required | Description                                                                                                             |
| ----- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| Team  | select (string) | No       | The team whose services to list. Leave blank to list services in every team. Options load from the selected connection. |

#### Outputs

| Field           | Type          | Description                                                         |
| --------------- | ------------- | ------------------------------------------------------------------- |
| Services        | object\_array | Services found, with id, name, team, and default escalation policy. |
| Teams truncated | boolean       | True when the account has more teams than one run scans.            |

### Create Incident

Create a Zenduty incident on a service. Zenduty notifies the on-call responders of the escalation policy right away. Blank escalation policy and assignee use the service's default escalation policy.

#### Inputs

| Field             | Type            | Required | Description                                                                                                                               |
| ----------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Team              | select (string) | Yes      | The team that owns the service. Options load from the selected connection.                                                                |
| Service           | select (string) | Yes      | The service the incident is about. Its escalation policy decides who is paged. Options load from the selected connection.                 |
| Title             | string          | Yes      | A short headline for the incident.                                                                                                        |
| Summary           | textarea        | No       | Details that help responders start work.                                                                                                  |
| Escalation policy | select (string) | No       | Who to page instead of the service's default policy. Leave blank to use the service's default. Options load from the selected connection. |
| Assignee          | select (string) | No       | Assign the incident to one team member instead of an escalation policy. Options load from the selected connection.                        |

#### Outputs

| Field    | Type   | Description           |
| -------- | ------ | --------------------- |
| Incident | object | The created incident. |

### List Incidents

List Zenduty incidents by status, team, service, and creation date, one page at a time. Blank status lists open incidents (triggered and acknowledged).

#### Inputs

| Field                | Type            | Required | Description                                                                                                                                                                                      |
| -------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Status               | select (string) | No       | Which incidents to include. Blank lists open incidents (triggered and acknowledged). Available values: Open (triggered and acknowledged), All, Triggered, Acknowledged, Resolved. Default: open. |
| Team                 | select (string) | No       | Only incidents of this team. Leave blank for every team. Options load from the selected connection.                                                                                              |
| Service              | select (string) | No       | Only incidents on this service. Requires Team. Options load from the selected connection.                                                                                                        |
| Created on or after  | string          | No       | Only incidents created on or after this day (inclusive, whole day).                                                                                                                              |
| Created on or before | string          | No       | Only incidents created on or before this day (inclusive, whole day).                                                                                                                             |
| Page                 | integer         | No       | Page number to read. Default: 1.                                                                                                                                                                 |

#### Outputs

| Field     | Type          | Description                                       |
| --------- | ------------- | ------------------------------------------------- |
| Incidents | object\_array | Incidents on this page.                           |
| Next page | integer       | Page number to read next, blank on the last page. |

### Resolve Incident

Mark a Zenduty incident as resolved. Zenduty stops escalating it and notifies responders. If this attempt finds the incident already resolved, it sends no update (already\_resolved is true, which can also happen on a retried run after an earlier attempt already resolved it).

#### Inputs

| Field    | Type             | Required | Description                                                              |
| -------- | ---------------- | -------- | ------------------------------------------------------------------------ |
| Incident | select (integer) | Yes      | The open incident to resolve. Options load from the selected connection. |

#### Outputs

| Field            | Type    | Description                                                                                                                                                  |
| ---------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Incident         | object  | The resolved incident.                                                                                                                                       |
| Already resolved | boolean | True when this attempt found the incident already resolved and sent no update. On a retried run this can be true even though an earlier attempt resolved it. |

### List On-Call Schedules

List the on-call schedules in one team, or in every team when Team is blank, with each schedule's time zone, rotation layers, and overrides. These are schedule definitions (rotations and overrides), not who is on call right now.

#### Inputs

| Field | Type            | Required | Description                                                                                                               |
| ----- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------- |
| Team  | select (string) | No       | The team whose schedules to list. Leave blank to list schedules in every team. Options load from the selected connection. |

#### Outputs

| Field           | Type          | Description                                                      |
| --------------- | ------------- | ---------------------------------------------------------------- |
| Schedules       | object\_array | Schedules found, with time zone, rotation layers, and overrides. |
| Teams truncated | boolean       | True when the account has more teams than one run scans.         |

### List Current On-Call

Show who is on call right now for each escalation policy in one team, or in every team when Team is blank, with each level's delay and on-call users. This is the live on-call roster, not the schedule definitions List On-Call Schedules returns.

#### Inputs

| Field | Type            | Required | Description                                                                                                      |
| ----- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
| Team  | select (string) | No       | The team to check. Leave blank to check who is on call in every team. Options load from the selected connection. |

#### Outputs

| Field               | Type          | Description                                              |
| ------------------- | ------------- | -------------------------------------------------------- |
| Escalation policies | object\_array | Current on-call responders per escalation policy.        |
| Teams truncated     | boolean       | True when the account has more teams than one run scans. |

## 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/zenduty.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.
