Integration
Connect Heartbeat to Elastic Cloud
When Course Completed fires in Heartbeat, your agent runs Add Elasticsearch project in Elastic Cloud. 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 Heartbeat and Elastic Cloud 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 Heartbeat can start in Elastic Cloud
When Course Completed in Heartbeat
then Add Elasticsearch project in Elastic Cloud
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 Heartbeat and Elastic Cloud
Triggers and actions 4 triggers · 15 actions
- 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.
- Add API key
Creates a new Elastic Cloud API key and returns it, including the secret key value, which is shown only once.
- Add Elasticsearch project
Creates an Elastic Cloud Serverless Elasticsearch project and returns its id, endpoints and access credentials.
- Delete API key
Deletes (invalidates) an Elastic Cloud API key.
- Delete Elasticsearch project
Schedules deletion of an Elastic Cloud Serverless Elasticsearch project.
- Get deployment
Returns a deployment's details, including its name, alias, health and Elasticsearch, Kibana and other resources.
- Get Elasticsearch project
Returns the details of one Elasticsearch serverless project, including its name, region, endpoints, cloud ID and tags.
- List API keys
Returns the metadata for the Elastic Cloud API keys your account is allowed to see.
- List Elasticsearch projects
Returns the Elasticsearch Serverless projects in your Elastic Cloud organization, optionally filtered by traffic filter or linked project.
- List regions
Returns the cloud provider regions where Elastic Cloud Serverless projects can be created.
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 Heartbeat
Heartbeat to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Heartbeat to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Heartbeat to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Heartbeat to MailchimpMailchimp marketing automation and email platform.
Heartbeat to StripeStripe is a payment processing platform for online businesses.
Heartbeat to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Elastic Cloud
Google Sheets to Elastic CloudGoogle Sheets
Gmail to Elastic CloudGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Elastic CloudGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Heartbeat and Elastic Cloud, answered
What can start an automation from Heartbeat?
Any of Heartbeat's 4 triggers in the catalog, including Course Completed, New Event, New Event RSVP and Abandoned Invitation Link. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Elastic Cloud when something happens in Heartbeat?
Any of Elastic Cloud's 9 actions, including Add API key, Add Elasticsearch project, Get deployment and Get Elasticsearch project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Elastic Cloud to Heartbeat?
Elastic Cloud has no triggers in the catalog today, so automations start in Heartbeat. If you need the other direction, ask: your agent reads Elastic Cloud's API documentation and adds it.
Do I have to build a connector for Heartbeat or Elastic Cloud?
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.