Querying corporate data

The Query corporate data step reads data from Infinite Data inside a flow — a balance, a history, a customer list — without exporting anything and without duplicating the source.

It is deterministic and read-only: no query from this step changes data.

The form

Field	Use
Action	Run a query, or explore the catalog
Query	The SQL, when the action is to run a query

The exploration actions answer what exists: list catalogs, list schemas, list tables, describe a table. They are useful for assembling the query, and for agents that need to orient themselves before asking.

Produces: the rows, the columns, the row count, whether the result was truncated, and the query's identifier.

Who sees what

The query runs with the identity of whoever triggered the run — not with a service account, and not with the identity of whoever built the agent.

That has a direct consequence: the agent widens nobody's access. Someone who cannot see a table in Infinite Data still cannot see it through an agent. Two people running the same agent may get different results, and that is the correct behavior — each one sees what they are entitled to see.

Infinite Data's governance continues to apply in full: masking, row filters, and the audit record. A query made by an agent appears in the Audit Center like any other.

This step requires a person

An agent that uses it does not work when triggered by a schedule or an endpoint. In those cases there is no person behind the run, and the step fails rather than picking an identity on its own.

If you need corporate data in an automatic agent, the way to do it is to publish the read as an automation with its own identity and declared governance, and use Run an automation.

When the result comes back truncated

Large queries are cut off and the result comes marked as truncated. The cut is never silent: a partial result must not look like a complete one.

If it comes back truncated, narrow the query — filter, aggregate, or paginate. Pulling everything into the flow is rarely what you want: the agent decides better with ten relevant rows than with ten thousand.

Common errors

Symptom	Cause	What to do
The step fails saying there is no person	The agent was triggered by a schedule or an endpoint	Trigger it as a person, or move the read into an automation
"Access denied" for one person and not another	Permissions are Infinite Data's, per person	See Understanding access denied
A table does not appear in the catalog	The person has no access to it	See Access problems
Truncated result	The query returns more rows than the limit	Filter or aggregate

Next steps

• Step types
• Data between steps
• Infinite Data