n8n automation

Call Jev from n8n via community node or HTTP; gate side effects on confidence — community node ≠ TypeSafe product.

Hands-on: call Jev from n8n

Automation tools are fine hosts for System One as long as the model never becomes the executor.

Suggested shape

1. Trigger / webhook receives payload.
2. Function node builds state + questions.
3. HTTP Request → TypeSafe System One endpoint with TYPESAFE_API_KEY.
4. IF / Switch nodes on allow-listed labels + confidence bands.
5. Only then: ticket create, Slack notify, etc.

Secrets

Store the API key in n8n credentials—not in workflow JSON checked into git.

Limits

n8n examples online change quickly; verify HTTP paths and body shapes against current docs. Community nodes are optional convenience, not a requirement.

Sources

• Quick start
• SDK overview