Integration
Connect Heartbeat to Getemails
When something happens in Heartbeat, your agent does the next thing in Getemails. Describe it 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 Getemails 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 Getemails
When Course Completed in Heartbeat
then Verify email in Getemails
When New Event in Heartbeat
then Find email in Getemails
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 Getemails
Triggers and actions 4 triggers · 9 actions
Trigger
Abandoned Invitation LinkTriggers 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.
Trigger
Course CompletedTriggers when a user completes a course.
Trigger
New EventTriggers when a new event is created.
Trigger
New Event RSVPTriggers when someone RSVPs to an event.
Action
Create EventCreates an event in a Heartbeat community and optionally invites people or groups.
Action
Create GroupCreates a group in a Heartbeat community, optionally nested under another group and seeded with members.
Action
Create ThreadPosts a new thread in a Heartbeat channel.
Action
Deactivate UserRemoves a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place.
Action
List ChannelsReturns all channels in the Heartbeat community, with each channel's name, emoji and type.
Action
List ThreadsReturns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time.
Action
Find emailFinds a prospect's professional email address from their full name and company domain or website.
Action
Get find email statusGet the status/result of a previously submitted Find Email request by its search id, without triggering a new search.
Action
Verify emailVerifies whether an email address is good or bad. Verification is a two-step process: the first call starts it, and calling again after a short wait returns the final result.
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 Getemails
HubSpot to GetemailsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to GetemailsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to GetemailsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to GetemailsGoogle Sheets
Gmail to GetemailsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to GetemailsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Heartbeat and Getemails, 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 Getemails when something happens in Heartbeat?
Any of Getemails's 3 actions, including Find email, Get find email status and Verify email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Getemails to Heartbeat?
Getemails has no triggers in the catalog today, so automations start in Heartbeat. If you need the other direction, ask: your agent reads Getemails's API documentation and adds it.
Do I have to build a connector for Heartbeat or Getemails?
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.