Integration
Connect Heartbeat to Cloudflare Trace
When something happens in Heartbeat, your agent does the next thing in Cloudflare Trace. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Heartbeat and Cloudflare Trace to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Heartbeat and Cloudflare Trace
Triggers and actions 4 triggers · 8 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
Get geolocation infoLook up the geolocation Cloudflare reports for this automation's own outbound requests — city, region, country, postal code, latitude and longitude — plus the IP address, network operator (ASN) and the Cloudflare data center serving it, from Cloudflare's speed-test metadata endpoint. Takes no input.
Action
Get trace infoFetch the requester's IP address, timestamp, user agent, country code, TLS/HTTP version, and other network metadata from Cloudflare's trace endpoint.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.