Integration
Connect Heartbeat and Pipefile
When something happens in Heartbeat or Pipefile, your agent does the next thing in the other. 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 Pipefile 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 and Pipefile can do together
From Heartbeat to Pipefile
When Course Completed in Heartbeat
then Add File Request From Template in Pipefile
From Pipefile to Heartbeat
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 Pipefile
Triggers and actions 5 triggers · 16 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.
- File Request Created
Triggers when a file request is created.
- Add File Request From Template
Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
- Create Contact
Add to contacts
- Delete Contact
Delete a contact by id. Returns 204 No Content on success.
- Get Contact
Retrieve one contact by id.
- Get File Request
Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.
- List Contacts
Retrieve a paginated list of contacts, filterable by name/email/phone partial match.
- List File Request Templates
Retrieve the list of file request templates available for creating new file requests, with optional name search.
- Search File Requests
Finds all file requests matching this search query (contact name, email, tags, etc).
- Send Request
Create and send a new request
- Update Contact
Update name/email/phone of an existing contact by id.
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 Pipefile
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Google Sheets to PipefileGoogle Sheets
Gmail to PipefileGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefileGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Heartbeat and Pipefile, 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 Pipefile when something happens in Heartbeat?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to Heartbeat?
Yes. When something happens in Pipefile, your agent can act in Heartbeat too. This page covers both directions: Pipefile's triggers and Heartbeat's actions are listed here as well.
Do I have to build a connector for Heartbeat or Pipefile?
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.