Short answer: Drop the "Google Vertex AI → Embed Text" 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 | Optional | Model. Options: Text Embedding 005, Gemini Embedding 001, Multilingual Embedding 002 |
Text text | string | Required | Text (required) |
Task Type task_type | options | Optional | Task Type. Options: Retrieval Document, Retrieval Query, Semantic Similarity … |
{"model": "{{trigger.model}}","text": "{{trigger.text}}","task_type": "{{trigger.task_type}}"}
{"predictions": [{"embeddings": {"values": [0.012],"statistics": {"token_count": 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.