> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/human-connections/google/gmail/action-add-label-to-email.md).

# Action: Add Label to Email

<p align="center"><a class="button primary" data-icon="circle-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscriptions</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

<figure><img src="/files/5kJqaCa4hNci9Yb597Jb" alt="" width="188"><figcaption></figcaption></figure>

<p align="center">The Add Label to Email action applies a specified label to a selected email in Gmail for better organization.</p>

{% embed url="<https://www.youtube.com/watch?v=CyuUuaBSZzA>" %}

#### Example User Story

I want to quickly add a 'Follow-Up' label to important emails so I can easily track and prioritize them later.

#### Fields

| Field Name  | Field Type | Required |
| ----------- | ---------- | -------- |
| emailId     | String     | Yes      |
| labelId     | String     | Yes      |
| accessToken | String     | Yes      |

### Related Connections

[Gmail](/human-connections/google/gmail.md)

### Related Automations

Example link

### Code (Apache v2.0): Operation

```
{
  "handle": "add-label-to-email",
  "state": "inDev",
  "meta": {
    "short": "Add Label to Email",
    "description": "Adds a specified label to an email in Gmail."
  },
  "input": [
    {
      "name": "emailId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the email to which the label will be added."
      }
    },
    {
      "name": "labelId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the label to be added to the email."
      }
    }
  ],
  "output": [
    {
      "name": "success",
      "type": "Boolean",
      "selector": ["success"],
      "meta": {
        "description": "Indicates whether the label was successfully added to the email."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "POST",
        "path": "/gmail/v1/users/me/messages/{{emailId}}/modify",
        "headers": {
          "Content-Type": "application/json"
        },
        "bodyTemplate": {
          "value": "{\"addLabelIds\": [\"{{labelId}}\"]}",
          "placeholders": [
            {
              "name": "emailId",
              "type": "String",
              "description": "The ID of the email.",
              "required": true
            },
            {
              "name": "labelId",
              "type": "String",
              "description": "The ID of the label to be added.",
              "required": true
            },
            {
              "name": "accessToken",
              "type": "String",
              "description": "The access token for authenticating with the Gmail API.",
              "required": true
            }
          ]
        }
      }
    }
  ]
}

```

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>


---

# 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:

```
GET https://docs.planetcrust.com/human-connections/google/gmail/action-add-label-to-email.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.