Integration
Connect Gridfox and Heartbeat
When Record Created fires in Gridfox, your agent runs Create Event in Heartbeat, or Course Completed in Heartbeat to Add record in Gridfox. 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 Heartbeat 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 and Heartbeat can do together
From Gridfox to Heartbeat
When Record Created in Gridfox
then Create Event in Heartbeat
From Heartbeat to Gridfox
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 Heartbeat
Triggers and actions 6 triggers · 15 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.
- Abandoned Invitation Link
Triggers when someone enters their information in an invitation link, but does not make a purchase or create their account. This will trigger after 4 hours, if the user still has not made a purchase or created their account.
- Course Completed
Triggers when a user completes a course.
- New Event
Triggers when a new event is created.
- New Event RSVP
Triggers when someone RSVPs to an event.
- Create Event
Creates an event in a Heartbeat community and optionally invites people or groups.
- Create Group
Creates a group in a Heartbeat community, optionally nested under another group and seeded with members.
- Create Thread
Posts a new thread in a Heartbeat channel.
- Deactivate User
Removes a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place.
- List Channels
Returns all channels in the Heartbeat community, with each channel's name, emoji and type.
- List Threads
Returns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time.
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 Heartbeat
ConvesioConvert to HeartbeatConvesioConvert is a cross-channel marketing automation tool to nurture your customer journey.
Google Sheets to HeartbeatGoogle Sheets
Gmail to HeartbeatGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HeartbeatGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to HeartbeatGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HeartbeatActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Gridfox and Heartbeat, 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 Heartbeat when something happens in Gridfox?
Any of Heartbeat's 6 actions, including Create Event, Create Group, Create Thread and Deactivate User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Heartbeat to Gridfox?
Yes. When something happens in Heartbeat, your agent can act in Gridfox too. This page covers both directions: Heartbeat's triggers and Gridfox's actions are listed here as well.
Do I have to build a connector for Gridfox or Heartbeat?
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.