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

# All Quiet Teams

A block for listing All Quiet teams. Mainly used to resolve the team IDs that the incident and on-call blocks accept as inputs.

## AllQuiet List Teams

### What it is

Lists All Quiet teams and their IDs

### How it works

Lists the teams in your All Quiet organization with their IDs, time zones and labels, optionally filtered by name. Its `team_ids` output is designed to feed the `team_ids` input on Create Incident, List Incidents and Get On-Call, so a graph can target teams by name without hardcoding UUIDs.

### Inputs

| Input         | Description                                                                               | Type         | Required |
| ------------- | ----------------------------------------------------------------------------------------- | ------------ | -------- |
| display\_name | Filter to teams whose name matches this text.                                             | str          | No       |
| limit         | Maximum number of teams to return.                                                        | int          | No       |
| offset        | Number of teams to skip, for paging.                                                      | int          | No       |
| region        | The All Quiet deployment your API key belongs to. Use EU if you signed up on allquiet.eu. | "us" \| "eu" | No       |

### Outputs

| Output    | Description                                               | Type        |
| --------- | --------------------------------------------------------- | ----------- |
| error     | Error message if the request failed                       | str         |
| teams     | All matching teams                                        | List\[Team] |
| team      | Each matching team, emitted one at a time                 | Team        |
| team\_ids | IDs of the matching teams, for use as team\_ids elsewhere | List\[str]  |
| has\_more | Whether more teams are available beyond this page         | bool        |

### Possible use case

A graph that should page whichever team owns a failing service looks the team up by display name, then passes the resulting ID to Create Incident — so renaming or re-creating a team in All Quiet doesn't require editing the agent.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://agpt.co/docs/integrations/block-integrations/teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.