> ## 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.

# Baserow on Vortex IQ

> Monitor Baserow publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Baserow publishing, engagement and freshness, and catch decay before organic reach erodes.

[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=baserow)

<CardGroup cols={5}>
  <Card title="10">
    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="9">
    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="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </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 (10)">
    ### Monitor performance

    10 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 (7 signals)">
        | Signal                      | Alert behaviour      | What it tracks                                                                                                                           |
        | --------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
        | **Field Count**             | Watch only           | Number of columns on the monitored table - baseline for schema-drift detection.                                                          |
        | **Freshness Lag (minutes)** | Alert band 60 / 1440 | Same stale-table detector as Hours Since Last Row Change, in minutes - the byo\_data\_source archetype's freshness\_lag band is minutes. |
        | **Open-Status Rows**        | Alert band 10 / 50   | Rows whose status is not in the done set - the unactioned queue (returns / order exceptions). Gated on a configured status field.        |
        | **Row Count**               | Watch only           | Total rows in the monitored table - from the `count` field on the list-rows response.                                                    |
        | **Rows Added (24h)**        | Merchant rule        | New rows in the last 24h - needs a Created-on field on the table (Baserow does not expose row creation time otherwise).                  |
        | **Saved Views**             | Watch only           | Number of saved views (grid / gallery / form / kanban / calendar) on the table.                                                          |
        | **Tables in Database**      | Watch only           | Inventory of tables in the parent database - id, name, row count. Gated on a configured database\_id.                                    |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal                          | Alert behaviour   | What it tracks                                                                                                                 |
        | ------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
        | **Hours Since Last Row Change** | Alert band 6 / 24 | Stale-table detector - hours since the most-recent row edit. >24h on a live ops table means the upstream feed has gone silent. |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                       | Alert behaviour | What it tracks                                                                                                                                        |
        | -------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Open Order-Exception Rows on Live Orders** | Merchant rule   | Manual order-exception queue rows that map to live, paid ecom orders still sitting unresolved - revenue stuck in a spreadsheet. Needs an ecom sibling |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                 | Alert behaviour   | What it tracks                                                                                                                                   |
        | ---------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Empty Field Rate %** | Alert band 2 / 15 | Share of field values left blank across the sampled rows (up to the 200-row page cap), measured against every column returned by the Fields API. |
      </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="Data-source API token invalid or access revoked">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this token fails, VortexIQ stops pulling data from this source entirely, and every card and finding built 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: `BYO-AUTH-001`
      </Accordion>

      <Accordion title="Source not updated in over 24h (stale data)">
        **Severity** high · **Outcome** Run operations · **Fix status** Report only

        A source that has not updated in over a day means every conclusion drawn from it describes yesterday; the staleness is invisible unless surfaced.

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

        Reference: `BYO-FRESH-001`
      </Accordion>

      <Accordion title="Required-field empty rate above 15%">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When required fields are empty in more than 15 percent of rows, every downstream calculation inherits the gaps and quietly under-reports.

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

        Reference: `BYO-DATA-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 **6 read** and **3 write** operations across databaserowtables, databasefieldtables, databasetabledatabases, databaseviewtables, users, workspaces on Baserow. 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=baserow)

    #### Ready to build your first Baserow 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 |
      | ---------------------- | --------------- | ---------------- |
      | databaserowtables      | 1               | 3                |
      | databasefieldtables    | 1               | 0                |
      | databasetabledatabases | 1               | 0                |
      | databaseviewtables     | 1               | 0                |
      | users                  | 1               | 0                |
      | workspaces             | 1               | 0                |

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