Mattering Automations Anthropic integration

Connect Anthropic's Claude models to Mattering Automations: generate messages inline, submit batches at reduced cost, and collect the results as workflow steps.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations Anthropic integration puts Claude on your automation canvas: generate a response inside a workflow step, submit a batch of message requests for asynchronous processing at reduced cost, and retrieve the results.

Setup is one Anthropic API key. Once connected, the Claude nodes appear in the palette and also become available to any MCP-capable assistant.

Before you start

An Anthropic account with API access at console.anthropic.com.
A Mattering workspace with access to the Automations app.

Create an Anthropic API key

The connector authenticates with an Anthropic API key sent as the x-api-key header.

In the Anthropic Console, open Settings > API keys and click Create Key.

The key is shown once at creation. Copy it now; you cannot view it again later.

Copy the key (it starts with sk-ant).

Connect Anthropic to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose Anthropic from the list.

Click Create new credential, paste the API key, and save. The credential is stored encrypted in Google Secret Manager.

Click Test Connection: Mattering verifies the key against Anthropic's models endpoint.

Click Connect. The Claude nodes appear in your canvas palette.

Verify it works

Open an automation canvas and drop Claude Message onto it. Set a model id and a short messages array, then run a test step: a successful response returns Claude's reply and token usage.

For batches, run Claude Batch with one small request, note the returned batch id, then run Claude Get Batch with that id once processing has ended to collect the results.

Node reference

3 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 1

Claude Get Batch

query_anthropic_get_batch

Fetch the status and results of a Claude message batch

Action nodes 2

Claude Batch

action_anthropic_batch

Submit a batch of message requests to Claude for asynchronous processing at half the standard token cost

Claude Message

action_anthropic_message

Generate a message with Claude

Using the integration

On the automation canvas

Drop Claude Message between a data-gathering node and a delivery node for summaries, classification, or drafting. Values accept template references, so the prompt can pull from any prior step.

Bulk work at reduced cost

Claude Batch submits many requests for asynchronous processing, which Anthropic prices below live calls per its pricing docs. Pair it with Claude Get Batch on a later scheduled run to collect finished results: the right shape for summarizing a backlog or drafting in bulk overnight.

From AI assistants over MCP

The Claude nodes speak MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can drive them, so an assistant can orchestrate a workflow that itself calls Claude for the heavy generation.

Troubleshooting

The node returns a 404 not found error naming a model

The model id is unknown to your account or retired. Set the model field to a current Claude model id you have access to (the node default tracks a current general-purpose model, but a pinned older id can go stale).

Test Connection fails with a 401

The API key is wrong, revoked, or was truncated on paste. Recreate the key in the Anthropic Console and update the credential.

Claude Get Batch returns no results

The batch has not finished processing yet. Batches complete asynchronously (typically minutes, up to 24 hours); poll again later, or set include_results to false for a cheap status-only check first.

The Anthropic MCP

What connecting Anthropic unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

Anthropic is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.