Start with your Google account.

1. Sign in and review permissions

Continue with Google using the account which runs your scripts. TriggerOps requests email identity and Apps Script process history. The private beta depends on the configured test-user list. No Drive content scope is requested.

2. Sync observed activity

The first-run flow imports recent execution metadata. Apps Script API access must be enabled for your account. Project names are not unique identifiers. Account-wide history therefore appears as unverified activity groups.

3. Verify identity and enable monitoring

Open Apps Script project settings, copy the Script ID, and use Link a project. TriggerOps verifies access with a script-scoped process request. Choose Monitor to start watching new executions. Existing historical failures do not open incidents.

Jobs keep their Google process type. Time-driven cadence learning needs at least nine observations and 90% of intervals within tolerance. Editor, web-app, execution-API and irregular event runs have no automatic missed-run schedule. Set an explicit interval only when a job has a known recurring schedule.

4. Connect Telegram

Open Alerts, choose Connect Telegram, open your short-lived bot link and press Start. Check the connection in TriggerOps, then send a test alert. Alerts route only to your verified private chat. A project also supports alert muting.

Remove and restore

Remove from TriggerOps hides the project and pauses monitoring. Use the Hidden projects filter to restore. Restoration keeps monitoring paused. No Google project, source or trigger is deleted.

Optional direct telemetry

Download the SDK and add the file to your test Apps Script project. Create an SDK key in Settings. Set TRIGGEROPS_ENDPOINT, TRIGGEROPS_INGEST_KEY and TRIGGEROPS_PROJECT in Apps Script Script Properties. The SDK includes the actual Script ID automatically.

function hourlySync() {
  return TriggerOps.run('hourlySync', 60, hourlySyncCore_);
}

function hourlySyncCore_() {
  // Your existing business logic.
}

Use a dedicated test project first. Do not alter a production trigger to validate a missed-run incident. The SDK catches transport failures independently from business logic.

Sync and detection limits

Background sync targets a ten-minute interval. Scheduler or Google API delays affect detection. Missed-run detection pauses when the last complete sync is more than 25 minutes old. A one-minute test trigger therefore does not imply a one-minute alert guarantee. Inspect Settings and incident delivery state when diagnosing delays.