Integration Studio

Transaction Log

Complete record of every outbound API call, connector request, and data exchange — searchable by connector, status, duration, and error type.

The Transaction Log at Integrations → Logs captures every outbound request made by FlowOS — connector calls, transformer invocations, webhook deliveries, and API Builder proxy requests. Use it to audit data exchanges, debug integration failures, and measure connector performance.

Transaction Record Schema

Field	Type	Description
id	varchar(26)	ULID. Prefixed txn_.
connector_id	varchar(26)	FK → connectors.id. Which connector was used.
connector_name	varchar(200)	Connector display name at log time.
operation	varchar(200)	Operation slug, e.g. jira.createIssue.
method	varchar(10)	HTTP method: GET \| POST \| PUT \| PATCH \| DELETE.
url	text	Request URL (credentials redacted).
status	integer	HTTP response status code.
request_headers	jsonb	Outbound headers (Authorization redacted → ***).
request_body	jsonb	Request payload (sensitive fields masked per connector config).
response_headers	jsonb	Response headers.
response_body	jsonb	Response body (truncated at 50KB).
duration_ms	integer	Round-trip time.
error	jsonb	{ code, message } for failed transactions.
source_type	enum	workflow_node \| sdk_artifact \| api_builder \| transformer
source_id	varchar(26)	ID of the workflow run, execution, etc.
environment	enum	development \| staging \| production
created_at	timestamptz	Request timestamp.

Filtering & Search

GET

/api/v1/integrations/logs

List transaction records with filters.

bash

# All failed Jira calls in the last 24h
GET /api/v1/integrations/logs
  ?filter[connector_id]=conn_jira_01
  &filter[status][gte]=400
  &filter[created_at][gte]=2026-05-31

# Slowest connector calls today
GET /api/v1/integrations/logs
  ?filter[created_at][gte]=2026-06-01
  &sort=-duration_ms
  &pageSize=50

# Transactions from a specific workflow run
GET /api/v1/integrations/logs
  ?filter[source_type]=workflow_node
  &filter[source_id]=run_01HX...

Replaying Transactions

Replay any logged transaction with its original request — useful for retrying a failed API call after fixing a configuration issue:

POST

/api/v1/integrations/logs/:id/replay

Replay the request and log a new transaction.

The replay creates a new transaction record linked to the original via replay_of. The connector credentials used are the current credentials, not the ones at time of the original request.

Sensitive Data Masking

The following data is automatically masked in transaction logs:

•Authorization headers (Authorization: Bearer ***).
•Connector credentials (client secrets, API keys).
•Fields marked as sensitive: true in the connector's field schema.
•Common PII field names: password, ssn, credit_card, cvv, token.

Retention & Export

•Transaction logs are retained for 30 days by default.
•Extend to 90 days (Pro plan) or 365 days (Enterprise).
•Export as NDJSON: GET /api/v1/integrations/logs/export?from=2026-05-01&to=2026-06-01.
•Forward to your SIEM in real time via webhook subscription on the integration.transaction.* event group.

Transaction logs complement (but do not replace) connector health monitoring. Use the Circuit Breaker dashboard for real-time availability tracking and the transaction log for historical debugging.