Skip to content

Prepare calendar events from email

Connect email and calendar using documented API steps, explicit date interpretation gaps and confirmation before an event is created.

Content updated:

Does this route fit?

Reading messages, querying availability and creating events are documented. Interpreting “next Friday” and its time zone is not established. Start with a prepared event that a person confirms.

Blocked: required steps are not documented.

4/5 steps backed by API documentation.

Required apps

Open the matching plan

Setup and a small test

  1. Explicitly confirm date, time, time zone and duration from the message. Stop when the information conflicts.

  2. Check availability separately from event creation. An available slot is not evidence that an invitee has agreed.

  3. Use your own test calendar without other attendees first. Expand the workflow only after checking the created event.

Steps and evidence

  1. Search messages

    Gmail

    Technically inspected · Workflow not yet practically tested

    Details

    Provider API: gmail.users.messages.list

    GET gmail/v1/users/{userId}/messages

    Permissions

    Documented scope alternatives

    • https://mail.google.com/
    • https://www.googleapis.com/auth/gmail.metadata
    • https://www.googleapis.com/auth/gmail.modify
    • https://www.googleapis.com/auth/gmail.readonly

    Do not request all scopes. Select the least privileged scope that covers the operation and resource.

    Costs and limits

    The provider describes standard use or use below its daily threshold without an additional API fee and announces future overage charges. Account, storage and connector costs may apply separately. Total cost has not been checked.

    Source ·

    Quotas apply per project and user. Check the limits assigned to your project; older Google projects may retain different quotas.

    Source · Last confirmed:

    Search matching registry entries

  2. Read a message

    Gmail

    Technically inspected · Workflow not yet practically tested

    Details

    Provider API: gmail.users.messages.get

    GET gmail/v1/users/{userId}/messages/{id}

    Permissions

    Documented scope alternatives

    • https://mail.google.com/
    • https://www.googleapis.com/auth/gmail.addons.current.message.action
    • https://www.googleapis.com/auth/gmail.addons.current.message.metadata
    • https://www.googleapis.com/auth/gmail.addons.current.message.readonly
    • https://www.googleapis.com/auth/gmail.metadata
    • https://www.googleapis.com/auth/gmail.modify
    • https://www.googleapis.com/auth/gmail.readonly

    Do not request all scopes. Select the least privileged scope that covers the operation and resource.

    Costs and limits

    The provider describes standard use or use below its daily threshold without an additional API fee and announces future overage charges. Account, storage and connector costs may apply separately. Total cost has not been checked.

    Source ·

    Quotas apply per project and user. Check the limits assigned to your project; older Google projects may retain different quotas.

    Source · Last confirmed:

    Search matching registry entries

  3. Extract date and time zone

    Not documented

  4. Check availability

    Google Calendar

    Technically inspected · Workflow not yet practically tested

    Details

    Provider API: calendar.freebusy.query

    POST freeBusy

    Permissions

    Documented scope alternatives

    • https://www.googleapis.com/auth/calendar
    • https://www.googleapis.com/auth/calendar.events.freebusy
    • https://www.googleapis.com/auth/calendar.freebusy
    • https://www.googleapis.com/auth/calendar.readonly

    Do not request all scopes. Select the least privileged scope that covers the operation and resource.

    Costs and limits

    The provider describes standard use or use below its daily threshold without an additional API fee and announces future overage charges. Account, storage and connector costs may apply separately. Total cost has not been checked.

    Source ·

    Quotas apply per project and user. Check the limits assigned to your project; older Google projects may retain different quotas.

    Source · Last confirmed:

    Search matching registry entries

  5. Create an event

    Google Calendar

    Technically inspected · Workflow not yet practically tested

    Details

    Provider API: calendar.events.insert

    POST calendars/{calendarId}/events

    Permissions

    Documented scope alternatives

    • https://www.googleapis.com/auth/calendar
    • https://www.googleapis.com/auth/calendar.app.created
    • https://www.googleapis.com/auth/calendar.events
    • https://www.googleapis.com/auth/calendar.events.owned

    Do not request all scopes. Select the least privileged scope that covers the operation and resource.

    Costs and limits

    The provider describes standard use or use below its daily threshold without an additional API fee and announces future overage charges. Account, storage and connector costs may apply separately. Total cost has not been checked.

    Source ·

    Quotas apply per project and user. Check the limits assigned to your project; older Google projects may retain different quotas.

    Source · Last confirmed:

    Search matching registry entries

Tests and limitations

There is no complete practical calendar report or calendar scenario in the local mail–file–table runner. API coverage does not prove correct date interpretation or invitation behavior.

Public verification reports · Open the local runner and instructions

Alternatives

Create the event manually as a first step. The planner can recalculate with Outlook and Microsoft Calendar; switching providers does not remove the interpretation gap.

Open the matching plan · All tasks

tracevero · https://tracevero.com/tasks/prepare-calendar-events-from-email