NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
LeadBoxer connects to a Nagent workspace with an API key. Once it is connected, agents can call 9 LeadBoxer actions, such as "Add or Update Lead Tags", "Get Events" and "Get Lead Score Formula". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against LeadBoxer, with input parameters and output schema.
LEADBOXER_ADD_OR_UPDATE_LEAD_TAGSTool to add or update lead tags in LeadBoxer. Use when you need to manage lead tags by adding new tags, removing specific tags, or overwriting all existing tags for a specified user.
Input parameters
Specifies the operation type. 'add' adds a tag without removing existing ones. 'remove' removes a specific tag. If omitted, overwrites all existing tags.
The LeadBoxer user ID of the visitor/lead. Can be obtained from the LeadBoxer cookie via ot_uid() function.
The tag name/value to add, remove, or set for the lead.
Optional dataset ID. If not provided, the site parameter from auth metadata will be used.
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
LEADBOXER_DELETE_CTDTool to delete a custom tracking domain entry for a dataset. Use when you need to remove a specific custom tracking domain (CTD) associated with a dataset in LeadBoxer.
Input parameters
The custom tracking domain value to delete (e.g., 'track.example.com').
User email address for authentication. Required to authorize the delete operation.
The unique identifier for the dataset whose custom tracking domain should be deleted.
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
LEADBOXER_GET_EVENTSTool to fetch events for specified sessions from LeadBoxer. Use when you need to retrieve behavioral data including pageviews, clicks, form submissions, email interactions, and custom events. Events can be filtered by session ID, email, user ID, or segment/smartlist IDs.
Input parameters
Filter events by email address. Use this to retrieve events for a specific email.
Maximum number of events to return. Use this to limit the result set size.
Filter events by user ID. Use this to retrieve all events associated with a specific user.
Filter events by segment ID. Use this to retrieve events for users in a specific segment.
Filter events by specific session ID. Use this to retrieve events for a particular user session.
Filter events by smartlist ID. Use this to retrieve events for users in a specific smartlist.
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
LEADBOXER_GET_LEAD_SCORE_FORMULATool to fetch the lead score formula for a specific dataset. Use when you need to understand how lead scores are calculated for records in a dataset. The formula defines scoring based on criteria types: Range (number ranges), Match (exact values), Exists (presence of values), and Boost (event-based scoring).
Input parameters
Optional email parameter for additional filtering or context.
The unique identifier for the dataset whose lead score formula you want 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
LEADBOXER_GET_SESSIONSTool to fetch sessions for a specified lead ID from LeadBoxer. Use when you need to retrieve session data for a user, with optional filtering by email, user ID, Smartlist ID, or segment ID. A session represents a single visit to the site, and users can have multiple sessions over time.
Input parameters
Optional email address to filter sessions by email.
Maximum number of sessions to return. Use this to limit the result set size.
The LeadBoxer user ID for which to retrieve sessions. This is a required parameter.
Optional user identifier to filter sessions by user ID.
Optional segment ID to filter sessions by segment membership.
Optional Smartlist ID to filter sessions by Smartlist membership.
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
LEADBOXER_LOG_EVENTTool to track server-side events in LeadBoxer. Use when tracking backend events, page views, or custom activities from your server. This endpoint supports tracking user interactions, conversions, and other activities that occur on the server-side.
Input parameters
Override the request IP address. Use this to provide the actual user IP if tracking from a server.
Event location as a full URL. Represents the page or location where the event occurred.
Event title or name that will appear in the clickstream. Describes the action being tracked (e.g., 'User Signup', 'Purchase Complete').
Timezone metadata (e.g., 'America/New_York', 'Europe/London').
Event ID. If not provided, it will be auto-generated by LeadBoxer.
Current referrer URL. The page that referred the user to the current location.
Session ID. If not provided, a new session will be auto-created by LeadBoxer.
User ID to update existing user records. Use this to associate the event with a known user.
User email address for identification purposes.
When set to true, prevents automatic geo-location and user-agent enrichment. Use when tracking events from a proxy or when you want to avoid automatic enrichment.
User locale metadata (e.g., 'en-US', 'fr-FR').
Preferred user identifier. This is the recommended way to identify users.
Browser metadata (e.g., 'Chrome', 'Firefox', 'Safari').
Platform metadata (e.g., 'web', 'mobile', 'ios', 'android').
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
LEADBOXER_MANAGEMENT_CTDTool to fetch custom tracking domain entries for a dataset. Use when you need to retrieve all custom tracking domains that are created or in progress for a specific datasetId.
Input parameters
Required email parameter for authentication.
The unique identifier for the dataset whose custom tracking domains should be retrieved.
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
LEADBOXER_POST_EVENTTool to send event data for tracking user activities via POST request. Use when tracking events by sending data in the request body with application/x-www-form-urlencoded format.
Input parameters
Dataset ID - Mandatory property that tells the engine which site/account the data is being inserted for.
Event title - Reserved property for displaying titles in LeadBoxer's UI. Describes the action being tracked.
Session ID - Identifies the user session. If not provided, a new session will be auto-created.
User ID - Unique identifier for the user to associate the event with a known user.
User name for identification purposes.
Page URL being tracked - The location where the event occurred.
Email address - User's email for identification purposes.
Set to true to prevent automatic detection and overwriting of user values like computer/browser, country/region/city data.
Company name associated with the user.
Referrer URL - The page that referred the user to the current location.
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
LEADBOXER_VIEWS_LEAD_DETAILTool to fetch detailed information about a lead based on filters. Use when you need comprehensive lead data for a specific lead ID. The default view type is B2B. Note: On initial pageview, there may be a few seconds overhead before data is populated; consider implementing a 3-second delay after lead creation.
Input parameters
Email address parameter. Can be empty or contain an email address. By default, email addresses are masked in results.
The LeadBoxer user ID for the lead you want to retrieve details for. Can be obtained using the ot_uid() function.
Set to true to disable email masking in the response.
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
Agents can call 9 LeadBoxer actions on Nagent, including "Add or Update Lead Tags", "Get Events" and "Get Lead Score Formula". Add or Update Lead Tags: Add or update lead tags in LeadBoxer. Each action is listed on this page with its input parameters and its output.
LeadBoxer connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
Add or Update Lead Tags takes 2 required inputs: userId and leadTags. It also takes 2 optional inputs: action and datasetId. It returns data, error and successful.