Short answer: Drop the "Anthropic → Computer Use" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Model model | options | Required | Model. Options: Claude Opus 4.7 (best for agents), Claude Sonnet 4.6 |
Task message | string | Required | Open the calculator and compute 17 × 23 |
Display Width display_width_px | string | Optional | Display Width |
Display Height display_height_px | string | Optional | Display Height |
Max Tokens max_tokens | string | Optional | Max Tokens |
{"model": "{{trigger.model}}","message": "Open the calculator and compute 17 × 23","display_width_px": "{{trigger.display_width_px}}","display_height_px": "{{trigger.display_height_px}}","max_tokens": "{{trigger.max_tokens}}"}
{"id": "msg_abc","content": [{"name": "computer","type": "tool_use","input": {"action": "screenshot"}}],"stop_reason": "tool_use"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.