Google Calendar Tools
Googlecalendar Create Event
Utilisez Googlecalendar Create Event avec Google Calendar Tools via Aident Loadout. Vérifiez les entrées, sorties, la configuration, le tarif et le risque avant exécution.
Action d'écritureNiveau de risque 2 sur 5Connexion OAuth
Description du fournisseur
Create a Google Calendar event using start_datetime plus duration fields. The organizer is added as an attendee unless exclude_organizer is True. By default adds Google Meet link (works for Workspace, gracefully falls back for personal Gmail). Attendees can be email strings (req…
Tarifs et limites
- Tarif
- Action gratuite
- Paiement unifié
- Non pris en charge actuellement
Entrées
- Summary (title) of the event.summarystring
- Geographic location of the event as free-form text.locationstring
- IANA timezone name from the timezone database (e.g., 'America/New_York', 'Europe/London', 'Asia/Jerusalem', 'UTC'). Required if datetime is naive. For recurring events, start and end must include a timeZone. If not provided, UTC is used. If datetime includes timezone info (Z or…timezonestring
- List of attendees. Each attendee can be either: (1) A string email address (e.g., 'user@example.com'), or (2) An object with 'email' (required), 'optional' (boolean, default false), 'displayName' (string), 'comment' (string), 'additionalGuests' (integer), and 'resource' (boolean…attendeesarray
- Type of the event, immutable post-creation. 'workingLocation' (REQUIRES Google Workspace Enterprise). Note: 'fromGmail' events cannot be created via API.eventTypestring
- List of RRULE, EXRULE, RDATE, EXDATE lines for recurring events. Supported frequencies: DAILY, WEEKLY, MONTHLY, YEARLY. For recurring events, start.timeZone and end.timeZone must be present. UNTIL values follow RFC 5545: date-only (YYYYMMDD) for all-day events, or UTC datetime w…recurrencearray
- Event visibility: 'default', 'public', 'private', or 'confidential'.visibilitystring
- Calendar identifier. Use 'primary' (recommended) for the user's main calendar. Alternatively, use a calendar ID from the user's accessible calendar list. Calendar IDs look like email addresses (e.g., 'xyz@group.calendar.google.com' for shared calendars). Important: Arbitrary ema…calendar_idstring
- Description of the event. Can contain HTML. Optional. Must be omitted for 'birthday' event type.descriptionstring
- Event end time in ISO 8601 format: YYYY-MM-DDTHH:MM:SS. When provided, this parameter takes precedence over event_duration_hour and event_duration_minutes. If not provided, the end time is calculated using start_datetime + duration. Must be after start_datetime. Fractional secon…end_datetimestring
- Options for who should receive notifications about event changes.send_updatesstring
- 'opaque' (busy) or 'transparent' (available).transparencystring
Sortie observable
- Data from the action executiondataObligatoire
- Error if any occurred during the execution of the actionerrorstring
- Whether or not the action execution was successful or notsuccessfulbooleanObligatoire
Skills qui utilisent cette Action
Cas d’usage associés
Aucun cas d’usage associé et vérifié pour le moment.