Read
Query the governed datasets and views selected for the runbook.
Overview
Use Teradata as a governed source or destination in a Context runbook. Configure the exact records and actions each agent can access.
- · Vendor-supported OAuth or scoped service credentials
- · Read and write access configured separately
- · Tool calls and outcomes recorded per run
Connector contract
Control what agents can do in Teradata.
Exact authentication methods and available scopes depend on your Teradata plan and deployment. Context keeps the connector configuration explicit.
Act
Materialize approved results to a designated table or workspace.
Verify
Keep query inputs and returned records attached to the run trace.
Set up the connection
- 01
Authenticate
Connect Teradata with an admin-approved OAuth flow or scoped credential supported by the vendor.
- 02
Choose scope
Select the accounts, workspaces, projects, or resources available to the runbook.
- 03
Map policy
Set read and write permissions, reviewer gates, and the identity used for each action.
- 04
Test a run
Verify one read, one permitted action, and the resulting audit record before rollout.
Build with Teradata
Teradata can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →
More in Data & warehouses
Connect Teradata to Context.
Request demo