> For the complete documentation index, see [llms.txt](https://playbook.nativemsg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.nativemsg.com/mcp/tool-reference/experiences.md).

# Experiences & Revisions

An **experience** is the conversation your channels run: workflows triggered by intents or keywords, each running a sequence of actions, defined by the [RCS Experience Schema](https://playbook.nativemsg.com/rcs-experience-schema). Every change to an experience's workflows saves a **revision** you can restore.

| Tool                          | What it does                                                                                                                                                                   | Key inputs                                                                                                                                                       |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `list_experiences`            | List experiences with `id`, `name`, `channels`, `published`, `currentRevision`, `latestRevision`, `enabled` (workflows omitted)                                                | `limit`, `cursor`                                                                                                                                                |
| `get_experience`              | One experience by id, including its workflows                                                                                                                                  | `experience_id`                                                                                                                                                  |
| `create_experience`           | Create an experience                                                                                                                                                           | `name` (1–100 chars, unique), `workflows` (RCS Experience Schema array; each needs `intents` + `actions`), optional `welcome_workflow`, `enabled` (default true) |
| `update_experience`           | Change name, workflows (replaces the whole array), welcome workflow, or enabled. Saves a new revision; returns `{ experience, revision, previous_revision, revision_created }` | `experience_id`, fields to change, `force`                                                                                                                       |
| `delete_experience`           | Delete the experience **and every channel attached to it**, including those channels' contacts and conversations. Cannot be undone                                             | `experience_id`, `force`                                                                                                                                         |
| `list_experience_revisions`   | Saved revisions: `{ id, botId, revision, revisionName, name }`                                                                                                                 | `experience_id`, `limit`, `cursor`                                                                                                                               |
| `get_experience_revision`     | One revision; `data` holds that revision's workflows as a JSON string                                                                                                          | `experience_id`, `revision`                                                                                                                                      |
| `restore_experience_revision` | Make a saved revision current (name, workflows, welcome workflow). The replaced revision stays in history                                                                      | `experience_id`, `revision`, `force`                                                                                                                             |
| `list_bots` / `get_bot`       | **Deprecated** — use `list_experiences` / `get_experience`                                                                                                                     | see [Versioning](/mcp/versioning.md)                                                                                                                             |

## Live-change protection (`force`)

An **unpublished** experience runs its current revision, so updating or restoring one that has **subscribed contacts** changes what those contacts see immediately. The server refuses that case — reporting the subscriber count — unless `force: true`. A **published** experience keeps running its published revision, so edits are safe to stage.

`delete_experience` is refused — naming the affected channels — when the experience has subscribed contacts or channels beyond the web-chat pair every experience gets, unless `force: true`. It returns `{ deleted, channels_deleted, subscribers, message }`.

## Typical flows

* **Build:** design workflows → `create_experience` → add a tester device → test on a phone → attach a channel (`create_channel` takes `experience_id`).
* **Revise:** `update_experience` → note the returned `revision` → re-test → roll back with `restore_experience_revision` if needed.
* See [Build an experience](/mcp/guides/build-an-experience.md) for the full walkthrough.


---

# 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://playbook.nativemsg.com/mcp/tool-reference/experiences.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.