Connect with your customers on Whatsapp, SMS, Messenger and Instagram using automation.
Connect with your customers on Whatsapp, SMS, Messenger and Instagram using automation. On Nagent, Heyy is exposed as a fully-configurable communication integration that any agent can call — 13 actions, and API key authentication. No code is required to wire Heyy into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Heyy to automate the kinds of tasks communication 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 Heyy 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 Heyy, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HEYY_CREATE_ATTRIBUTETool to create a new custom attribute for contacts in Heyy. Use when you need to add custom fields to track additional information about contacts, such as customer segments, preferences, or custom identifiers.
Input parameters
Name of the attribute to create. This will be displayed in the UI.
External identifier for the attribute. Must start with a letter and contain only letters, numbers, and underscores. This is used for API and integration purposes.
Optional description providing details about the attribute's purpose and usage.
Whether this attribute should be visible in the quick edit panel. Defaults to false if not specified.
Whether this attribute should be visible when creating a new contact. Defaults to false if not specified.
Whether this attribute should be visible in the contacts table view. Defaults to false if not specified.
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
HEYY_CREATE_CONTACTTool to create a new contact in Heyy with optional details including first name, last name, email, phone number, labels, and custom attributes. Use when you need to add a new contact to your Heyy account.
Input parameters
Email address of the contact. Must be a valid email format if provided.
List of labels to assign to the contact
Last name of the contact
First name of the contact
List of custom attributes to attach to the contact
Phone number of the contact
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
HEYY_CREATE_LABELTool to create a new label for categorizing contacts in Heyy. Use when you need to organize contacts into categories or groups.
Input parameters
The name of the label to create. Used for categorizing contacts. Must be a non-empty string.
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
HEYY_CREATE_WEBHOOKTool to create a new webhook for receiving event notifications across multiple channels. Use when you need to set up real-time event notifications for messages.
Input parameters
HTTPS endpoint URL where webhook events will be sent. Must be a valid, publicly accessible URL
Type of event notification to receive. Determines which events trigger webhook calls
Tenant identifier for the webhook. Required to associate the webhook with your tenant
Optional channel identifier to filter webhook events to a specific channel. If not provided, webhook receives events from all channels
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
HEYY_DELETE_ATTRIBUTETool to delete an attribute by its unique identifier. Use when you need to remove an attribute from the system.
Input parameters
Unique identifier of the attribute to delete
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
HEYY_DELETE_LABELTool to delete a label by its unique identifier. Use when you need to remove a label from the system.
Input parameters
Unique identifier of the label to delete
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
HEYY_DELETE_WEBHOOKTool to delete a webhook by its unique identifier. Use when you need to remove a webhook from Heyy.
Input parameters
Unique identifier of the webhook to delete
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
HEYY_LIST_ATTRIBUTESTool to retrieve all attributes available in the Heyy system. Use when you need to get a list of all attributes with their properties and visibility settings.
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
HEYY_LIST_AUTOMATIONSTool to retrieve automation workflows for a specified channel. Use when you need to get all workflows configured for a channel.
Input parameters
The unique identifier of the channel for which to retrieve automation workflows
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
HEYY_LIST_CHANNELSTool to retrieve all available channels from the Heyy system. Use when you need to get a complete list of channels with their details including name, type, status, and timestamps.
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
HEYY_LIST_MESSAGE_TEMPLATESTool to retrieve all message templates available in the Heyy system. Use when you need to view all existing templates for messaging.
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
HEYY_LIST_WEBHOOKSTool to retrieve all API webhooks configured for the account. Use when you need to inspect or manage webhook configurations.
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
HEYY_UPDATE_WEBHOOKTool to update a webhook's URL and active status. Use when you need to modify an existing webhook's endpoint or enable/disable it.
Input parameters
The new webhook URL to receive POST requests. Must be a valid HTTPS endpoint.
Whether the webhook is active. Set to true to enable or false to disable webhook notifications.
The unique identifier of the webhook to update (UUID format)
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 87 agents privately built on Nagent that already use Heyy.
Build on Nagent
Connect Heyy 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 Heyy, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Heyy is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Heyy is connected, you configure its 13 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Heyy 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 Heyy event fires, the agent kicks off automatically.
Every Heyy 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 Heyy ships with 13 pre-built communication actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Heyy together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Heyy-based workflows tailored to your business.