Short answer: Drop the "Mistral AI → Mistral 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 |
|---|---|---|---|
Model model | options | Required | Model. Options: Mistral Large, Mistral Medium, Mistral Small, Codestral, Mistral Nemo |
Message message | string | Required | Message |
System Prompt system | string | Optional | System Prompt. e.g. "You are a helpful assistant." |
Temperature temperature | number | Optional | Temperature |
Max Tokens max_tokens | number | Optional | Max Tokens. e.g. "1024" |
{"model": "{{trigger.model}}","message": "{{trigger.message}}","system": "You are a helpful assistant.","temperature": "{{trigger.temperature}}","max_tokens": "1024"}
{"id": "cmpl-abc123","usage": {"total_tokens": 170,"prompt_tokens": 20,"completion_tokens": 150},"choices": [{"message": {"role": "assistant","content": "Here is the response..."},"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.