Tessra
Menu
ProductIntegrationsDocsCortexDemo

Integrations

Connect Tessra across decision, consent, and execution

Tessra sits between where actions are proposed, where humans approve, and where work runs—enforcing policy and recording receipts.

Control plane topology

Decision systems  (agents, Cortex, apps)
        ↓
     Tessra  (policy · consent routing · execution control)
        ↓
Consent systems  (human approval & delegation)
        ↓
Execution systems  (webhooks, Stripe, internal APIs)
        ↓
Receipts in Snowflake

Tessra does not replace your agents or your APIs. It governs the handoff between them.

Every governed action flows through three surfaces: where it is proposed, where it is approved, and where it is executed.

Decision systems

Where actions originate.

Snowflake Cortex

Native

Submit governed actions directly from SQL agents using native procedures.

View Cortex integration →

Internal agents / services

Generic

Any system that can call SQL or HTTP can propose actions through Tessra.

Future

Additional SQL warehouses and agent hosts (e.g. Databricks) can follow the same request model when you wire them as callers.

Consent systems

Where human approval and delegation happen.

Slack

Default

Route approval requests into Slack with structured actions and audit context.

Email

Generic

Send approval requests via email with secure links and response tracking.

Future

Future

ServiceNow, Jira, and internal approval systems can plug into the same consent interface.

Execution systems

Where approved work runs.

Generic webhook

Default

Send approved actions to any system via secure HTTP callbacks.

Stripe

Reference

Execute real payment flows (refunds, credits) with policy and approval enforcement.

Internal APIs

Custom

Connect to your own services (billing, ops, infra).

How it fits in your stack

Decision → consent → execution, with Tessra as the control plane and Snowflake as the ledger.

  • Decision systems propose governed actions.
  • Tessra evaluates policy and routes consent when humans must decide.
  • Consent surfaces capture approvals and delegation.
  • Execution systems run approved work.
  • Snowflake stores the receipt.

Action lifecycle

DECISION → CONSENT → EXECUTION → RECEIPT

Request shape

Native Snowflake procedures are the reference path; HTTP or SQL callers reuse the same action lifecycle.

Illustrative Cortex call
CALL APP.REQUEST_ACTION_FROM_CORTEX(
  'customer.credit_issue',
  OBJECT_CONSTRUCT(...),
  'reasoning'
);

Works with Cortex today. Same model applies to other agent systems.

Run your first governed actionRead the docs