WActionWeaviateUpdated September 2026

How do I insert an object into a Weaviate collection?

Short answer: You can insert object in Weaviate by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Weaviate Insert Object action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Insert Object in Weaviate — 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
Collection
collection
stringRequiredDocument
Properties
properties
objectRequiredObject data. Keys must match schema.
Vector (optional)
vector
arrayOptionalPrecomputed embedding. Skip to let Weaviate's vectorizer compute it.
UUID (optional)
id
stringOptionalCustom UUID. Weaviate auto-generates if omitted.
Sample request
{
"collection": "Document",
"properties": "{ \"content\": \"...\", \"source\": \"doc.pdf\" }",
"vector": "{{trigger.vector}}",
"id": "{{trigger.id}}"
}
Returns
{
"id": "abc-123-def-456",
"class": "Document",
"properties": {
"content": "..."
}
}

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

Triggered by

Apps that pair well as the trigger for Insert Object.

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

FAQ

Questions about Insert Object.

What does the Insert Object action do in Weaviate?
Inserts a single object into a Weaviate collection. Weaviate auto-embeds the text properties via the collection's configured vectorizer (e.g. text2vec-openai), or you can pass a precomputed vector array.
What inputs does Insert Object require?
Required: Collection, Properties. 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 Weaviate returns an error?
The run history shows the failed step with its input and the error message Weaviate 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 Insert Object support batch operations?
Run Insert Object 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 Weaviate's rate limits.
More actions

Other Weaviate actions.

Insert Object in Weaviate — start free