feat(trigger): add Google Sheets, Drive, and Calendar polling triggers

[waleedlatif1]

Summary

• Add polling triggers for Google Sheets (new rows), Google Drive (file changes), and Google Calendar (event updates)
• Google Drive uses changes.list API with opaque cursor (no clock skew, catches deletes)
• Google Calendar uses updatedMin + singleEvents=true (expanded recurring events)
• Google Sheets uses row count comparison + Drive modifiedTime pre-check (saves Sheets quota)
• Each poller supports: OAuth credentials, configurable filters (event type, MIME type, folder, search term, render options), idempotency, first-poll seeding
• Wire triggers into block configs so trigger UI appears and generate-docs.ts discovers them
• Regenerate integrations.json with new trigger entries
• Update add-trigger skill with polling instructions and versioned block wiring guidance

Type of Change

• New feature

Testing

Tested manually — type-check passes, lint passes, integrations.json regenerated correctly

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Building	Preview, Comment	Apr 10, 2026 1:24am

[cursor]

PR Summary

Medium Risk
Adds new polling-based trigger execution paths (new provider handlers, cron schedules, and UI wiring) and changes idempotency semantics for polling to retry failed keys, which could affect trigger firing and load if misconfigured.

Overview
Adds polling triggers for Google Sheets (new rows), Google Drive (file changes), and Google Calendar (event changes), including new polling provider handlers that fetch deltas, seed state on first run, apply user-configurable filters, and emit events via processPolledWebhookEvent with polling idempotency.

Wires these triggers into the Google blocks via getTrigger(...).subBlocks and triggers.available, registers the new providers in polling/trigger registries, and enables new 1-minute polling cron jobs in helm/sim/values.yaml.

Updates idempotency to support retryFailures (enabled for pollingIdempotency), regenerates integrations.json to expose the new triggers, and expands the add-trigger docs/commands to cover polling trigger creation and versioned block wiring.

^{Reviewed by Cursor Bugbot for commit 47c7b3e. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds polling triggers for Google Sheets (new rows), Google Drive (file changes), and Google Calendar (event updates). It introduces a retryFailures option to the idempotency service, wires all three triggers into their respective block configs, and updates the polling registry and constants. The core failure-handling logic (cursor/timestamp revert on any failure, idempotency deduplication on retry) is well-implemented, consistent with the existing Gmail/Outlook patterns, and the previously-raised issues from earlier review rounds appear resolved.

Confidence Score: 5/5

Safe to merge — all previously raised data-integrity concerns are resolved and the only remaining finding is a minor P2 style inconsistency in error messaging.

All critical issues from prior review rounds (cursor/timestamp revert on failure, partial-failure handling, rate-limit classification for Calendar and Sheets, Drive merge-order, resume-token overshoot) have been addressed. The retryFailures idempotency extension is correctly implemented with no infinite-loop risk. The sole remaining finding is a P2 suggestion to align Drive 403/429 error messaging with Calendar and Sheets for easier log diagnostics.

apps/sim/lib/webhooks/polling/google-drive.ts — missing explicit 403/429 rate-limit error classification in fetchChanges/getStartPageToken (P2 only)

Important Files Changed

Filename	Overview
apps/sim/lib/webhooks/polling/google-drive.ts	New Drive polling handler; cursor-revert, partial-failure handling, and knownFileIds logic are correct. Minor: 403/429 rate-limit response is not explicitly distinguished from other API errors, unlike Calendar and Sheets handlers.
apps/sim/lib/webhooks/polling/google-calendar.ts	New Calendar polling handler; timestamp revert on any failure (failedCount > 0), idempotency key includes updated field for re-edit detection, and rate-limit handling are all correctly implemented.
apps/sim/lib/webhooks/polling/google-sheets.ts	New Sheets polling handler; Drive modifiedTime pre-check, row-count heuristic, partial-failure revert logic, and 403/429 handling in all three API calls are correctly implemented.
apps/sim/lib/core/idempotency/service.ts	Adds retryFailures option: on failure the key is deleted rather than stored, enabling the next poll cycle to retry. pollingIdempotency singleton opts in with retryFailures: true. Logic is correct; no infinite-loop risk since failed keys are deleted before any recursive re-attempt.
apps/sim/triggers/registry.ts	New trigger entries (google_calendar_poller, google_drive_poller, google_sheets_poller) correctly added and imported from kebab-case directories.
apps/sim/lib/webhooks/polling/registry.ts	Three new handlers registered under their provider keys; keys match POLLING_PROVIDERS constants and block trigger configs.

Sequence Diagram

sequenceDiagram
    participant Scheduler as Trigger.dev
    participant Poller as Poll Handler
    participant GoogleAPI as Google API
    participant Idempotency as pollingIdempotency
    participant DB as Webhook State

    Scheduler->>Poller: pollWebhook(ctx)
    Poller->>DB: read providerConfig
    alt First poll
        Poller->>GoogleAPI: get start cursor or seed row count
        GoogleAPI-->>Poller: initial state
        Poller->>DB: persist seeded state
        Poller-->>Scheduler: success, no events emitted
    else Subsequent polls
        Poller->>GoogleAPI: fetch changes since last state
        GoogleAPI-->>Poller: events or rows
        loop For each item
            Poller->>Idempotency: executeWithIdempotency(key, op)
            alt Cache hit
                Idempotency-->>Poller: cached result, no re-fire
            else New execution
                Idempotency->>Poller: run op
                alt Success
                    Poller-->>Idempotency: result stored as completed
                else Failure
                    Poller-->>Idempotency: key deleted for retry
                end
            end
        end
        alt anyFailed is true
            Poller->>DB: revert state to pre-poll values
        else All succeeded
            Poller->>DB: advance state to new cursor or timestamp
        end
    end

Loading

_{Reviews (7): Last reviewed commit: "fix(polling): revert drive cursor on any..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 104690d. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 47c7b3e. Configure here.}