Google Idx Live Trigger icon

Google Idx Live Trigger

Triggers the workflow on a given schedule

Google Idx Live Trigger

AI-generated

Overview

The Google Idx Live Trigger node is a scheduled trigger designed to run workflows on user-defined intervals or cron expressions. It integrates with Google Workstations APIs to monitor the status of configured workstations and automatically triggers workflow executions based on the schedule and workstation states.

Typical use cases include:

  • Automatically checking the status of Google Workstations at regular intervals.
  • Restarting stopped workstations and refreshing access tokens as needed.
  • Running workflows that depend on live data from Google Workstations without manual intervention.

For example, you could set this node to trigger every day at midnight to verify if any workstations have stopped and start them automatically, or to refresh access tokens before they expire.

Properties

Name Meaning
Trigger Rules Defines one or more scheduling rules for triggering the workflow. Each rule can specify an interval type (seconds, minutes, hours, days, weeks, months) or a custom cron expression.
- Seconds Number of seconds between each trigger (e.g., every 30 seconds).
- Minutes Number of minutes between each trigger (e.g., every 5 minutes).
- Hours Number of hours between each trigger (e.g., every 1 hour).
- Days Number of days between each trigger (e.g., every 1 day). Also allows specifying the hour and minute of the day to trigger.
- Weeks Number of weeks between each trigger (e.g., every week). Allows selecting specific weekdays to trigger on and the hour/minute of the day.
- Months Number of months between each trigger (e.g., every month). Allows specifying the day of the month, hour, and minute to trigger.
- Custom (Cron) A custom cron expression defining the exact schedule. Users can input standard cron syntax including seconds, minutes, hours, day of month, month, and day of week.

Output

The node outputs an array of JSON objects, each representing the status of a monitored Google Workstation at the time of the trigger. Each output item includes:

  • statusCode: HTTP-like status code indicating the workstation state (e.g., 200 for running, 401 for expired token, 404 for stopped).
  • status: Human-readable status string such as "running", "accessToken-exp" (expired), "stopped", or "unknown".
  • data: The name of the workstation.
  • accessToken: If refreshed during the trigger, the new access token for the workstation.
  • expireTime: Expiration time of the access token.
  • workspaceRestarted: Boolean flag indicating if the workstation was restarted during this trigger execution.
  • Additional timestamp fields describing when the trigger fired, formatted in various human-readable ways and including timezone information.

No binary data is output by this node.

Dependencies

  • Requires an API authentication token credential for Google OAuth2 to access Google Workstations APIs.
  • Uses external libraries for cron scheduling and timezone handling.
  • Needs network access to Google Workstations API endpoints.
  • The node expects configuration of Google Workstations environments and credentials containing workspace details.

Troubleshooting

  • Invalid Cron Expression: If a custom cron expression is invalid, the node throws an error with a message pointing to https://crontab.guru/ for help. Verify your cron syntax carefully.
  • Failed to Generate Access Token: Errors generating access tokens usually indicate credential issues. Check that the OAuth2 credentials are valid and have required scopes.
  • Failed to Start Workstation: If the node cannot start a stopped workstation, ensure the credentials have permissions and the workstation exists.
  • No Triggers Occurring: Confirm that the trigger rules are correctly configured and that the workflow is activated (not just saved).
  • Timezone Issues: The node uses the workflow's timezone setting; incorrect timezone may cause unexpected trigger times.

Links and References

Discussion