Skip to the operations

AI

Anthropic in a decision flow.

A Connection node calls Anthropic mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.

Category
AI
Type
Integration
Authentication
api_key
Test environment
Production host only

What a flow can call

4 operations, each one a step you can place on the canvas.

  1. POST/v1/messages

    Ask a model (Messages)

    One request, one answer. max_tokens is required and is a hard ceiling on the reply — if it is hit the response comes back truncated with stop_reason "max_tokens" rather than failing.

  2. POST/v1/messages

    Extract structured JSON

    Same endpoint, constrained to a JSON schema so the reply parses without a regex.

  3. POST/v1/messages/count_tokens

    Count tokens before sending

    Returns the input token count for a request without running it.

  4. GET/v1/models

    List available models

    Model ids, context windows and capabilities as the account sees them.

Where it sits in the decision

A provider call is a node, not a side effect.

The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.

Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Anthropic returned at the time is in the trace, not re-fetched from a service whose answer has since changed.

  • 01Add Anthropic as a connection, with your credentials.
  • 02Place a Connection node and choose the operation.
  • 03Read the response in the rules, tables and branches that follow.
  • 04Test the whole path in Sandbox before it carries live traffic.

Ready when you are

Wire Anthropic into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs