n8n

Tracira has a native n8n node. Add monitoring to any workflow with a single node, no HTTP Request configuration required: connect once with your token, then branch on the verdict with an IF node.

Verdict response

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

Reacting to decisions: the Tracira Trigger node

The package also ships a Tracira Trigger node ("Watch decisions") that starts a workflow the moment an output gets a verdict or a human decision in Tracira - approved, rejected, or sent back for changes. Activating the workflow registers the trigger with Tracira automatically; there is nothing to set up in the dashboard.

The typical human-in-the-loop pattern uses two workflows:

Workflow A: [ AI drafts ] → [ Tracira: Send an output ]           (submit for review)
Workflow B: [ Tracira Trigger ] → [ IF decision = approved ] → [ Send the reply ]

Decision events include the AI output and its metadata, so the approval workflow can deliver the approved reply with no extra lookup.

Logging a conversation

For a chatbot workflow, send one output per exchange - do not paste the full message history into every output:

• Input Text: only the newest user message (the one your AI just replied to)
• AI Output: the reply to it
• Session ID: your conversation or thread ID (e.g. {{ $json.threadId }}) - the same value on every turn

Tracira stitches all outputs sharing a Session ID into a single conversation thread, so reviewers read the whole exchange in order with nothing repeated.

Hosted instructions (self-improving prompts)

Tracira can host the instructions (system prompt) your AI runs with, so the prompt lives next to the people reviewing its output instead of hardcoded in your AI node. Reviewers see, edit, and restore every version on the Instructions page in the dashboard; your workflow always drafts with the latest.

1. Add Tracira → Get Instructions at the start of the workflow. Use the same Project Name and Task Name as your Send an output node, and put your prompt into Starter Instructions - it is saved as version 1 on the very first run. Map the returned Instructions into your AI node's system message.
2. In Send an output, map the returned Version into Instructions Version so every output links back to the exact instructions that produced it.
3. To make the prompt self-improving, react to changed decisions with the Tracira Trigger node: have an AI step rewrite the current instructions to follow the reviewer's comment, then save the result with Tracira → Update Instructions. The next run fetches the improved version automatically.

Attaching files

For small files, use the Input Attachments or Output Attachments fields on Send an output. Each attachment has three sources: Upload File (map a binary field, keep under ~3 MB), From URL (a publicly accessible HTTPS link), or Tracira Upload (a key from the Upload a File operation).

For large documents, add the Tracira → Upload a File operation before Check an output. It uploads the binary straight to Tracira storage (up to 32 MB) and returns a key; map that key into an attachment with source Tracira Upload.

[ AI node ] → [ Tracira: Upload a File ] → [ Tracira: Send an output ]

Manual setup without the node

Prefer to wire it up yourself, or running an n8n version where the community node is unavailable? Everything above is a thin wrapper over the public API: send a POST to https://tracira.com/api/logs from an HTTP Request node with an Authorization: Bearer YOUR_TOKEN header. See the HTTP guide for the payload reference.