Integration
Connect FieldAware and Heartbeat
When New job completed fires in FieldAware, your agent runs Create Event in Heartbeat, or Course Completed in Heartbeat to Add invoice in FieldAware. 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 FieldAware and Heartbeat to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 FieldAware and Heartbeat can do together
From FieldAware to Heartbeat
When New job completed in FieldAware
then Create Event in Heartbeat
When New job completed in FieldAware
then Deactivate User in Heartbeat
From Heartbeat to FieldAware
When Course Completed in Heartbeat
then Add invoice in FieldAware
When New Event in Heartbeat
then Create contact in FieldAware
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 FieldAware and Heartbeat
Triggers and actions 5 triggers · 41 actions
Trigger
New job completedPolls for jobs that have reached the Completed state. Dedupe on each job's uuid.
Action
Add invoiceCreates an invoice for one or more completed jobs for a customer, with its line items and totals.
Action
Create assetCreate an asset. name and a location UUID are required.
Action
Create contactCreate a contact.
Action
Create customerCreate a customer. name and a location object are required.
Action
Create jobCreate a new job. scheduledOn is required; location is a UUID reference.
Action
Create locationCreate a location. Provide either name+lat+lng or street+locality.
Action
Delete assetDelete an asset by UUID.
Action
Delete contactDelete a contact by UUID.
Action
Delete customerDelete a customer by UUID.
Action
Delete jobDeletes a job from FieldAware.
Action
Delete locationDelete a location by UUID.
Action
Get assetRetrieve a single asset by UUID.
Action
Get contactRetrieve a single contact by UUID.
Action
Get customerRetrieve a single customer by UUID.
Action
Get invoiceRetrieve a single invoice by UUID or invoice number.
Action
Get itemReturns one item (product) by its ID, including its pricing, tax settings and custom fields.
Action
Get jobRetrieve a single job by its UUID.
Action
Get locationRetrieve a single location by UUID.
Action
Get taskRetrieve a single task by UUID.
Action
Get userRetrieve a single user by UUID.
Action
List assetsList all assets.
Action
List contactsList all contacts.
Action
List customersList all customers.
Action
List invoicesList invoices, optionally filtered by createdOn date range.
Action
List itemsList all items (products/services in the catalog).
Action
List jobsList jobs in a date range, optionally filtered by state.
Action
List locationsList all locations.
Action
List tasksList all tasks.
Action
List usersList all users.
Action
Update assetUpdate an asset.
Action
Update contactUpdate a contact.
Action
Update customerUpdate a customer. Fields other than location are optional.
Action
Update invoiceUpdates an existing FieldAware invoice's comments, customer, contact, invoiced jobs, totals or custom fields.
Action
Update itemUpdates an existing item (product) in FieldAware, such as its name, pricing, part number or tax settings.
Action
Update locationUpdate a location.
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.
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 FieldAware
FieldAware to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FieldAware to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FieldAware to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FieldAware to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FieldAware to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FieldAware to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Heartbeat
ConvesioConvert to HeartbeatConvesioConvert is a cross-channel marketing automation tool to nurture your customer journey.
Google Sheets to HeartbeatGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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
FieldAware and Heartbeat, answered
What can start an automation from FieldAware?
Any of FieldAware's 1 trigger in the catalog, including New job completed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Heartbeat when something happens in FieldAware?
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 FieldAware?
Yes. When something happens in Heartbeat, your agent can act in FieldAware too. This page covers both directions: Heartbeat's triggers and FieldAware's actions are listed here as well.
Do I have to build a connector for FieldAware 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.
Can my AI client use FieldAware and Heartbeat without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.