Engage turns your customers into fans with personalised messaging; using emails, push and in-app notifications, and SMS.
Engage turns your customers into fans with personalised messaging; using emails, push and in-app notifications, and SMS. On Nagent, Engage is exposed as a fully-configurable marketing automation integration that any agent can call — 22 actions, and BASIC authentication. No code is required to wire Engage into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Engage to automate the kinds of tasks marketing automation 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 Engage 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 Engage, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ENGAGE_ADD_CUSTOMER_TO_ACCOUNTSTool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.
Input parameters
User ID of the customer to add to accounts
Array of accounts to add the customer to, each with account ID and optional role
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
ENGAGE_ADD_USER_TO_LISTSTool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.
Input parameters
User ID of the Customer or Account to add to lists
Array of list IDs to add the user to. Each ID should be a valid list identifier.
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
ENGAGE_ARCHIVE_LISTTool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.
Input parameters
The List ID to archive
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
ENGAGE_ARCHIVE_USERTool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events for the user will be stopped, but all messages, logs, and related data will be preserved.
Input parameters
User ID of the Customer or Account to archive.
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
ENGAGE_CONVERT_USER_TYPETool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.
Input parameters
User ID of the Customer or Account to convert.
The entity type to convert to: customer or account.
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
ENGAGE_CREATE_LISTTool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.
Input parameters
List title (required)
String attached to the object - a description or summary of the list
If true, subscribers receive a confirmation mail before being added to the list
URL to redirect users to after subscription
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
ENGAGE_CREATE_USERTool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.
Input parameters
Unique identifier for the user in your application. This will be returned as 'uid' in the response.
Object containing additional custom user attributes (string, number, or boolean values)
User's email address for communication
Array of List IDs to automatically subscribe the user to
User's phone number in international format (e.g., +1234567890)
Array of account assignments with ID and optional role
User's last name
Date the user signed up. Should be a valid ISO 8601 date string
User's first name
If true, creates the user as an Account entity instead of a regular Customer
Device token for push notifications
Device platform for push notifications. Must be 'android' or 'ios'
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
ENGAGE_DELETE_SUBSCRIBER_FROM_LISTTool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.
Input parameters
The List ID from which to remove the subscriber
The subscriber's unique user ID to remove from the list
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
ENGAGE_DELETE_USERTool to completely delete all user data for a Customer or Account. This is a permanent, destructive action that removes all associated user data from Engage.
Input parameters
User ID of the Customer or Account to delete. This is the ID you supplied when creating the user, not Engage's internal 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
ENGAGE_GET_ACCOUNT_MEMBERSTool to retrieve all members (Customers) of an Account in Engage. Use when you need to list users who are part of a specific account.
Input parameters
User ID of the Account whose members 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
ENGAGE_GET_LISTTool to retrieve a single List by its ID. Use when you need to fetch details about a specific List.
Input parameters
The unique identifier of the List 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
ENGAGE_GET_USERTool to retrieve a single user by their user ID. Use when you need to fetch complete user information including metadata, attributes, devices, lists, segments, and message statistics.
Input parameters
User ID of the Customer or Account (the ID you supplied when creating the user)
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
ENGAGE_LIST_LISTSTool to retrieve a paginated list of all Lists in Engage. Use when you need to view available Lists or iterate through all Lists in the account.
Input parameters
Number of Lists to return. Defaults to 10. Maximum of 30.
Pagination cursor for next dataset page
Pagination cursor for previous dataset 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
ENGAGE_LIST_USERSTool to retrieve a paginated list of all users in Engage. Use when you need to list users with optional filtering by email and cursor-based pagination support.
Input parameters
Filter results to return only users with this specific email address.
Number of users to return. Defaults to 10. Maximum of 30.
Pagination cursor for retrieving the next page of results.
Pagination cursor for retrieving the previous 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
ENGAGE_MERGE_USERSTool to merge two user profiles in Engage. The source user is merged into the destination user, and the source user profile is removed. Use when you need to consolidate duplicate user accounts or combine user data from multiple profiles into a single account.
Input parameters
The ID of the user to merge. This user will be merged into the destination user and the source user profile will be removed.
The ID of the user that the source user is being merged into. This user will contain all merged data.
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
ENGAGE_REMOVE_CUSTOMER_FROM_ACCOUNTTool to remove a Customer from an Account in Engage. Use when you need to disassociate a customer from a specific account.
Input parameters
User ID of the Account to remove the Customer from. Example: 'test_account_1739394000'
User ID of the Customer to remove from the Account. Example: 'test_customer_1739394000'
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
ENGAGE_SEND_BATCH_REQUESTTool to batch multiple create user, update user, and add user events operations into a single API call. Use when you need to perform multiple operations efficiently at the cost of one API request. The batch is queued for processing without immediate validation, so ensure all parameters are correct. Request size must remain under 100KB.
Input parameters
Array of batch operations. Each item must have 'type' and 'id', plus operation-specific parameters. Total request size must be under 100KB.
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
ENGAGE_SUBSCRIBE_USER_TO_LISTTool to create a user and subscribe them to an Engage.so List. Use when you need to add users to a specific list for email marketing or user segmentation. If the user already exists, they will be added to the List without creating a duplicate.
Input parameters
The List ID to subscribe the user to.
Additional user attributes as key-value pairs. Values must be string, number, or boolean.
The user's email address (required). Requires full authentication.
The user's phone number in international format (e.g., +1234567890).
The user's last name.
Creation date if the user already exists (ISO 8601 format recommended).
The user's first name.
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
ENGAGE_TRACK_USER_EVENTTool to add user events to Engage. Use this to track user actions and events in your application. You can later segment users based on these actions or events.
Input parameters
User ID of the Customer or Account
The event title
The event value. Can be string, number, or boolean
Timestamp of the event. Defaults to current time.
Object containing additional event properties (string, number, or boolean values)
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
ENGAGE_UPDATE_ACCOUNT_ROLETool to update the role of a Customer in an Account or set a new one if none exists. Use when you need to assign or change a customer's role within a specific account.
Input parameters
User ID of the Account in which to update the Customer's role.
User ID of the Customer whose role to update.
The new role to assign to the Customer in the Account.
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
ENGAGE_UPDATE_SUBSCRIBER_STATUSTool to update a subscriber's status on a List. Use when you need to subscribe, re-subscribe, or unsubscribe a user from a specific List.
Input parameters
The List ID to update the subscriber status for
The subscriber's user ID
Set to true to subscribe or re-subscribe the user, false to unsubscribe
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
ENGAGE_UPDATE_USERTool to update user data and attributes on Engage. Use this to update user data changes like changes in plan, name, location, etc. If the user doesn't exist, this method creates the user.
Input parameters
User ID of the Customer or Account to update. This is the unique identifier for the user in your system.
Object containing additional user attributes to add or update. Use this for custom properties like plan, location, preferences, etc.
User's email address. Updating email requires full authentication.
User's phone number in international format (e.g., +1234567890).
User's last name.
Date the user signed up. Should be a valid date string in ISO format.
User's first name.
If true, converts user to account. If false and entity is account, converts to user.
User's device token for push notifications.
Device platform: android or ios.
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 51 agents privately built on Nagent that already use Engage.
Build on Nagent
Connect Engage 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 Engage, and click "Connect Now." You'll authenticate with BASIC — Nagent handles credential storage and refresh automatically. Once connected, Engage is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Engage is connected, you configure its 22 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Engage 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 Engage event fires, the agent kicks off automatically.
Every Engage 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 Engage ships with 22 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Engage together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Engage-based workflows tailored to your business.