Integration setup
n8n setup for FrankKi
Design a manual, human-reviewed FrankKi workflow without claiming unsupported transport compatibility.
Setup
- 1.Use Manual Trigger only. Do not import the workflow with a schedule or webhook enabled.
- 2.Confirm that the installed n8n version explicitly supports Streamable HTTP in its MCP Client Tool before entering https://mcp.frankki.app. The currently reviewed documentation only promises SSE.
- 3.If that transport is supported, store the FrankKi token in n8n Bearer credentials and expose only the health, address, draft, preview, quote, approval, send, and status tools required by the workflow.
- 4.Attach n8n human review to every send-side tool. Show the recipient summary, every preview page, exact quote, delivery type, maxCostEuros, and stable clientOrderId.
- 5.If the installed node remains SSE-only, stop. Do not emulate MCP with ad hoc HTTP Request nodes unless a separately verified protocol bridge is introduced and tested.
Required FrankKi safety boundary
Validate the address, create a stable draft, inspect every preview page, obtain a fresh quote, set maxCostEuros, persist a stable clientOrderId, and obtain an explicit human decision before a live submission. Framework approval controls supplement FrankKi approval; model text never substitutes for the human decision.
Continue with canonical agent onboarding, the draft guide, send guide, and error recovery.
Trust and live status
Machine-readable service facts and the current operational status of the partner interface are publicly available at all times, no login needed.