INTEGRATION
Vector Database actions
Store and search embeddings: semantic search, similarity lookups, and retrieval-augmented generation
- Actions
- 22
- Services
- 2
- Maintained by
- Flomation
Services
Azure AI Search actions
- Azure AI Search: Count DocumentsCount the documents in an index. The count is eventually consistent: a just-finished upload can take a few seconds to show.
- Azure AI Search: Create or Update IndexCreate an Azure AI Search index from a full index definition (fields, vector search profiles, semantic configuration), or update it in place. Needs an admin API key.
- Azure AI Search: Delete DocumentsDelete documents from an index by key. Deleting a key that does not exist counts as success (the service treats it as already gone). Needs an admin API key.
- Azure AI Search: Delete IndexDelete an Azure AI Search index and every document in it. This cannot be undone. Needs an admin API key.
- Azure AI Search: Get DocumentLook up a single document in an index by its key. Optionally select specific fields to return.
- Azure AI Search: Get IndexFetch an Azure AI Search index definition: fields, vector search profiles, scoring profiles, and semantic configuration.
pgvector actions
- Count DocumentsCount the documents in the store, with an optional metadata filter
- Create Search IndexAdd an approximate-nearest-neighbour index so similarity search stays fast as the table grows
- Create Vector TableCreate a table that stores documents and their embeddings, with the index that makes search fast
- Delete DocumentsRemove documents by ID or by a metadata filter
- Get DocumentFetch a single document by its ID
- Hybrid SearchCombine meaning-based and keyword search, so exact terms and product codes are not missed
Wire Vector Database into the rest of your stack
Every action here drops onto the canvas alongside the other 3,585, so a Vector Database step can sit between a form, a database and a message without any glue code.
