Short answer: Drop the "OpenAI → Create Response" 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 | OpenAI model id |
Input input | string | Required | Plain-text prompt or structured input |
Instructions (system) instructions | string | Optional | Top-level instructions (replaces system role) |
Max Output Tokens max_output_tokens | string | Optional | 1024 |
Temperature temperature | string | Optional | 0.7 |
Store Response store | options | Optional | Whether OpenAI stores the response server-side for later retrieval |
{"model": "{{trigger.model}}","input": "e.g. Summarize the attached document","instructions": "e.g. You are a helpful research assistant","max_output_tokens": "1024","temperature": "0.7"}
{"id": "resp_abc","model": "gpt-5","usage": {"input_tokens": 10,"total_tokens": 60,"output_tokens": 50},"output": [{"role": "assistant","type": "message","content": [{"text": "Sample","type": "output_text"}]}]}
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.