Plug-and-play online communities. Heartbeat provides tools for creating and managing online communities with features for users, channels, events, messages, and more.
Plug-and-play online communities. Heartbeat provides tools for creating and managing online communities with features for users, channels, events, messages, and more. On Nagent, Heartbeat is exposed as a fully-configurable team collaboration integration that any agent can call — 7 actions, and API key authentication. No code is required to wire Heartbeat into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Heartbeat to automate the kinds of tasks team collaboration teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Heartbeat into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Heartbeat, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HEARTBEAT_GET_EVENTSTool to retrieve event information from the community. Use when you need to list events with optional pagination support.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_LIST_CHANNELSTool to retrieve a paginated list of channels in the community. Use when you need to list, browse, or search for channels in the Heartbeat community. Supports filtering by archived status, channel type, and pagination.
Input parameters
Number of results per page. Must be between 1 and 100. If not specified, uses the API's default pagination size.
Filter by archived status. Use 'all' for all channels, 'active' for active channels only, 'archived' for archived channels only. If not specified, defaults to active channels.
Filter by channel type. Use 'thread' for thread channels, 'chat' for chat channels, 'voice' for voice channels. If not specified, returns all types.
Cursor token for pagination to fetch the next page of results. Use the cursor from the previous response to get the next page. Omit for the first page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_LIST_GROUPSTool to retrieve a paginated list of access groups in the community. Use when you need to browse groups with optional filters for parent groups or user membership. Supports cursor-based pagination.
Input parameters
Number of results to return (1-100). Used for pagination.
Filter groups that a user is a member of. Returns only groups where the specified user is a member.
Filter by parent group. Returns only groups that are children of the specified parent group ID.
Cursor for pagination - returns results after this ID. Used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_LIST_USERSTool to retrieve a paginated list of users in the Heartbeat community. Use when you need to get user information with optional filtering by creation date, group membership, or role.
Input parameters
Filter by user role ID
Number of results to return per page (1-100)
Filter by group membership - returns only users in the specified group
Filter users created after this date (ISO 8601 format)
Filter users created before this date (ISO 8601 format)
Cursor for pagination - return results after this user ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_REACTIVATE_USERTool to reactivate a previously deleted user by email to allow them to access the community again. Use when you need to restore access for a user who was previously removed.
Input parameters
Email address of the user to reactivate. The user must have been previously deleted from the community.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_RETRIEVE_GROUPTool to retrieve a single group by its ID. Use when you need to get detailed information about a specific group in the Heartbeat community.
Input parameters
The unique identifier for the group to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HEARTBEAT_RETRIEVE_USERTool to retrieve a single user by their ID. Use when you need to get detailed information about a specific user in the Heartbeat community.
Input parameters
The unique identifier for the user to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 84 agents privately built on Nagent that already use Heartbeat.
Build on Nagent
Connect Heartbeat to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Heartbeat, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Heartbeat is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Heartbeat is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Heartbeat steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Heartbeat event fires, the agent kicks off automatically.
Every Heartbeat action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Heartbeat ships with 7 pre-built team collaboration actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Heartbeat together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Heartbeat-based workflows tailored to your business.