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

# Plain

Support tickets tell you which accounts are struggling before anyone on the revenue side hears about it. Connecting Plain syncs its Slack conversations and support tickets onto the matching CRM records.

{% stepper %}
{% step %}

### Copy the required scopes from Zero

In Zero, go to **Settings → Connections → Integrations**, scroll to **Issue Tracker integrations**, click **Connect Issue Tracker** and select **Plain**. The form shows the full list of API key scopes as a copyable snippet — click the copy button next to it. You will use this snippet in Plain's scope selector via **From Clipboard**.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_connect_scopes_snippet.png" alt="Connect Issue Tracker dialog with Plain selected, an empty API key field and the list of read scopes to copy"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Go to Plain settings, scroll to the bottom and click Machine users

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_settings_machine_users_menu.png" alt="Plain settings sidebar under Build with Plain showing the Machine users menu item"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add a new machine user

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_add_machine_user_form.png" alt="Plain Add a machine user form with Name and Public name set to Zero"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add API key

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_machine_user_api_keys.png" alt="Machine user detail page in Plain with an empty API Keys section and Add API key button"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Give API key permissions

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_api_key_permissions.gif" alt="Plain Add API Key form with permissions list, From clipboard option, and Create API Key button"><figcaption></figcaption></figure>

In Plain's scope selector, choose **From Clipboard** to apply the scopes you copied from Zero. Alternatively, grant read permissions to the following objects manually:

* company:read
* company:search
* customer:read
* customerEmail:read
* email:read
* label:read
* labelType:read
* machineUser:read
* tenant:read
* thread:read
* threadActivity:read
* threadDiscussion:read
* threadDiscussionMessage:read
* threadField:read
* threadFieldSchema:read
* timeline:read
* user:read
* workspace:read
  {% endstep %}

{% step %}

### Save and copy the API key

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/plain_api_key_created.png" alt="Plain API key created page showing the generated key with a copy button and I got it"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Paste the API key to Zero

Back in the Zero connect form, paste the key into **Issue Tracker API Key** and click **Connect Integration**.

If the integration shows `plain getThreads http error: 403`, the key is missing one of the scopes above. Create a new key with all of them applied and reconnect. A `401` means the key is invalid or has been revoked.
{% endstep %}

{% step %}

### Add issues properties to your lists to track Plain support threads

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/issue_tracker_add_issues_property.png" alt="Add a property menu listing Issues, Open issues, # of issues, and # of open issues"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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.zero.inc/settings/integrations/plain.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.