Chat: Cohere action · Tiny Command

Inputs

The fields this action accepts.

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: Command R+, Command R, Command, Command Light
Message message	string	Required	Message. Example: Summarize this quarterly report...
System Preamble preamble	string	Optional	Instructions for the model
Temperature temperature	string	Optional	Temperature. Example: 0.3

Sample request

{
  "model": "{{trigger.model}}",
  "message": "e.g. Summarize this quarterly report...",
  "preamble": "{{trigger.preamble}}",
  "temperature": "e.g. 0.3"
}

Returns

{
  "id": "abc123",
  "usage": {
    "input_tokens": 50,
    "output_tokens": 200
  },
  "message": {
    "role": "assistant",
    "content": "Based on the report..."
  },
  "finish_reason": "COMPLETE"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Chat.

What does the Chat action do in Cohere?

Sends a message and gets a response from one of Cohere's Command models. Cohere is known for enterprise-grade chat with strong RAG and grounded-answer features.

What inputs does Chat require?

Required: Model, Message. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Cohere returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Chat support batch operations?

Yes. Run Chat inside a Loop node to process arrays. Tiny Command handles Cohere's rate limits automatically so you don't have to throttle manually.

More actions