TTP Request Node - Payload Configuration { "model": "claude-sonnet-4-6", "max_tokens": 1024, "temperature": 0.2, "system": [ { "type": "text", "text": "You are a data classification engine. Output only the requested category. No explanations.", "cache_control": { "type": "ephemeral" } } ], "messages": [ { "role": "user", "content": "Classify the following support request:\n\n{{ $json.ticket_body }}" } ] }

**Step 3: Extract & Validate the Response**
Claude returns a structured JSON object. The generated text lives in `content[0].text`. In n8n, extract it safely with a fallback to prevent pipeline breaks on malformed responses:

```javascript
// n8n Expression for Response Extraction
{{ $json.content[0]?.text?.trim() || 'unclassified' }}

Step 4: Route Based on Inference Connect the HTTP Request node to a Switch node. Evaluate the extracted category and branch to downstream actions (Slack notification, CRM update, email reply). Add a Wait node (1–2 seconds) between consecutive Claude calls when processing arrays to respect rate limits.

Step 5: Implement Batch Processing for Non-Real-Time Workloads For workflows that don’t require immediate responses (e.g., SEO meta generation, weekly digest compilation), route payloads to the Batch API:

{
  "requests": [
    {
      "custom_id": "post_001",
      "params": {
        "model": "claude-sonnet-4-6",
        "max_tokens": 150,
        "messages": [
          { "role": "user", "content": "Generate SEO meta for: {{ $json.post_title }}" }
        ]
      }
    }
  ]
}

Batch jobs process asynchronously. Poll the POST /v1/messages/batches/{batch_id} endpoint or use n8n’s Schedule Trigger to retrieve results once Anthropic marks the batch as ended.

Pitfall Guide

Production Bundle

Action Checklist

• Store Anthropic API keys in n8n’s Credential Manager; never embed in node JSON
• Set max_tokens and temperature explicitly on every inference call
• Isolate system prompts in the system array with cache_control: { type: "ephemeral" }
• Add an Error Trigger node with retry logic and exponential backoff for 429/5xx responses
• Implement token truncation in a pre-processing Code node for unstructured inputs
• Route non-real-time workloads to the Batch API endpoint for 50% cost reduction
• Log all inputs and outputs to a structured sink (Google Sheets, PostgreSQL, or n8n execution logs) for debugging
• Pin model versions explicitly; avoid wildcard references like claude-sonnet-4-*

Decision Matrix

Configuration Template

Copy this template into an n8n HTTP Request node. Replace credential references with your n8n credential names.

{
  "method": "POST",
  "url": "https://api.anthropic.com/v1/messages",
  "authentication": "predefinedCredentialType",
  "credentialType": "anthropicApi",
  "sendHeaders": true,
  "headerParameters": {
    "parameters": [
      { "name": "anthropic-version", "value": "2023-06-01" },
      { "name": "content-type", "value": "application/json" }
    ]
  },
  "sendBody": true,
  "bodyParameters": {
    "parameters": [
      { "name": "model", "value": "claude-sonnet-4-6" },
      { "name": "max_tokens", "value": "1024" },
      { "name": "temperature", "value": "0.2" },
      { "name": "system", "value": "[{\"type\":\"text\",\"text\":\"You are a classification engine. Output only the category. No explanations.\",\"cache_control\":{\"type\":\"ephemeral\"}}]" },
      { "name": "messages", "value": "[{\"role\":\"user\",\"content\":\"Classify: {{ $json.input_data }}\"}]" }
    ]
  },
  "options": {
    "timeout": 15000,
    "response": { "response": { "fullResponse": false } }
  }
}

Quick Start Guide

1. Install n8n: Run npx n8n locally or deploy via Docker. Access the UI at http://localhost:5678.
2. Create Credential: Navigate to Credentials → Add Anthropic API → Paste key from console.anthropic.com → Save.
3. Build Workflow: Add a Trigger node (Webhook, Schedule, or App) → Add HTTP Request node → Paste the Configuration Template → Connect to a Switch node for routing.
4. Test & Validate: Execute with sample payload. Verify $json.content[0].text extraction. Check execution logs for token usage and latency.
5. Deploy: Enable production mode, attach Error Trigger for fallback routing, and schedule batch jobs if applicable. Pipeline is live in under 5 minutes.