Short answer: Drop the "Voyage AI → Create Embeddings" 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: Voyage 3 Large (best quality), Voyage 3.5, Voyage 3.5 Lite (cheap) … |
Text text | string | Required | Text (required) |
Input Type input_type | options | Optional | Input Type. Options: Document, Query |
{"model": "{{trigger.model}}","text": "{{trigger.text}}","input_type": "{{trigger.input_type}}"}
{"data": [{"index": 0,"embedding": [0.012,-0.045]}],"model": "voyage-3-large","usage": {"total_tokens": 5}}
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.