> 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-reply-to-email.md).

# Action: Reply 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 Reply to Email action sends a response to the sender of a selected email in Gmail.</p>

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

#### Example User Story

I want to reply to a client's inquiry email to provide a solution and close the ticket.

#### Fields

| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| messageId  | String     | Yes      |
| subject    | String     | No       |
| body       | String     | Yes      |
| from       | String     | No       |
| to         | String     | No       |

### Related Connections

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

### Related Automations

Example link

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

```
{
  "handle": "reply-to-email",
  "state": "inDev",
  "meta": {
    "short": "Reply to Email",
    "description": "Send a reply to a specific email in Gmail."
  },
  "input": [
    {
      "name": "messageId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the email to reply to."
      }
    },
    {
      "name": "subject",
      "type": "String",
      "required": false,
      "meta": {
        "description": "The subject of the reply email."
      }
    },
    {
      "name": "body",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The body content of the reply email."
      }
    },
    {
      "name": "from",
      "type": "String",
      "required": false,
      "meta": {
        "description": "The sender email address."
      }
    },
    {
      "name": "to",
      "type": "String",
      "required": false,
      "meta": {
        "description": "The recipient email address."
      }
    }
  ],
  "output": [
    {
      "name": "success",
      "type": "Boolean",
      "selector": ["success"],
      "meta": {
        "description": "Indicates if the reply was sent successfully."
      }
    },
    {
      "name": "messageId",
      "type": "String",
      "selector": ["messageId"],
      "meta": {
        "description": "The ID of the sent reply email."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "POST",
        "path": "/gmail/v1/users/me/messages/send",
        "headers": {
          "Content-Type": "application/json"
        },
        "bodyTemplate": {
          "value": "{\n  \"raw\": \"{{base64EncodedEmail}}\"\n}",
          "placeholders": [
            {
              "name": "accessToken",
              "type": "String",
              "description": "The OAuth access token for Gmail API.",
              "required": true
            },
            {
              "name": "base64EncodedEmail",
              "type": "String",
              "description": "The base64 URL-safe encoded email message.",
              "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-reply-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.