# Google Calendar

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**Google Calendar** performs various operations on a Google Calendar.

## **Parameters**

Take a look at the configuration parameters for the connector. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Dynamic Account</strong></td><td>When active, the connector will use the account dynamically. Otherwise, it will use the account statically.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Account Name</strong> <code>(DB)</code></td><td>The name of the dynamic account used by the connector. This account must have been previously configured in a <a href="/pages/0kxlZ011XP4A2T43v9kh"><strong>Store Account</strong></a> connector in the pipeline for this process to take effect. It is only available if the <strong>Dynamic Account</strong> parameter is active.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Account</strong></td><td>The account used by the connector. It is only available if the <strong>Dynamic Account</strong> parameter is inactive.</td><td>N/A</td><td>Account</td></tr><tr><td><strong>Api Name</strong></td><td>The operation to perform.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Method Name</strong></td><td>The sub-operation to use for the selected operation.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Application Name</strong> <code>(DB)</code></td><td>Google Calendar application name. Example would be digibee-google-calendar/1.0</td><td>N/A</td><td>String</td></tr><tr><td><strong>Client Id</strong> <code>(DB)</code></td><td>Client ID of the calendar application.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Delegate</strong> <code>(DB)</code></td><td>Delegate for wide-domain service account.</td><td>N/A</td><td>String</td></tr><tr><td><strong>In Body</strong> <code>(DB)</code></td><td>Sets the name of a parameter to be passed in the exchange <strong>In Body</strong>.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Scopes <code>DB</code></strong></td><td>Specifies the level of permissions you want a calendar application to have to a user account. You can separate multiple scopes by comma. <a href="https://developers.google.com/google-apps/calendar/auth">Learn more in the Google documentation</a>.</td><td><a href="https://www.googleapis.com/auth/calendar">https://www.googleapis.com/auth/calendar</a></td><td>JSON</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# Agent Instructions: 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.digibee.com/documentation/connectors-and-triggers/connectors/google-gcp/calendar.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.