Twilio Segment is a customer data platform that helps businesses collect, clean, and control their customer data.
Twilio Segment is a customer data platform that helps businesses collect, clean, and control their customer data. On Nagent, Segment is exposed as a fully-configurable analytics integration that any agent can call — 17 actions, and API key authentication. No code is required to wire Segment into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Segment to automate the kinds of tasks analytics 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 Segment 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 Segment, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SEGMENT_ADD_LABELS_TO_SOURCETool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
Input parameters
List of labels to associate with the Source. Must include at least one label.
ID of the Source (1-255 characters)
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
SEGMENT_ALIASTool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities.
Input parameters
New known unique identifier for the user.
Additional context (e.g., ip, locale).
ISO-8601 timestamp for the event; server time used if omitted.
Previous unique identifier for the user.
Anonymous identifier for the user.
Per-destination enable/disable controls.
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
SEGMENT_BATCHTool to send multiple analytics calls in a single batch request. Use when you want to reduce HTTP overhead by batching Identify/Track/Page/Screen/Group calls into one request.
Input parameters
Array of analytics calls (identify, track, page, screen, or group). Each item must include 'type' and required fields per call type.
Optional top-level context merged into each call's context.
Segment write key; required when using Bearer authentication.
Optional top-level integrations merged into each call's integrations.
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
SEGMENT_DELETE_SOURCETool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation.
Input parameters
The Source ID. Length 1–255 characters.
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
SEGMENT_GET_DAILY_PER_SOURCE_API_CALLS_USAGETool to fetch daily API call counts per source for a given period. Use when you need daily breakdown of API usage by source after determining the reporting period.
Input parameters
Start of the usage period in ISO-8601 format (YYYY-MM-DD), e.g. '2021-02-01'.
Pagination parameters for querying source daily API calls usage.
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
SEGMENT_GET_DESTINATIONTool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint; returns minimal envelope on legacy HTML or parse errors.
Input parameters
The destination’s unique 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
SEGMENT_GROUPTool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits.
Input parameters
Free-form dictionary of group traits (e.g., name, industry, employees).
Unique user identifier. Exactly one of 'userId' or 'anonymousId' must be provided.
Additional contextual information (e.g., ip, locale, device).
Unique identifier for the group.
Write key for authentication if not using OAuth Bearer token.
ISO-8601 timestamp when the event occurred; if omitted, server time is used.
Pseudo-unique ID for anonymous users. Exactly one of 'userId' or 'anonymousId' must be provided.
Per-destination enable/disable controls (case-sensitive keys).
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
SEGMENT_IDENTIFYTool to identify a user and set/update traits via Segment HTTP Tracking API.
Input parameters
Free-form dictionary of user traits (e.g., email, name, plan).
Unique user identifier. Exactly one of 'userId' or 'anonymousId' must be provided.
Additional contextual information (e.g., ip, locale, device).
Write key for authentication if not using Basic or OAuth headers.
Unique id for deduplication; Segment auto-generates one if omitted.
ISO-8601 timestamp when the identification occurred; if omitted, server time is used.
Pseudo-unique ID for anonymous users. Exactly one of 'userId' or 'anonymousId' must be provided.
Per-destination enable/disable controls (case-sensitive keys).
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
SEGMENT_IMPORT_HISTORICAL_DATATool to import historical data in bulk with support for historical timestamps. Use when you need to backfill or import past events with their original timestamps into Segment.
Input parameters
Array of event objects to import. Each event should contain: type (track/identify/page/screen/group), userId or anonymousId, timestamp (ISO 8601 format for historical data), and event-specific properties.
Optional top-level context merged into each call's context.
Optional top-level integrations merged into each call's integrations.
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
SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCETool to list warehouses connected to a Source. Use when you need to retrieve warehouses for a given source ID.
Input parameters
ID of the Source to retrieve warehouses for.
Pagination parameters for the request.
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
SEGMENT_LIST_DELIVERY_METRICS_SUMMARY_FROM_DESTINATIONGet an event delivery metrics summary from a Destination. Primary attempt uses Segment Public API; fallback to legacy app host if needed. On HTML fallback responses, returns a minimal valid envelope to maintain contract.
Input parameters
Filter events that happened before this time (ISO-8601). Defaults to now.
Source id linked to the destination
Filter events that happened after this time (ISO-8601). Defaults depend on granularity.
Granularity of the metrics aggregation
Destination 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
SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCERetrieve schema configuration settings for a Source.
Input parameters
ID of the Source
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
SEGMENT_PAGETool to record a page view via Segment HTTP Tracking API. Use when sending page views with optional page name and properties.
Input parameters
Name of the page. Optional.
Unique user identifier. Exactly one of 'userId' or 'anonymousId' must be provided.
Additional contextual information (e.g., ip, locale, device).
Write key for authentication if not using Basic or Bearer auth in headers.
Unique id for deduplication; Segment auto-generates one if omitted.
ISO-8601 timestamp when the event occurred; if omitted, server time is used.
Free-form dictionary of page properties (e.g., path, url).
Pseudo-unique ID for anonymous users. Exactly one of 'userId' or 'anonymousId' must be provided.
Per-destination enable/disable controls (case-sensitive keys).
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
SEGMENT_REMOVE_SOURCE_WRITE_KEYTool to remove a write key from a Source. Use when you need to revoke an existing write key for security or rotation.
Input parameters
The unique identifier of the Source.
The write key to remove from the Source.
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
SEGMENT_SCREENTool to record a mobile app screen view. Use when tracking screen views in a mobile app via Segment HTTP Tracking API.
Input parameters
Name of the screen.
Unique user identifier. Exactly one of 'userId' or 'anonymousId' must be provided.
Additional contextual information (e.g., ip, locale, device).
Write key for authentication if not using Basic or OAuth headers.
ISO-8601 timestamp when the screen event occurred; if omitted, server time is used.
Free-form dictionary of screen properties.
Pseudo-unique ID for anonymous users. Exactly one of 'userId' or 'anonymousId' must be provided.
Per-destination enable/disable controls (case-sensitive keys).
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
SEGMENT_TRACKTool to record a custom user event via Segment HTTP Tracking API. Use when sending events to Segment with valid identity.
Input parameters
Name of the action performed (e.g., 'Item Purchased').
Unique user identifier. Exactly one of 'userId' or 'anonymousId' must be provided.
Additional contextual information (e.g., ip, locale, device).
Write key for authentication if not using Basic or OAuth headers.
ISO-8601 timestamp when the event occurred; if omitted, server time is used.
Free-form dictionary of event-specific properties (e.g., revenue).
Pseudo-unique ID for anonymous users. Exactly one of 'userId' or 'anonymousId' must be provided.
Per-destination enable/disable controls (case-sensitive keys).
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
SEGMENT_UPDATE_SOURCETool to update a Source's metadata and settings. Use when you need to modify an existing Source after confirming its ID.
Input parameters
Human-readable name for the Source (displayName).
Slug that identifies the Source (config name).
Whether the Source can send data.
Key-value settings specific to the Source type; see Sources catalog for required options.
The Source ID. Length 1–255 characters.
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 91 agents privately built on Nagent that already use Segment.
Build on Nagent
Connect Segment 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 Segment, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Segment is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Segment is connected, you configure its 17 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Segment 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 Segment event fires, the agent kicks off automatically.
Every Segment 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 Segment ships with 17 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Segment together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Segment-based workflows tailored to your business.