Amplitude gives you the self-serve tools and real-time data to make products and experiences that win no matter what.
Amplitude gives you the self-serve tools and real-time data to make products and experiences that win no matter what. On Nagent, Amplitude is exposed as a fully-configurable analytics integration that any agent can call — 54 actions, and API key authentication. No code is required to wire Amplitude into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Amplitude 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 Amplitude 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 Amplitude, with input parameters and output schema. Drop these into any step of an agent built in Helix.
AMPLITUDE_ASSIGN_ANNOTATIONS_TO_CATEGORYTool to bulk assign multiple annotations to a category in Amplitude. Use when you need to organize annotations by assigning them to a specific category.
Input parameters
Category ID to assign annotations to
Array of annotation IDs to assign to the category
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
AMPLITUDE_CANCEL_DELETIONCancel a pending user deletion request in Amplitude. Use this to remove a user from a scheduled deletion job before it completes. Only works on deletion jobs in 'Staging' status (not yet submitted).
Input parameters
The Amplitude ID to remove from the deletion job. This is the unique identifier for the user whose deletion request you want to cancel.
The scheduled deletion date in YYYY-MM-DD format. This is the date when the deletion job is scheduled to begin. Must match the exact date from the original deletion 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
AMPLITUDE_CHECK_COHORT_STATUSCheck the status of a cohort export request. This action allows you to: - Poll the status of an in-progress cohort download request - Determine if a cohort is ready for download
Input parameters
Request ID from cohort 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
AMPLITUDE_CREATE_ANNOTATIONCreate a chart annotation in Amplitude to mark important dates. Use to highlight key events like feature releases, marketing campaigns, or product updates on analytics charts.
Input parameters
End date/time in ISO 8601 format for time ranges. Omit for single-point annotations.
The title of the annotation
Start date/time in ISO 8601 format (e.g., '2025-11-01T07:00:00+00:00')
Additional details or description for the annotation
Category name to organize the annotation (e.g., 'Releases', 'Marketing'). Must be an existing category.
Specific chart ID to associate the annotation with. Omit to create a global annotation visible across all charts.
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
AMPLITUDE_CREATE_ANNOTATION_CATEGORYTool to create an annotation category in Amplitude to organize annotations. Use when you need to create a new category for grouping related annotations.
Input parameters
The name of the annotation category to create
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
AMPLITUDE_CREATE_EVENT_CATEGORYCreate a new event category in Amplitude. This action allows you to: - Create a new event category to organize event types - Validate category name before creation Key features: - Creates event categories for organizing events - Returns success/failure status
Input parameters
Name of the category to create
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
AMPLITUDE_CREATE_EVENT_TYPECreate a new event type in Amplitude. This action allows you to: - Define a new event type with various properties - Associate the event with a category - Add metadata like description, tags, and owner Key features: - Creates trackable events in your Amplitude project - Supports full event type configuration
Input parameters
List of tags, separated by a comma
Owner of the event type
The event type's category
Activity of the event type
The event name
Details about the event type
Event type is hidden from timeline
Event type is hidden from dropdowns
Event type is hidden from pathfinder
Event type is hidden from persona 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
AMPLITUDE_CREATE_RELEASECreate a release to document product changes. Use when you want to track app version releases and their impact on metrics. Can be integrated into deployment workflows to automatically log releases in Amplitude.
Input parameters
Title of the release for easy identification
Version string for the release (e.g., '1.0.0', '2.1.3')
Array of platforms this release applies to (e.g., \['iOS', 'Android', 'Web'\])
Description of what changed in this release. Include key features, bug fixes, or improvements.
Release start date/time in format 'YYYY-MM-DD HH:MM:SS' (e.g., '2026-02-12 00:00:00'). This marks when the release became active.
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
AMPLITUDE_DELETE_ANNOTATIONDelete a chart annotation from Amplitude. Use to remove existing annotations from charts.
Input parameters
Annotation ID 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
AMPLITUDE_DELETE_ANNOTATION_CATEGORYDelete an annotation category from Amplitude. Use when you need to remove an annotation category that is no longer needed.
Input parameters
The ID of the annotation category 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
AMPLITUDE_DELETE_EVENT_CATEGORYDelete an event category from Amplitude. This action allows you to: - Delete an existing event category - Remove category organization from events Key features: - Permanently removes event categories - Returns success/failure status
Input parameters
ID of the category 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
AMPLITUDE_DELETE_EVENT_TYPEDelete an event type from Amplitude. This action allows you to: - Remove an event type from your project - Mark live events as deleted - Remove planned events from the tracking plan Key features: - Different behavior based on event status (live, planned, etc.) - Returns success/failure status
Input parameters
The event name 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
AMPLITUDE_DELETE_USERSSubmit user deletion requests for GDPR/CCPA compliance. Supports up to 100 users per request. Use when you need to delete user data from Amplitude in compliance with privacy regulations. Either amplitude_ids or user_ids must be provided.
Input parameters
Array of string User IDs to delete (e.g., \['user_1', 'user_2'\]). Either amplitude_ids or user_ids must be provided. Maximum 100 users per request.
Email address of the person requesting deletion (for auditing). Must be a valid email format.
Array of numeric Amplitude IDs to delete (e.g., \[123456, 789012\]). Either amplitude_ids or user_ids must be provided. Maximum 100 users per request.
If true, deletes from entire organization instead of single project. Default false.
Must be string 'True' or 'False' (capitalized). When 'True', API returns 200 even if IDs don't exist. When 'False' (default), returns 400 for invalid IDs.
If true, returns valid user_id values corresponding to supplied amplitude_ids 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
AMPLITUDE_DOWNLOAD_COHORT_FILEDownload the cohort file after request is complete. Use this action after checking that the cohort status is 'JOB COMPLETED'. The download link is valid for 7 days, but the S3 link is valid for only 1 minute.
Input parameters
Request ID from cohort download 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
AMPLITUDE_FIND_USERSearch for users in Amplitude by canonical identifier (Amplitude ID, device ID, user ID, or user ID prefix). Use this to find matching Amplitude IDs for deterministic user mapping. Important: This searches only canonical identifiers (Amplitude ID, device_id, user_id), NOT arbitrary user properties like email unless email is your actual user_id.
Input parameters
The user identifier to search for. This must be one of: Amplitude ID, Device ID, User ID, or User ID prefix. This searches canonical identifiers (Amplitude ID, device_id, user_id) - NOT arbitrary user properties like email unless email is actually the user_id in your Amplitude project.
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
AMPLITUDE_GET_ACTIVE_USERSGet the number of active or new users for a date range with optional segmentation. Use when you need user count metrics aggregated by day, week, or month, optionally grouped by user properties.
Input parameters
Group by property name for segmentation (e.g., 'city', 'country', 'device_type')
Interval type for aggregation
Metric type for user counts
JSON array string of segment filters to apply to the query
End date in YYYYMMDD format (e.g., '20260212')
Start date in YYYYMMDD format (e.g., '20260205')
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
AMPLITUDE_GET_ANNOTATIONGet a single chart annotation by ID from Amplitude. Use when you need to retrieve detailed information about a specific annotation including its label, timestamps, category, and associated chart.
Input parameters
The ID of the annotation 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
AMPLITUDE_GET_ANNOTATION_CATEGORYGet a single annotation category by ID from Amplitude. Use when you need to retrieve details about a specific annotation category.
Input parameters
Category 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
AMPLITUDE_GET_COHORTGet a single cohort by ID and initiate download. This action allows you to: - Request a specific cohort from Amplitude - Optionally include user properties in the response - Start the asynchronous download process Key features: - Supports filtering by specific user properties - Returns a request ID used for polling status and downloading - Supports EU data residency
Input parameters
Cohort ID to retrieve
User properties to include
Include user properties in 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
AMPLITUDE_GET_DELETION_REQUESTSGet the status of user deletion requests within a date range. Use this to track GDPR/CCPA deletion compliance and monitor deletion job progress.
Input parameters
End date for deletion requests in YYYY-MM-DD format
Start date for deletion requests in YYYY-MM-DD 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
AMPLITUDE_GET_EVENT_CATEGORIESGet event categories from Amplitude. This action allows you to: - Get all event categories in your project - Get a specific category by name
Input parameters
Optional category name to get specific category
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
AMPLITUDE_GET_EVENT_PROPERTYGet a specific event property from Amplitude taxonomy. Use when you need to retrieve details about a specific event property including its type, validation rules, and metadata.
Input parameters
The event property name to retrieve
The event type associated with the property. Optional but recommended to get event-specific property details.
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
AMPLITUDE_GET_EVENT_SEGMENTATIONGet event segmentation data from Amplitude Analytics API. Use this to analyze event metrics over time with optional grouping by properties. Supports multiple metrics (uniques, totals, percentage of DAU, averages) and time intervals (realtime, hourly, daily, weekly).
Input parameters
JSON-encoded event definition. Example: {"event_type":"page_view"} or {"event_type":"purchase","filters":\[{"subprop_type":"event","subprop_key":"price","subprop_op":"greater","subprop_value":\["10"\]}\]}
Property to group results by. Use event property names like 'country', 'device_type', etc.
Time interval for bucketing results: '-300000' (realtime/5-min), '1' (hourly), '7' (daily), '30' (weekly). Default is '1'.
Metric type to calculate. Default is 'uniques'.
End date for the query in YYYYMMDD format
Start date for the query in YYYYMMDD 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
AMPLITUDE_GET_EVENT_TYPEGet a specific event type from Amplitude by name. This action allows you to: - Retrieve detailed information about a single event type - Get all properties and metadata for the event Key features: - Retrieves comprehensive event type details - Returns metadata like category, description, and settings - Supports lookup by exact event name
Input parameters
The event name 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
AMPLITUDE_GET_EVENT_TYPESGet all event types from Amplitude. This action allows you to: - Retrieve all event types in your project - Optionally include deleted events
Input parameters
Whether to include deleted events
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
AMPLITUDE_GET_FUNNEL_DATAGet funnel analysis data showing user conversion through a sequence of events. Use this to analyze user drop-off rates and conversion times across multiple steps in a user journey.
Input parameters
Group by property name. For custom properties, prepend with 'gp:' (e.g., 'gp:country'). Only one group-by property is allowed.
Interval options for funnel analysis
User type options for funnel analysis
Conversion window in seconds (how long users have to complete the funnel). Defaults to 2,592,000 seconds (30 days).
End date in YYYYMMDD format (e.g., '20260212')
Funnel mode options
Number of group-by values to return. Must be between 1 and 1000. Defaults to 100.
Start date in YYYYMMDD format (e.g., '20260201')
List of events representing funnel steps (2-4 events required). Each event represents a step in the user journey.
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
AMPLITUDE_GET_REALTIME_ACTIVE_USERSGet real-time active users count from Amplitude. Returns active user counts with 5-minute granularity (configurable) for today and yesterday. Use this to monitor current user activity and compare with historical data.
Input parameters
Time interval in minutes. The Amplitude realtime endpoint only supports 5-minute intervals. This parameter can be omitted or set to 5. Other values will result in a 400 Bad Request error.
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
AMPLITUDE_GET_RETENTIONGet user retention analysis showing how users return over time after a starting action. Use when analyzing user engagement patterns, measuring feature stickiness, or understanding long-term user behavior across cohorts.
Input parameters
Property to group by (limit of one). Use 'gp:' prefix for custom properties (e.g., 'gp:plan_type')
Interval options in days
JSON-encoded segment definitions for filtering (optional)
Retention bracket ranges, required if rm=bracket. Format: "\[\[0,4\],\[5,9\]\]" for day ranges
JSON-encoded return event object (e.g., '{"event_type":"_active"}' for active users or '{"event_type":"_all"}' for all events)
Retention mode options
JSON-encoded starting event object (e.g., '{"event_type":"_active"}' for active users or '{"event_type":"_new"}' for new users)
End date in YYYYMMDD format
Start date in YYYYMMDD 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
AMPLITUDE_GET_REVENUE_LTVGet revenue lifetime value (LTV) metrics including ARPU, ARPPU, and total revenue. Use when you need to analyze revenue trends over time for user cohorts.
Input parameters
Interval type for revenue LTV aggregation
Metric type for revenue LTV calculation
End date in YYYYMMDD format (e.g., 20260212)
Start date in YYYYMMDD format (e.g., 20260101)
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
AMPLITUDE_GET_SESSION_AVERAGEGet average session length (in seconds) for a specified date range from Amplitude. Use when you need to analyze user engagement patterns and session duration trends over time.
Input parameters
End date in YYYYMMDD format (e.g., '20260212' for February 12, 2026)
Start date in YYYYMMDD format (e.g., '20260113' for January 13, 2026)
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
AMPLITUDE_GET_SESSION_LENGTHTool to retrieve session length distribution data for a specified date range from Amplitude. Use when you need to analyze how long users' sessions typically last or visualize session duration patterns across time buckets.
Input parameters
End date in YYYYMMDD format (e.g., '20260212')
Start date in YYYYMMDD format (e.g., '20260205')
Maximum value for bucketing (e.g., 600). Must be used with binMin and binSize for custom bucketing.
Minimum value for bucketing (e.g., 0). Must be used with binMax and binSize for custom bucketing.
Size of each bucket (e.g., 60 for 60-second buckets). Must be used with binMin and binMax for custom bucketing.
Time unit for bucket sizes: 'hours', 'minutes', or 'seconds'. If not specified, uses default bucketing.
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
AMPLITUDE_GET_SESSIONS_PER_USERTool to get average number of sessions per user for each day in a date range from Amplitude. Use when analyzing user engagement patterns or session frequency over time.
Input parameters
End date in YYYYMMDD format (e.g., '20260212')
Start date in YYYYMMDD format (e.g., '20260205')
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
AMPLITUDE_GET_USER_ACTIVITYFetch a single user's profile summary and event stream by Amplitude ID. Use when you need to extract attribution data (UTM parameters, referrers) from early events or user properties, or when analyzing user behavior patterns.
Input parameters
Amplitude ID of the user to retrieve activity for
Number of events to return (1-1000). Default is 100 to avoid large payloads. Note: session boundary behavior may affect actual count returned.
Zero-indexed offset from most recent event (default: 0)
Direction to retrieve events: 'earliest' for oldest first, 'latest' for newest first (default)
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
AMPLITUDE_GET_USER_COMPOSITIONTool to get user composition breakdown by property (platform, version, country, etc.). Use when analyzing user distribution across property values during a date range.
Input parameters
Property to segment by. Built-in options: 'version', 'country', 'city', 'region', 'DMA', 'language', 'platform', 'os', 'device', 'start_version', 'paying'. Custom user properties use format 'gp:name'
End date in YYYYMMDD format (e.g., '20250212')
Start date in YYYYMMDD format (e.g., '20250211')
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
AMPLITUDE_GET_USER_MAPPINGSGet the list of user mappings for provided user IDs. Use when you need to retrieve aliasing relationships between user identifiers in Amplitude. Returns mapping data showing which users map into and out of the requested user IDs.
Input parameters
Array of user IDs to get mappings for. Returns the list of mappings that involve the provided user IDs.
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
AMPLITUDE_GET_USER_PROPERTYGet a specific user property from Amplitude taxonomy. Use when you need to retrieve details about a specific user property including its type, validation rules, and classifications.
Input parameters
The user property name to retrieve. Custom properties have a 'gp:' prefix.
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
AMPLITUDE_IDENTIFYUpdate user properties using Amplitude's Identify API. This action allows you to: - Set or update the User ID for a Device ID - Update user properties without sending an event - Perform operations on user properties (set, append, etc.) - Update user attributes like device info and location
Input parameters
Your Amplitude API Key for your project. If not provided, will be extracted from authentication credentials.
Single identification object or array of identifications
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
AMPLITUDE_LIST_ANNOTATION_CATEGORIESList all annotation categories from Amplitude. Use to retrieve available categories for chart annotations.
Input parameters
When specified, returns only that particular category. Otherwise returns all categories.
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
AMPLITUDE_LIST_ANNOTATIONSTool to get all chart annotations with optional filtering by category, chart, and date range. Use when you need to retrieve annotations that mark important events or milestones on Amplitude charts.
Input parameters
Filter annotations before this ISO 8601 timestamp
Filter annotations occurring after this ISO 8601 timestamp
Filter by category name (mutually exclusive with chart_id)
Filter by chart ID (mutually exclusive with category)
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
AMPLITUDE_LIST_COHORTSList all discoverable cohorts for an Amplitude project. This action allows you to: - Get a list of all cohorts in your Amplitude project - Optionally include sync information for each cohort Key features: - Returns cohort details including ID, name, size, and definition - Optionally includes sync metadata for integration with other tools - Supports EU data residency. An empty result may indicate insufficient permissions to view cohorts rather than an absence of cohorts in the project.
Input parameters
Whether to include cohort sync metadata
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
AMPLITUDE_LIST_EVENT_PROPERTIESGet all event properties from Amplitude, optionally filtered by event type or property name. Use when you need to retrieve property definitions, data types, or validation rules for events.
Input parameters
Filter by event type name. If provided, returns only properties for this specific event type
Filter by property name. If provided, returns only properties matching this 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
AMPLITUDE_LIST_EVENTSTool to get a list of all event types in your Amplitude project with current week's statistics. Use when you need to see all events and their recent activity metrics including totals, uniques, and DAU percentages.
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
AMPLITUDE_LIST_USER_PROPERTIESTool to get all user properties in your Amplitude project. Use when you need to retrieve the complete list of user properties including both default and custom properties.
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
AMPLITUDE_MAP_USERMap users with different user IDs together (alias/merge users) in Amplitude. Use this to merge user identities across different identifiers or unmap previously merged users. Supports up to 2000 mappings per request with 1MB size limit.
Input parameters
Your Amplitude API Key for any project in your organization. If not provided, will be extracted from authentication credentials
Single mapping object or array of mapping objects to map user IDs together. Can map up to 2000 users per request with 1MB size limit
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
AMPLITUDE_RESTORE_EVENT_TYPERestore a deleted event type in Amplitude. This action allows you to: - Restore a previously deleted event type - Make the event available again in the UI and API Key features: - Undoes the deletion of an event type - Returns success/failure status
Input parameters
The event name to restore
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
AMPLITUDE_SEND_EVENTSSend events to Amplitude using the HTTP V2 API. This action allows you to send events to Amplitude for tracking user behavior and analytics. It supports all Amplitude event fields, handles proper validation, and includes comprehensive error handling.
Input parameters
Array of events to upload
Your Amplitude API Key for your project. If not provided, will be extracted from the authentication metadata.
Model for Amplitude API options
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
AMPLITUDE_SET_GROUP_PROPERTIESSet group properties for account-level reporting without sending an event. Use this action to update group attributes like company name, industry, or plan type. Requires Enterprise plan with Accounts add-on.
Input parameters
Your Amplitude API Key for your project. If not provided, will be extracted from authentication credentials.
Single group identification object or array of identifications (max 1024 per 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
AMPLITUDE_UPDATE_ANNOTATIONTool to update an existing chart annotation in Amplitude. Use when you need to modify annotation properties such as label, timestamps, category, or chart association. Supports partial updates - only include fields you want to change.
Input parameters
Timestamp in ISO 8601 format for annotation end. Set to null to convert to a point-in-time annotation
The title of your annotation
Timestamp in ISO 8601 format for annotation start (e.g., '2026-02-13T00:00:00Z')
Details for the annotation
The name of the category that the annotation belongs to
Chart identifier. Set to null to make annotation visible globally across all charts
The ID of the annotation to update
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
AMPLITUDE_UPDATE_ANNOTATION_CATEGORYTool to update an annotation category in Amplitude. Use when you need to rename or modify an existing annotation category for organizing chart annotations.
Input parameters
Updated name for the annotation category
ID of the annotation category to update
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
AMPLITUDE_UPDATE_COHORT_MEMBERSHIPIncrementally update cohort membership by adding or removing IDs. This action allows you to: - Add new IDs to an existing cohort - Remove IDs from an existing cohort - Perform multiple operations in a single request
Input parameters
Cohort ID to update
Count group of the IDs
Membership operations to perform
Skip invalid IDs
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
AMPLITUDE_UPDATE_EVENT_CATEGORYUpdate an existing event category in Amplitude. This action allows you to: - Update the name of an existing event category - Validate the new category name Key features: - Updates category names - Returns success/failure status
Input parameters
ID of the category to update
New name for the category
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
AMPLITUDE_UPDATE_EVENT_TYPEUpdate an existing event type in Amplitude. This action allows you to: - Change event type properties - Update event name, category, metadata, and settings - Modify display name for ingested events Key features: - Updates event type configuration - Supports partial updates (only specified fields are changed)
Input parameters
List of tags, separated by a comma
Owner of the event type
Category name for the event type
Activity of the event type
The event name to update
Details about the event type
Display name of the event type
New name for the event type
Event type is hidden from timeline
Event type is hidden from dropdowns
Event type is hidden from pathfinder
Event type is hidden from persona 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
AMPLITUDE_UPLOAD_BATCH_EVENTSBulk upload events to Amplitude using the Batch Event Upload API. Supports larger payloads (20MB) and higher throttling limits than HTTP V2 API. Use when you need to send large batches of events efficiently.
Input parameters
Array of events to upload
Your Amplitude API Key for your project. If not provided, will be extracted from the authentication metadata.
Model for Amplitude API options
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
AMPLITUDE_UPLOAD_COHORTGenerate a new cohort or update an existing cohort by uploading user IDs or Amplitude IDs. Use when you need to create cohorts from a specific list of users.
Input parameters
Array of user IDs or Amplitude IDs to include in the cohort
Name of the cohort
Email address of the cohort owner (must be a valid email)
Project ID for the cohort
Type of IDs being uploaded: BY_AMP_ID for Amplitude IDs or BY_USER_ID for user IDs
Whether the cohort is discoverable by other users in the project
ID of an existing cohort to update. If provided, the cohort will be updated instead of creating a new one
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 81 agents privately built on Nagent that already use Amplitude.
Build on Nagent
Connect Amplitude 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 Amplitude, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Amplitude is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Amplitude is connected, you configure its 54 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Amplitude 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 Amplitude event fires, the agent kicks off automatically.
Every Amplitude 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 Amplitude ships with 54 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Amplitude together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Amplitude-based workflows tailored to your business.