# Review a diagram and send comments to Claude

> Leave comments on individual steps of an automation's diagram in APIANT.ai, then have Claude or the assistant apply every pending comment across your automations in one pass.

The automation diagram in APIANT.ai is read-only, but each step's dialog has a **Request a change** box. A comment you queue there is tied to that exact step, so you can describe the change without saying where it goes. Queue comments on as many steps and automations as you like, then ask Claude to apply them; Claude edits every commented step, saves each automation, and reports what it changed.

## Prerequisites

- Claude Code connected to your APIANT account. See [Connect Claude Code](/docs/mcp/claude-code). The assistant can apply comments too.
- Claude signed in as the same APIANT account you use in the browser. Comments belong to the account that queued them.

## Steps

### 1. Open the automation's diagram

From the dashboard, open the automation's diagram, or use the diagram link Claude gave you when it saved the automation.

### 2. Open a step

Select a step on the diagram. Its dialog shows the step's settings, the connected account it uses and its field mappings, followed by **Request a change**.

### 3. Queue a comment

1. Under **Request a change**, describe what should be different about this step.
2. Select **Queue**.

The box is replaced by "Comment saved. Comment on any other steps across your automations, then go back to your AI assistant and ask it to apply your comments."

Write the comment as you would to a colleague. It does not need field IDs or step numbers:

```text
Only send this for orders over $100.
```

```text
This should use the customer's billing email, not the shipping one.
```

After you queue a comment, the step dialog shows a confirmation in place of the comment box.

### 4. Repeat for other steps and automations

Open other steps, on this automation or on others, and queue a comment on each. Several comments on the same step are applied in the order you queued them, so a later comment can refine an earlier one.

### 5. Ask Claude to apply them

In Claude Code, in the project connected to your account:

```text
Apply my comments.
```

Claude collects every pending comment across all your automations in one pass, groups them by automation, applies each one to its step, and saves each automation as a new version. When a comment is ambiguous, Claude applies its best reading and says what it assumed.

### 6. Review the summary

Claude replies with a summary grouped by automation: the step, what it understood each comment to ask for, and what it changed. That summary is the record of the batch, because applied comments leave the queue. Open the diagram again to check the result, and ask Claude to test the changed automations.

## How the comment queue behaves

| Behavior | Detail |
|---|---|
| Scope | Each comment is tied to one step of one automation. |
| Collection | Asking to apply comments takes every pending comment from all your automations at once. |
| Delivery | Each comment is handed over once. After Claude or the assistant collects it, it is no longer pending. |
| Deleted steps | A comment on a step that no longer exists is reported as skipped, with its text, and the rest are applied. |
| Where you can comment | Step dialogs opened from the automation's diagram. Step details opened from Execution History have no comment box. |
| Who applies | Claude in Claude Code, or the assistant in the app. Whichever collects first applies the batch. |

## Troubleshooting

| Symptom | Cause and fix |
|---|---|
| Claude says nothing is pending | The comments were already collected by another Claude session or the assistant, or Claude is signed in as a different account from the one you commented with. Check which account Claude uses; see [Authentication and permissions](/docs/mcp/authentication). |
| There is no **Request a change** box | You opened the step from Execution History. Open it from the automation's diagram instead. |
| A comment was skipped | Its step was removed or replaced after you commented. Queue the comment again on the current step. |
| A change was applied differently than you meant | Tell Claude what you meant. The summary names what it assumed. |
| The confirmation did not appear after **Queue** | The comment was not saved. Reload the diagram and try again; an empty comment is not accepted. |

## Next steps

- [Working with Claude](/docs/mcp/working-with-claude)
- [Drafts and versions](/docs/automations/versions)
- [Testing an automation](/docs/automations/testing)