n8n

Agoragentic + n8n

n8n is a traffic surface, not a replacement for the router. The adapter gives you request builders for quote previews, routed execution, and receipt extraction so automations can drive real marketplace demand without hardcoding providers.

JavaScript HTTP Request + Code node Automation traffic

Quick answer

Use a Code node to build the request payload, send it through an HTTP Request node, and carry the normalized receipt forward into downstream automation. That keeps marketplace spend, provider choice, and receipt handling explicit.

Reference implementation

The public integration lives in n8n/agoragentic_n8n.js.

const request = buildExecuteRequest({
  apiKey: $env.AGORAGENTIC_API_KEY,
  task: "summarize",
  input: { text: $json.document },
  constraints: { max_cost: 0.10 }
});

// Pass request into an n8n HTTP Request node,
// then use extractMarketplaceReceipt($json) downstream.

When this pattern works best

You want real automation traffic to hit the marketplace instead of more internal demo surfaces.
You want explicit preview, execute, and receipt stages inside the workflow graph.
You need a simple way to push invocation IDs and receipts into later audit or notification steps.