Anthropic
AI & modelsAPI keyConnection test available
Claude models for AI extract, transform, classify and agent nodes.
Anthropic has no typed nodes of its own: it connects as a stored credential that 8 generic nodes use — the node picks Anthropic from the connection you select.
Before you connect Anthropic
- Authentication
- API key
- Credential
- {"api_key"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The provider adapter is chosen from the connection; `model` must belong to it.
- Only prompt_injection, topics and language call a model. A guard that runs pii / secrets / length needs no credential.
- Only op=summarize calls a model; get / append / clear need no credential at all. The provider adapter is chosen from the connection and `model` must belong to it.
Prerequisites are taken from the connection notes of the nodes listed below that accept your Anthropic credential.
What you can do with Anthropic
Operations of the generic nodes your Anthropic connection drives, grouped by what they do to your data.
Other operations 8
- AI Agent
- AI Classify
- AI Extract
- AI Generate
- AI Guard
- LLM Call
- and 2 more
Nodes that use your Anthropic connection
These generic nodes accept your Anthropic credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.
- AI Agentai.agentTool-using LLM agent: model + memory + tools, with a step-by-step trace.
- AI Classifyai.classifyPick one label from a fixed list, with a confidence score.
- AI Extractai.extractPull structured fields out of text against a JSON Schema, with optional human review.
- AI Generateai.generateFill a {{var}} prompt template from the input and generate free text.
- AI Guardai.guardCheck text for PII, secrets, prompt injection, topics, length or language.
- LLM Callai.llmFree-form prompt to any configured LLM provider, optionally JSON-schema constrained.
- AI Memoryai.memoryRead, extend, clear or summarise an ai.agent conversation history.
- AI Transformai.transformSummarize, translate, paraphrase or clean text with a curated prompt.
A sample Anthropic workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Anthropic trigger is needed.
- 2AI Agentai.agentTool-using LLM agent: model + memory + tools, with a step-by-step trace.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Templates that use Anthropic
- Q&A over a fetched documentAnswer a question about any public document: fetch it over HTTP, hand the text plus the question to an LLM with a grounding prompt, and post the answer to a callback URL.
- Document extraction to APIReceive a PDF (base64) by webhook, parse it, extract structured fields with a JSON schema, reshape them and POST the record to your API.
- Inbox triage: classify and route emailEvery 15 minutes, fetch the next unread email, classify it (urgent / billing / general) and route urgent ones to the on-call inbox with an auto-acknowledgement.
- AI support agent with order lookupA webhook hands a customer message to a tool-using agent that can look up the order over HTTP, then the answer is emailed back.
- AI screen, human approve, then sendClassify an inbound request, ask a reviewer to approve or reject it, and email the requester the outcome.
- Extract with human clarification on low confidenceExtract structured data from text; when the model is unsure it pauses and asks a person to pick from candidates, then the record is posted.
- First notice of loss: extract, validate, triageA claim notification arrives by webhook; AI extracts the loss details, the payload is validated, an adjuster triages it and the claim is opened in Iris.
- Sales inbox: qualify and routePoll the sales mailbox, classify each email as lead / existing customer / vendor, create Iris records for new leads and forward the rest to the right team.
- Scheduled API digest by emailEvery weekday morning pull a JSON summary from your API, have an LLM turn it into three bullet points and email the team.
Anthropic questions
- How does OCNORA authenticate with Anthropic?
- With a stored API key credential, shaped {"api_key"}. A connection test can check it when you add it.
- What can I automate with Anthropic?
- Anthropic has no typed nodes of its own. Your Anthropic connection is used by AI Agent (ai.agent), AI Classify (ai.classify), AI Extract (ai.extract), AI Generate (ai.generate), AI Guard (ai.guard), LLM Call (ai.llm) and 2 more.
- What if the Anthropic operation I need is not listed?
- Where Anthropic has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Anthropic?
- Yes: 9 templates, listed above.
- How are Anthropic calls controlled?
- Every call and every run step is audited, runs count against the tenant’s token and USD budgets, and Workflow Health pre-flights the workflow when you save it.
More in AI & models
See your first Anthropic workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.