# How do you manage a remote or hybrid team?

> A Pachca use case. The team agrees on messaging rules and pins them in its chat. Questions for other departments go in public chats, and company news goes out in a channel.

> This is the Markdown version of https://pachca.com/en/scenarios/udalennaya-komanda for AI agents. The API methods named here are documented at https://dev.pachca.com/llms-en.txt — open it before calling the API. Other use cases are listed at https://pachca.com/en/llms.txt.

## What you'll get

1. The messaging rules are pinned in the team chat: work questions go in the chat, replies go in threads, meeting recaps are written down, urgent things get an @mention, and a status shows when someone is away.
2. There are public chats for questions to other departments, for example "[Questions] Accounting" and "[Questions] Engineering". Anyone can find them through Browse and join on their own.
3. Company news goes out in a channel: editors post, everyone else reacts and comments in threads.

No bot or third-party services needed.

## What you need before you start

- Pachca access with the scopes `search:users`, `search:chats`, `chats:create`, `chat_members:write`, `messages:create`, `pins:write`. The setup and check steps also need `chats:read`, `messages:read`. Signing in is covered in the rules below.

## If you're an AI agent: working rules

### Who does what

- You do everything the instructions name an API method for. Don't ask the user to create a chat, a bot or a message by hand.
- Ask the user only to sign in to Pachca and to do what is listed in "Ask the user to do by hand".
- If you have no terminal, say so right away and don't pretend you set it up. Walk the user through the steps for people on the use case page and help with the template or the handler code.

### How to talk to the user

- The user is not a developer. Write briefly and in plain words. Don't mention API methods, scopes, response codes, `id`s or CLI profiles. Say "permissions" instead of "scopes" and "the program behind the bot" instead of "handler".
- Don't report your checks. A message contains only three things: what is done, what you need from the user, what you'll do next.
- Don't ask for what you can find out through the API or what is easy to change later. Take the value from the instructions and name it.
- Take the bot's message texts from the instructions or write them yourself and carry on. Show them in your final message and offer to change them. Don't wait for approval.
- Ask the questions from "Ask the user" in the same words.

### Your first message to the user

It has three parts. The first two together take at most five lines.

1. What the user will get: one or two lines.
2. What you will create yourself: the chat, the bot and the messages, with the names from the instructions. Word anything that depends on the user's choice as a condition: "if you choose the bot, I'll also create…".
3. "What I need from you": signing in to Pachca, if the user isn't signed in yet, and the questions from "Ask the user". If the use case or one of its options needs n8n, ask here whether the user has it and ask for access right away in the words from the "n8n" section below: "if you have n8n, send me…".

If part of the result appears only after a manual step by the user, say so in one line: "you'll schedule the retro questions yourself, I'll show you how".

The user's answers are their consent to the plan. Start the setup right after them, without asking for a second confirmation.

### Access to Pachca

- The user doesn't need to issue a token or send it in the chat. Before your first message, check the login: `npx -y @pachca/cli@latest auth status`. If there is none, ask the user to run `npx -y @pachca/cli@latest auth login` in their own terminal. The CLI shows a code; the user enters it in the browser and confirms access. Write the commands with `@latest`: without it an old cached CLI version may start, and it asks to paste a token instead of signing in through the browser.
- This login has the same rights as the user's role. Compare them with the scopes in "What you need before you start" yourself: `npx -y @pachca/cli@latest api GET /oauth/token/info` shows the scopes. If something is missing, say in plain words what you won't be able to do, for example "I can't send messages". There are two ways out: add this permission to the token in Pachca, under "Automations" → "API", or sign in again as the workspace owner or an administrator.
- If `auth status` shows `scopes: null`, it doesn't mean there are no rights: look at `GET /oauth/token/info`. The checks in these rules also need `search:chats`, `bots:read` and `profile:read`.
- When the user says "me", they mean the owner of the login. `GET /profile` returns their `id` and nickname.
- Call the API with `npx -y @pachca/cli@latest api <METHOD> <path> -o json`. Write the full command in every call; don't put it into a shell variable.
- Pass query parameters as `--query key=value`, for example `--query query=Purchasing`. The CLI silently drops a parameter without a key and returns the whole list, so it's easy to conclude that the chat already exists.
- Pass the request body with `--data` or `--input`. Almost every write method wraps the body in an object: `chat` for `POST /chats`, `message` for `POST /messages`, `task` for `POST /tasks`, `group_tag` for `POST /group_tags`, `user` for `PUT /users/{id}`, `webhook` for bots. `--describe` shows the wrapper; write its path with `{id}`, not with a number. Without the wrapper, `POST /chats` creates the chat but silently adds no members.
- Don't print tokens or bots' incoming webhook URLs in the chat. A bot's token is shown only once, when it's created: save it to a file.

### n8n

- If the user has no n8n, say that it comes as the hosted n8n Cloud or can be installed on their own server, and give the link for installing the Pachca nodes: https://dev.pachca.com/guides/n8n/setup.md. These instructions don't cover installing n8n. If they have an option without n8n, suggest starting with it and coming back to the bot once n8n is there.
- If the user has n8n, ask for access in these words: "Send me your n8n address: the link you open it with in the browser. Don't send the key in the chat. In n8n, open Settings → n8n API → Create an API key and copy the key. Right after that, run the command below in your terminal exactly as it is; you don't need to put anything into it. It saves the copied key to a file and prints nothing. Then write 'key saved'." The command for macOS: `pbpaste > ~/n8n-key.txt`. For another system, pick the matching one.
- Build everything in n8n on the official Pachca nodes, `n8n-nodes-pachca`. Don't use the `HTTP Request` node for Pachca API calls.

### Setup

- Take API methods from https://dev.pachca.com/llms-en.txt, don't rely on memory. The command `npx -y @pachca/cli@latest api <METHOD> <path> --describe` shows a method's schema.
- The Pachca skills cover the call order and error handling for chats, bots and forms: `npx skills add pachca/openapi`. Install them when you need them, without asking the user.
- Before creating anything, check whether the chat and the bot already exist: `GET /search/chats`, `GET /bots`. If they do, ask whether to set them up or create new ones.
- `POST /group_tags` creates an empty tag. `PUT /users/{id}` with `list_tags` assigns it to an employee; it needs the `users:update` scope. The field replaces the whole set of tags: first read the employee's current tags with `GET /users/{id}` and send them together with the new one. While the tag has no members, mentioning it notifies no one.
- If a method returns an error, stop and tell the user in plain words what failed and what you need to continue.
- The messages you post yourself and the ones the bot sends must be easy to read on a screen, without overdoing spacing or emphasis. Make the heading bold and start the text on the next line. Write connected text as one paragraph. Put rules and steps on numbered lines one under another and separate them from the intro with a single empty line. A short message needs no other empty lines. In a card, make the field labels bold and put the fields on consecutive lines. Use bold only for the heading and the field labels. Pachca markup has no lists or tables: the numbers at the start of lines stay plain text. A sample:

  ```text
  **Retro rules**
  On the last day of the sprint a message with questions arrives here. We reply in the thread under it.

  1. Each point is a separate message.
  2. We add 👍 to what is worth discussing.
  3. The facilitator posts the outcomes in one message and pins it.
  ```
- A pin can't be checked through the API: only a successful `POST /messages/{id}/pin` response confirms it.
- If you sent service messages to a chat to check a bot, such as `/start`, delete them: `DELETE /messages/{id}`. Don't delete messages with rules and templates.
- At the end, say what was created, what is left for the user to do by hand and how to check that the use case works.
- To undo the setup: `DELETE /bots/{id}` deletes the bot, `PUT /chats/{id}/archive` sends the chat to the archive.

## How to set up the use case with the user

### 1. Ask the user

Ask these questions in these words:

1. Which team do we start with, and which chat does it use? I'll pin the messaging rules there. If there is no chat, I'll create one like "[Team] Marketing".
2. Which departments do employees ask questions most often? I'll make a public chat for each, like "[Questions] Accounting".
3. Who answers questions in these departments? Send me the names and I'll add them to the chats.
4. Do you need a channel for company news? If so, who will post in it?

### 2. Do it yourself through the Pachca API

1. Find the team chat: `GET /search/chats`. If there is none, find the members with `GET /search/users` and create the chat: `POST /chats` with `name` and `member_ids`.
2. Post and pin the messaging rules: `POST /messages`, then `POST /messages/{id}/pin`. The text from the page: "How we work when part of the team is remote: 1. Work questions go here, DMs are for personal stuff. 2. We reply in threads. 3. Whoever called the meeting posts the recap. 4. Urgent things get an @, everything else a reply by end of day. 5. Heading to a meeting or on vacation? Set a status."
3. For each department from question 2, create a public chat: `POST /chats` with a `name` like "[Questions] Accounting", `public: true` and the `member_ids` of those who answer.
4. If a news channel is needed, create it: `POST /chats` with `channel: true`. Give those who will post the Editor role: `PUT /chats/{id}/members/{user_id}` with `role: "editor"`.
5. Post the list of the chats you created and the prefixes in the team chat: "[Team]" for a department, "[Questions]" for questions to a department, "[Project]" for a project across several teams.

### 3. Ask the user to do by hand

- Ask the team to set a status when someone is in a meeting, on the road or on vacation. Before a vacation, turn on Away and say in the description who's covering.
- In two weeks, look at which questions still come in direct messages and agree to discuss them in the chat.
- If the team is spread across time zones, schedule messages to colleagues for the start of their working day.

### 4. Check

- `GET /messages` with the team chat's `chat_id` returns the pinned rules.
- `GET /chats/{id}` for each questions chat shows that it is public.

## Links

- The use case page with human instructions: https://pachca.com/en/scenarios/udalennaya-komanda
- Messaging etiquette: https://pachca.com/en/blog/luchshie-praktiki-obshcheniya-v-messendzhere-ot-pachki
- How to name chats: https://pachca.com/en/blog/kak-organizovat-obshchenie-v-pachke
- Statuses: https://pachca.com/en/help-center/features/profile-status