WActionWeaviateUpdated May 2026

How do I run a semantic search in Weaviate?

Short answer: Drop the "Weaviate → Search Objects" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Weaviate actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Search Objects support batch operations?

Yes. Run Search Objects inside a Loop node to process arrays. Tiny Command handles Weaviate's rate limits automatically so you don't have to throttle manually.

More actions