> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Cloud Platform on Vortex IQ

> Monitor Google Cloud Platform health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Google Cloud Platform health, cost and reliability signals, and catch incidents and runaway spend early.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gcp)

<CardGroup cols={5}>
  <Card title="20">
    performance signals
  </Card>

  <Card title="3">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (20)">
    ### Monitor performance

    20 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (16 signals)">
        | Signal                          | Alert behaviour    | What it tracks                                                                                                                   |
        | ------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
        | **Active Projects**             | Watch only         | Count of projects\[] with lifecycleState == ACTIVE from GET /v1/projects.                                                        |
        | **Avg Daily Spend (30d)**       | Watch only         | 30d net\_cost / count of distinct usage days with net\_cost > 0.                                                                 |
        | **Billing Accounts**            | Watch only         | Count of billingAccounts\[] from GET /v1/billingAccounts.                                                                        |
        | **Closed Billing Accounts**     | Watch only         | Count of billingAccounts\[] with open == false; a closed account with live projects stops workloads.                             |
        | **Daily Spend Trend**           | Watch only         | net\_cost summed per usage day over the last 30d of the billing export.                                                          |
        | **GCP Spend (30d)**             | Alert band 10 / 50 | SUM(net\_cost) from the BigQuery billing export (SUM(cost) + credits) where usage date >= 30d ago. Needs billing\_export\_table. |
        | **GCP Spend (7d)**              | Watch only         | SUM(net\_cost) from the billing export where usage date >= 7d ago.                                                               |
        | **Largest Daily Spend (30d)**   | Watch only         | MAX over usage days of the per-day net\_cost sum in the last 30d; spots one-off blowout days.                                    |
        | **Month-to-Date Spend**         | Watch only         | SUM(net\_cost) from the billing export where usage date >= first day of the current month.                                       |
        | **Open Billing Accounts**       | Watch only         | Count of billingAccounts\[] with open == true from GET /v1/billingAccounts.                                                      |
        | **Previous 30d Spend**          | Watch only         | SUM(net\_cost) for usage days 31-60 ago; the comparison base for the spend trend.                                                |
        | **Projects Pending Delete**     | Watch only         | Count of projects\[] with lifecycleState DELETE\_REQUESTED or DELETE\_IN\_PROGRESS; anything here is disappearing in \<=30 days. |
        | **Projects Total**              | Watch only         | Count of projects\[] from GET /v1/projects. Renders with any working service account.                                            |
        | **Projects by Lifecycle State** | Watch only         | projects\[] grouped by lifecycleState from GET /v1/projects.                                                                     |
        | **Service Concentration (30d)** | Watch only         | Top service 30d net\_cost / total 30d net\_cost x 100; how concentrated the bill is in one service.                              |
        | **Spend Spike Alert**           | Alert band 10 / 50 | 30d net\_cost change vs the prior 30d from the billing export; fires on a spike per the ai\_spend\_trend band.                   |
      </Accordion>

      <Accordion title="Catalogue quality (3 signals)">
        | Signal                        | Alert behaviour | What it tracks                                                                                         |
        | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------ |
        | **Active Services (30d)**     | Watch only      | Count of distinct service.description values with net\_cost > 0 in the last 30d of the billing export. |
        | **Cost by Service (30d)**     | Watch only      | net\_cost grouped by service.description over the last 30d of the billing export; top 10 services.     |
        | **Top Service by Cost (30d)** | Watch only      | The single largest service.description by 30d net\_cost; the service name is the card detail.          |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour    | What it tracks                                                                                                                                         |
        | ---------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Cloud Health Score** | Alert band 90 / 70 | 0-100 composite over whatever is readable: token exchange ok (100) + pct of projects ACTIVE (/v1/projects) + pct of billing accounts open (/v1/billing |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (3)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="API key invalid, expired or lacking the scopes the cards need">
        **Severity** high · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it goes stale from that moment, silently, until someone notices the numbers stopped updating.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-AUTH-001`
      </Accordion>

      <Accordion title="Spend up more than 50% vs the prior period">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a misconfigured autoscaler, quietly running up a bill nobody approved.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-SPEND-001`
      </Accordion>

      <Accordion title="Usage dropped more than 50% vs the prior period (silent stall)">
        **Severity** medium · **Outcome** Control risk and change · **Fix status** Report only

        Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CLOUD-USAGE-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **2 read** and **2 write** operations across https:bigquerygoogleapicombigqueryprojectquerys, https:cloudbillinggoogleapicombillingaccounts, https:oauth2googleapicomtokens, projects on Google Cloud Platform. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gcp)

    #### Ready to build your first Google Cloud Platform workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource                                        | Read operations | Write operations |
      | ----------------------------------------------- | --------------- | ---------------- |
      | https:bigquerygoogleapicombigqueryprojectquerys | 0               | 1                |
      | https:cloudbillinggoogleapicombillingaccounts   | 1               | 0                |
      | https:oauth2googleapicomtokens                  | 0               | 1                |
      | projects                                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>