Integration
Connect Gridfox to Clickhouse
When Record Created fires in Gridfox, your agent runs Add API key in Clickhouse. 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 Clickhouse to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Clickhouse
When Record Created in Gridfox
then Add API key in Clickhouse
When Record Created or Updated in Gridfox
then Update API key in Clickhouse
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 Clickhouse
Triggers and actions 2 triggers · 29 actions
Trigger
Record CreatedTriggers when a new record is created.
Trigger
Record Created or UpdatedFires when a record in the chosen Gridfox table is created or updated.
Action
Add recordCreate a record in a table.
Action
Add userAdd a user to the project.
Action
Delete recordDelete a record.
Action
Find recordsSearch records in a table by search parameters.
Action
Get recordGet a record by reference field value.
Action
Get record auditGet audit history for a record.
Action
List tablesList tables in the project.
Action
List User Groupslists the project's user groups with their member users (id, email).
Action
Update recordUpdate a record by reference field value.
Action
Add API keyCreate a new organization API key.
Action
Delete API keyDelete an organization API key.
Action
Delete invitationDelete an organization invitation.
Action
Delete query API endpointDelete a Query API endpoint.
Action
Get API keyGet key details.
Action
Get organizationGet organization details.
Action
Get serviceGet service details.
Action
Get usage costGet organization usage costs.
Action
List activitiesList of organization activities (audit log).
Action
List API keysGet list of all organization API keys.
Action
List backupsList of service backups.
Action
List invitationsList all organization invitations.
Action
List membersList organization members.
Action
List organizationsGet list of available organizations.
Action
List query API endpointsList Query API endpoints for a service.
Action
List servicesList of organization services.
Action
Update API keyUpdate key details.
Action
Update organizationUpdate organization details.
Action
Update serviceUpdate service basic details.
Action
Update service stateStart/stop a service by updating its state.
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 HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Gridfox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gridfox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gridfox to MailchimpMailchimp marketing automation and email platform.
Gridfox to StripeStripe is a payment processing platform for online businesses.
Gridfox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Clickhouse
Grist to ClickhouseGrist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...
HubSpot to ClickhouseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ClickhouseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ClickhouseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ClickhouseGoogle Sheets
Gmail to ClickhouseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Gridfox and Clickhouse, 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 Clickhouse when something happens in Gridfox?
Any of Clickhouse's 20 actions, including Update API key, Update organization, Update service and Update service state. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clickhouse to Gridfox?
Clickhouse has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads Clickhouse's API documentation and adds it.
Do I have to build a connector for Gridfox or Clickhouse?
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.
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.