Integration
Connect Gridfox to Hippo
When Record Created fires in Gridfox, your agent runs Create Summary of Ticket History in Hippo. 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 Hippo 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 Hippo
When Record Created in Gridfox
then Create Summary of Ticket History in Hippo
When Record Created or Updated in Gridfox
then Create Ticket in Hippo
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 Hippo
Triggers and actions 2 triggers · 22 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 custom eventCreate a custom event for a user (Automation/Create custom event in Hippo Postman docs): app_secret_key, user_unique_key, event_type, etc.
Action
Create ConversationCreates a new conversation in the system
Action
Create or Update UserCreate a new user or update an existing one
Action
Create Summary of Ticket HistoryCreates a summary of all notes and comments added in the ticket
Action
Create TicketCreates a new ticket in the system
Action
Get ticketGet ticket details by ticket_id. POST to Hippo ticketing API (Ticketing/Get Ticket Details in the Postman docs) with ticket_id, app_secret_key.
Action
List conversationsFetch a customer's conversation list (Chat/Fetch customer conversation list): email, app_secret_key, start, limit.
Action
List messagesFetch messages and chat details for a channel (Chat/Fetch messages and chat details): channel_id, app_secret_key, start, limit.
Action
Send Broadcast to UsersSends broadcast messages through hippo
Action
Send MessageSends a message in an existing chat
Action
Update Due Date of TicketUpdates due date of an existing ticket
Action
Update Ticket PriorityUpdates the priority of a ticket
Action
Update Ticket StatusUpdate status of a ticket
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 Hippo
Outlign to HippoOutlign is a simple Project Management tool for Creative Teams
HubSpot to HippoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HippoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HippoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HippoGoogle Sheets
Gmail to HippoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Gridfox and Hippo, 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 Hippo when something happens in Gridfox?
Any of Hippo's 13 actions, including Create Conversation, Create or Update User, Create Summary of Ticket History and Create Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hippo to Gridfox?
Hippo has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads Hippo's API documentation and adds it.
Do I have to build a connector for Gridfox or Hippo?
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.