Messaging, documents, and calendar work

Manage event calendar bookings

Reconcile one Google Calendar booking by stable booking ID, including cancellation.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Stable booking identity prevents duplicate inserts; provider errors are uncertain.

What to customize

Set calendar ID/timezone and bind GOOGLE_CALENDAR_TOKEN.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "{\"bookingId\":\"b1\",\"title\":\"Demo\",\"start\":\"2026-09-14T10:00:00Z\",\"end\":\"2026-09-14T11:00:00Z\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "dry_run",
    "output3": "{\"calendar\":\"team@example.com\",\"bookingId\":\"b1\",\"eventId\":\"7dc96f776c8423e57a2785489a3f9c43\"}"
  }
}

Returned fields

output1: booked, updated, cancelled, planned, or error
output2: event ID or reason
output3: JSON provider result

What changes when it runs

In live mode looks up an extended property and inserts, patches, or deletes one Google Calendar event.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe