Make

Tracira has a native Make app. Add monitoring to any scenario with a single module, no HTTP setup required.

Install the Tracira app for Make

Open the Tracira app invitation link and click Install. This only needs to be done once per Make organization.

Add the Log Execution module to your scenario

In your scenario, click + after the module that generates the AI output. Search for Tracira and select Log Execution.

Connect your workspace

Click Add to create a connection. When prompted for an API key, paste your webhook token from the Integrations tab in your Tracira workspace.

Map the fields

At minimum, map project and output from the previous module. Optional fields:

task: groups logs inside the project
input: the prompt sent to the AI
model, latencyMs, costUsd: for analytics
sync: set to true to get the verdict inline (gate mode)

Branch on the verdict (gate mode)

When sync is enabled, add a Router after the Tracira module:

Route 1, filter: {{tracira.status}} = pass then continue
Route 2, filter: {{tracira.status}} = flagged then alert or stop

Field mapping

// Log Execution module fields
{
  "project": "{{1.project}}",
  "output": "{{1.aiOutput}}",
  "task": "Tone Validator"
  // sync left blank, returns id + pending instantly
}

// Set sync = true to get the verdict inline
{
  "project": "{{1.project}}",
  "output": "{{1.aiOutput}}",
  "task": "Tone Validator",
  "sync": true
}

Verdict response

{
  "ok": true,
  "id": "b1c2d3e4-...",
  "status": "pass",
  "verdict": {
    "pass": true,
    "rules": [{ "name": "Tone Validator", "triggered": false }]
  }
}

{
  "ok": true,
  "id": "b1c2d3e4-...",
  "status": "flagged",
  "verdict": {
    "pass": false,
    "rules": [{ "name": "Tone Validator", "triggered": true, "reason": "Tone too aggressive" }]
  }
}

For small files, map them into the Attachments field of the Create Log module. Pick Upload file and map the binary, or From URL and paste an HTTPS link. Tracira auto-detects whether each attachment is an image, audio, or document.

Large files: the Upload File module

Inline attachments travel inside the Create Log request, which is capped at 4.5 MB. For larger files (a multi-page scanned PDF, a high-res image) add the Upload File module before Create Log. It uploads the binary straight to Tracira storage (no size cap from the request body) and returns a key, supporting files up to 32 MB.

Add the Upload File module

After the module that produces the file, add Tracira → Upload File. Map the binary into File and its name into File name.

Add Create Log after it

In Create Log, under Attachments, add an item with source Tracira upload and map the Upload File module's Attachment Key output into the key. That is the only mapping needed; the file is linked to this log automatically.

[ AI module ] → [ Tracira: Upload File ] → [ Tracira: Create Log ]

Why two modules

The file is uploaded directly to storage, bypassing the request-body limit, then the log references it by key. This is the same flow any client uses through the public API (POST /api/uploads, then POST /api/logs), just packaged as a module.

Tip

Leave sync blank for fire-and-forget logging (Make continues instantly). Set it to true only when you need to gate the scenario on the evaluation result.