Integration
Connect Gridfox to Azure AI Search Vector Store
When Record Created fires in Gridfox, your agent runs Upload Documents in Azure AI Search Vector Store. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Gridfox and Azure AI Search Vector Store to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Gridfox can start in Azure AI Search Vector Store
When Record Created in Gridfox
then Upload Documents in Azure AI Search Vector Store
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Gridfox and Azure AI Search Vector Store
Triggers and actions 2 triggers · 16 actions
- Record Created
Triggers when a new record is created.
- Record Created or Updated
Fires when a record in the chosen Gridfox table is created or updated.
- Add record
Create a record in a table.
- Add user
Add a user to the project.
- Delete record
Delete a record.
- Find records
Search records in a table by search parameters.
- Get record
Get a record by reference field value.
- Get record audit
Get audit history for a record.
- List tables
List tables in the project.
- List User Groups
lists the project's user groups with their member users (id, email).
- Update record
Update a record by reference field value.
- Create Index
Creates a search index with the fields you define, including vector fields for similarity search.
- Delete Index
Deletes a search index and every document in it.
- Get Document
Returns one document from a search index by its key.
- Get Index
Returns a search index's definition: its fields, vector search and semantic settings.
- List Indexes
Returns the search indexes in your Azure AI Search service.
- Search Documents
Searches a search index by keywords, filter and/or vector similarity and returns the matching documents with their scores.
- Upload Documents
Adds documents to a search index, replacing any existing document with the same key.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Gridfox
Gridfox to ChecklySynthetic monitoring platform for uptime, API, and browser checks with alerting and status pages.
Gridfox to Jungle GridGPU orchestration platform that runs AI inference/training jobs by intent without managing GPU providers.
Gridfox to Less Annoying CRMLess Annoying CRM is a small business CRM with easy-to-use features at an affordable price.
Gridfox to LuchtmeetnetLuchtmeetnet is the Dutch national air quality portal operated by RIVM.
Gridfox to MemsourceTranslation management system for automating localization workflows, machine translation, and multilingual...
Gridfox to Octopus DeployContinuous deployment platform that automates and orchestrates software releases across servers, Kubernetes...
More into Azure AI Search Vector Store
HubSpot to Azure AI Search Vector StoreHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Azure AI Search Vector StoreSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Azure AI Search Vector StoreSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Azure AI Search Vector StoreGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Azure AI Search Vector StoreGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Azure AI Search Vector StoreGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Gridfox and Azure AI Search Vector Store, answered
What can start an automation from Gridfox?
Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Azure AI Search Vector Store when something happens in Gridfox?
Any of Azure AI Search Vector Store's 7 actions, including Create Index, Upload Documents, Get Document and Get Index. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Azure AI Search Vector Store to Gridfox?
Azure AI Search Vector Store has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads Azure AI Search Vector Store's API documentation and adds it.
Do I have to build a connector for Gridfox or Azure AI Search Vector Store?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Gridfox and Azure AI Search Vector Store without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.