text
stringlengths
0
59.1k
1. Enable the [Google Calendar API](https://console.cloud.google.com/apis/library/calendar-json.googleapis.com) in your Google Cloud project.
2. In **APIs & Services β†’ Credentials**, create an **OAuth client ID** (type: **Web application**).
3. Add the VoltOps OAuth redirect URL shown in the console as an authorized redirect URI.
4. In VoltOps Console **Step 1 (Connection)**, create a Google Calendar credential and provide the **Client ID** and **Client Secret**, then click **Authorize with Google** to complete the OAuth flow.
VoltOps requests the `https://www.googleapis.com/auth/calendar` scope and automatically refreshes tokens.
## Trigger Configuration
- **Calendar ID**: Calendar to watch. Default: `primary`.
- **Event Type**: Choose one of the supported events below.
- **Search Term (Optional)**: Keyword query sent as `q` to Google Calendar (e.g., `"interview"`).
- **Expand Recurring Events**: When enabled, recurring instances are expanded for started/ended checks.
- **Polling Interval**: How often VoltOps polls. Default 60 seconds; minimum 30 seconds.
## Event Types
- `googlecalendar.eventCreated` β€” New event created (delivery: Polling)
- `googlecalendar.eventUpdated` β€” Existing event updated (delivery: Polling)
- `googlecalendar.eventCancelled` β€” Event cancelled (delivery: Polling)
- `googlecalendar.eventStarted` β€” Event start time reached (delivery: Polling)
- `googlecalendar.eventEnded` β€” Event end time reached (delivery: Polling)
## Payload Structure
VoltOps delivers the event with provider metadata:
```json
{
"provider": "googlecalendar",
"triggerType": "eventUpdated",
"calendarId": "primary",
"matchTerm": "planning",
"polledAt": "2024-11-14T10:00:00.000Z",
"eventId": "abcd1234",
"event": {
"id": "abcd1234",
"status": "confirmed",
"summary": "Product sync",
"start": { "dateTime": "2024-11-14T10:30:00.000Z", "timeZone": "UTC" },
"end": { "dateTime": "2024-11-14T11:00:00.000Z", "timeZone": "UTC" },
"updated": "2024-11-14T09:55:00.000Z",
"htmlLink": "https://www.google.com/calendar/event?eid=..."
}
}
```
## Add Target to Activate Binding
After configuring your Google Calendar trigger, add a target (agent or workflow) to activate the binding. For detailed instructions on:
- Adding targets to activate bindings
- Mapping trigger data to agent inputs
- Testing triggers with sample payloads
- Deploying and monitoring triggers
See the [Add Target to Activate Binding section](https://voltagent.dev/automations-docs/triggers/overviewusage/#step-3-add-target-to-activate-binding). These steps are the same for all trigger providers.
<|endoftext|>
# source: VoltAgent__voltagent/website/actions-triggers-docs/triggers/airtable.md type: docs
# Airtable Trigger
The Airtable trigger polls your bases at a configurable interval and executes agents or workflows when records match the configured criteria.
For complete trigger setup and usage instructions, see the [Usage Guide](https://voltagent.dev/automations-docs/triggers/overviewusage/).
**Use Cases**:
- Process new customer records
- Handle form submissions
- Sync data between systems
- Run content management workflows
## Setting Credentials
To set up Airtable authentication:
1. Navigate to the [VoltOps Triggers page](https://console.voltagent.dev/triggers)
2. Select Airtable as the provider and click **New credential**
3. Choose between Personal Access Token or OAuth 2.0 and follow the instructions below.
<video controls loop muted playsInline style={{width: '100%', height: 'auto'}}>
<source src="https://cdn.voltagent.dev/console/trigger/airtable-credentials.mp4" type="video/mp4" />
Your browser does not support the video tag.
</video>
<br/>
<br/>
### Personal Access Token
**Create your token:**
1. Visit [airtable.com/create/tokens](https://airtable.com/create/tokens)
2. Click **+ Create new token** and name it (e.g., "VoltAgent Trigger")
3. Add the following scopes:
```
data.records:read # Fetch record data