# Create Google Calendar Event

Creates a new event in Google Calendar.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## When to use this node

Creates a new event in Google Calendar.

Add **Create Google Calendar Event** to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

## Before you begin

Connect Google Workspace in **App Connections** first. Select the intended account in this node; an account connected to a different service is not interchangeable. Available actions depend on the permissions granted to that connection.

## Configure the fields

| Field | What to enter |
| --- | --- |
| **Google Account** | Returned from integration |
| **Calendar ID** | Usually 'primary'<br>Example/default shown in the editor: `primary`. |
| **Event Title** | Title of the event |
| **Description** | Event description |
| **Start Time** | ISO format or 'now' for current time, or 'now + N' for N minutes from now (e.g., 'now + 30'). For Persian calendar, use combined date+time format: YYYY-MM-DD HH:MM (e.g., '1404-09-10 15:00') with 'calendar' set to 'persian'<br>Example/default shown in the editor: `now`. |
| **End Time** | ISO format or 'now' for current time, or 'now + N' for N minutes from now (e.g., 'now + 60')<br>Example/default shown in the editor: `now + 60`. |
| **Time Zone** | IANA timezone name (NOT UTC+offset format). Examples: UTC, America/Toronto, Asia/Dubai, Europe/London, America/New_York<br>Example/default shown in the editor: `UTC`. |
| **Location (Optional)** | Physical location or virtual meeting link (e.g., 'Conference Room A' or 'https://meet.google.com/xyz') |
| **Attendees (Optional)** | Email addresses of attendees, comma-separated (e.g., 'john@example.com, jane@example.com') |
| **Send Updates (Optional)** | Send email notifications: 'all' (everyone), 'externalOnly' (external attendees), 'none' (no emails). Default: 'none'<br>Choices: `none`, `all`, `externalOnly`.<br>Example/default shown in the editor: `none`. |
| **Calendar System (Optional)** | Calendar system for date input parsing. Options: 'gregorian' (default), 'persian'. When set to 'persian', the 'start' and 'end' fields accept Persian dates in single combined format (e.g., '1404-09-10 15:00', '1404/09/10 15:00', '10 آذر 1404 15:00'). If not specified, defaults to Gregorian calendar. This only affects input parsing - output is always ISO format for Google Calendar.<br>Choices: `gregorian`, `persian`.<br>Example/default shown in the editor: `gregorian`. |
| **Locale (Optional)** | Language for date input parsing. Options: 'en' (English, default), 'fa' (Persian), 'ar' (Arabic), 'es' (Spanish), 'de' (German), 'fr' (French), 'it' (Italian), 'pt' (Portuguese). Works with calendar parameter to parse dates in user's language. If not specified, defaults to English.<br>Choices: `en`, `fa`, `ar`, `es`, `de`, `fr`, `it`, `pt`.<br>Example/default shown in the editor: `en`. |
| **Color (Optional)** | Event color ID (1-11): 1=Lavender, 2=Sage, 3=Grape, 4=Flamingo, 5=Banana, 6=Tangerine, 7=Peacock, 8=Graphite, 9=Blueberry, 10=Basil, 11=Tomato<br>Choices: `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`. |
| **Availability Profile (Optional)** | Multi-line availability profile for conflict prevention. All keys optional. Format: key: value (one per line)<br><br>Resource Identifiers:<br>• resource-title: Dr. Sarah Johnson<br>• resource-code: DOC001<br>• resource-email: dr.sarah@clinic.com<br>• resource-location: Room A<br><br>Time Constraints:<br>• appointment-duration: 60min (or 1.5h, defaults to 60min if not specified)<br>• unavailable-days: saturday, sunday<br>• available-hours: 08:00-18:00<br>• blocked-times: daily 12:00-13:00<br>• blocked-times: monday 10:00-11:00<br><br>Conflict Settings:<br>• conflict-detail: minimal (default, or full)<br><br>Custom Information (ignored by system, for AI/workflow context):<br>• speciality: Orthopedic Surgery<br>• services: Hair Coloring, Highlights, Keratin<br>• department: Cardiology<br>• Any other key: Custom value for AI training<br><br>System checks requested time slot in calendar. If conflict found, event creation fails and workflow branches to 'Unavailable'. Keys are case-insensitive and space-tolerant (key:value = key : value). Supports multi-language keys. Unknown keys are ignored, allowing unlimited custom information for AI context. |

## Use the result

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

| Output | Meaning / label |
| --- | --- |
| `result` | Event Status |
| `eventId` | Event ID |
| `eventLink` | Event Link |
| `detail` | Availability Detail |

## Connect the next step

This definition exposes these paths:

- **Created** — branch 1.
- **Unavailable** — branch 2.
- **Error** — branch 3.

Connect each relevant outcome, especially any error or timeout path. Outputs can differ by outcome; check that a result exists before using it.

## Test it in a workflow

1. Configure this node with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use **Run** only for a Manual workflow.
4. Open **Workflow Activity** and check the outcome before enabling wider use.

## If something goes wrong

- Reconnect the account if authorization has expired, then verify its permissions on the specific resource.
- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the [troubleshooting guide](/help/troubleshooting/) for a symptom-by-symptom checklist.

## Related guides

- [Work with variables](/workflows/variables/)
- [Understand branches and error handling](/workflows/branches/)
- [Browse all nodes](/reference/nodes/)
- [Add Sheet to Spreadsheet](/nodes/google-sheets-addsheet/)
- [Append Data to Google Sheet](/nodes/google-sheets-appenddata/)
- [Clear Range in Google Sheet](/nodes/google-sheets-clearrange/)
- [Create Folder in Google Drive](/nodes/google-drive-createfolder/)
- [Create Google Doc (Advanced)](/nodes/google-docs-createdocument/)


## Catalog coverage

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.