Short answer: Drop the "Azure OpenAI → Chat Completion" 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 |
|---|---|---|---|
User Message message | string | Required | User Message (required) |
System Prompt system_prompt | string | Optional | System Prompt |
Temperature temperature | string | Optional | 0.7 |
Max Tokens max_tokens | string | Optional | 1024 |
{"message": "{{trigger.message}}","system_prompt": "{{trigger.system_prompt}}","temperature": "0.7","max_tokens": "1024"}
{"id": "chatcmpl-abc","usage": {"total_tokens": 60,"prompt_tokens": 10,"completion_tokens": 50},"choices": [{"message": {"role": "assistant","content": "Sample"},"finish_reason": "stop"}]}
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.