ActionCohereUpdated September 2026

How do I create text embeddings with Cohere?

Short answer: You can create embeddings in Cohere by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cohere Create Embeddings action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Embeddings in Cohere — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Texts (JSON array)
texts
arrayRequiredArray of strings to embed
Model
model
optionsOptionalModel. Options: English v3, Multilingual v3, English Light v3
Input Type
input_type
optionsRequiredInput Type. Options: Search Document (for indexing), Search Query (for querying), Classification, Clustering
Sample request
{
"texts": "{{trigger.texts}}",
"model": "{{trigger.model}}",
"input_type": "{{trigger.input_type}}"
}
Returns
{
"id": "abc",
"meta": {
"api_version": {
"version": "1"
}
},
"embeddings": [
[
0.1,
0.2,
0.3
]
]
}

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

Triggered by

Apps that pair well as the trigger for Create Embeddings.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Embeddings.

What does the Create Embeddings action do in Cohere?
Generates vector embeddings for text using Cohere's embed-v3 model. Supports input_type (search_document, search_query, classification, clustering), which materially improves retrieval quality, so set it correctly.
What inputs does Create Embeddings require?
Required: Texts (JSON array), Input Type. 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 run history shows the failed step with its input and the error message Cohere returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Embeddings support batch operations?
Run Create Embeddings inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Cohere's rate limits.
More actions

Other Cohere actions.

Create Embeddings in Cohere — start free