> 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/google-calendar-individual/action-quick-add-event.md).

# Action: Quick Add Event

<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/XTIXuRodkVx2AJQ6LF4T" alt="" width="188"><figcaption></figcaption></figure>

<p align="center">The Quick Add Event action creates an event using natural language input.</p>

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

#### Example User Story

I want to quickly add an event to my Google Calendar by typing a natural language description so that I can efficiently manage my schedule.

#### Fields

| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| calendarId | String     | Yes      |
| text       | String     | Yes      |

### Related Connections

[Google Calendar](/human-connections/google/google-calendar-individual.md)

### Related Automations

Example link

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

```
{
  "handle": "quick-add-event",
  "state": "inDev",
  "meta": {
    "short": "Quick Add Event",
    "description": "Quickly add an event to Google Calendar using natural language input."
  },
  "input": [
    {
      "name": "calendarId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The calendar identifier. Populated from discovered calendars."
      }
    },
    {
      "name": "text",
      "type": "String",
      "required": true,
      "meta": {
        "description": "Natural language text describing the event (e.g., 'Meeting with John at 3pm tomorrow')."
      }
    }
  ],
  "output": [
    {
      "name": "eventID",
      "type": "String",
      "selector": [
        "id"
      ],
      "meta": {
        "description": "The ID of the created event."
      }
    },
    {
      "name": "status",
      "type": "String",
      "selector": [
        "status"
      ],
      "meta": {
        "description": "The status of the event (e.g., 'confirmed')."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "POST",
        "path": {
          "value": "/{{calendarId}}/events/quickAdd",
          "placeholders": [
            {
              "name": "calendarId",
              "type": "String",
              "description": "The calendar identifier.",
              "required": true,
              "default": ""
            }
          ]
        },
        "queryParams": {
          "text": {
            "value": "{{text}}"
          }
        },
        "bodyTemplate": {
          "value": ""
        }
      }
    }
  ]
}
```

<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/google-calendar-individual/action-quick-add-event.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.