WActionWeaviateUpdated September 2026

How do I run a semantic search in Weaviate?

Short answer: You can search objects in Weaviate by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Weaviate Search Objects 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.

Search Objects in Weaviate — start free All 3 Weaviate actions

Search Objects 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.

Field	Type	Required	Description
Collection collection	string	Required	Document
Query Text query	string	Required	Natural-language query. Vectorized server-side.
Limit limit	number	Optional	–
Properties to Return properties	string	Optional	Space-separated property names. Reduces response size.

Sample request

{
  "collection": "Document",
  "query": "what is photosynthesis",
  "limit": "{{trigger.limit}}",
  "properties": "{{trigger.properties}}"
}

Returns

{
  "data": {
    "Get": {
      "Document": [
        {
          "source": "doc.pdf",
          "content": "...",
          "_additional": {
            "id": "abc-123",
            "distance": 0.21
          }
        }
      ]
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Search Objects.

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

Google Sheets → Weaviate

2 Google Sheets triggers

HubSpot → Weaviate

18 HubSpot triggers

FAQ

Questions about Search Objects.

What does the Search Objects action do in Weaviate?

Runs a semantic GraphQL search: Weaviate vectorizes your query via the collection's configured vectorizer and returns the nearest-neighbor objects. Pass properties to control which fields come back.

What inputs does Search Objects require?

Required: Collection, Query Text. 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 Search Objects support batch operations?

Run Search Objects 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.

Action

Insert Object

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.

Action

List Collections

Lists every collection (class) defined in this Weaviate instance along with its vectorizer and property schema. Use as the first step in any cross-collection automation.

Search Objects in Weaviate — start free