Yandex is a Russian internet services provider offering search, email, navigation, and other web-based solutions, often referred to as “Russia’s Google”
Yandex is a Russian internet services provider offering search, email, navigation, and other web-based solutions, often referred to as “Russia’s Google” On Nagent, Yandex is exposed as a fully-configurable email integration that any agent can call — 21 actions, and OAuth authentication. No code is required to wire Yandex into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Yandex to automate the kinds of tasks email 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 Yandex 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 Yandex, with input parameters and output schema. Drop these into any step of an agent built in Helix.
YANDEX_GEOCODER_REVERSETool to convert geographic coordinates to a human-readable address (reverse geocoding). Returns address information including street, city, country, and other location details. Use this when you have latitude/longitude coordinates and need to find the corresponding address.
Input parameters
Filter results by toponym type (house, street, metro, district, locality)
Preferred language and region for the response in format language_region
Yandex Maps HTTP Geocoder API key. Get your key from Yandex Developer Dashboard.
Response format; only 'json' is supported
Latitude of the location in decimal degrees (range: -90 to 90)
Longitude of the location in decimal degrees (range: -180 to 180)
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
YANDEX_GET_ACCOUNT_EXPERIMENTSTool to retrieve Yandex Music account experimental features and A/B testing flags. Use when you need to check which experimental features are enabled for an 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
YANDEX_GET_ACCOUNT_STATUSTool to retrieve Yandex Music account status and permissions. Use when you need to check account availability, region, subscription status, and granted permissions.
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
YANDEX_GET_GENRESTool to retrieve the list of music genres from Yandex Music. Use when you need to get available music genres for browsing or categorization.
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
YANDEX_GET_PERMISSION_ALERTSTool to retrieve permission alerts and notifications from Yandex Music API. Use this to check for system notifications about subscription status, permissions, or other user alerts.
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
YANDEX_GET_PLAYLISTS_IDS_BY_TAGTool to retrieve playlist IDs associated with a specific tag. Use when you need to find playlists categorized under a tag like 'rock', 'pop', or 'jazz'.
Input parameters
Tag identifier to get playlist IDs for. Examples: 'rock', 'pop', 'jazz'
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
YANDEX_GET_PUBLIC_RESOURCETool to retrieve metadata for a public file or folder on Yandex Disk. Use when you need to get information about publicly shared resources including their properties, nested items, and download URLs.
Input parameters
Path to a resource within the public folder (relative to the folder root).
Field to sort nested resources by (e.g., 'name', 'created', 'modified', 'size'). Prefix with '-' for descending order.
Maximum number of nested resources to return. Use for paginating through folder contents.
Comma-separated list of attributes to return. If not specified, all available attributes are returned.
Offset from the beginning of the nested resources list. Use with limit for pagination.
Public key or public URL of the resource (e.g., 'https://disk.yandex.ru/d/3LwGaY3ast26ig')
Whether to allow cropping the preview image. Set to true to enable preview cropping.
Size of the preview image (e.g., 'S', 'M', 'L', 'XL', '100x100').
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
YANDEX_GET_PUBLIC_RESOURCE_DOWNLOAD_LINKTool to get a direct download link for a publicly shared Yandex Disk resource. Use when you need to download a file or folder that has been shared publicly.
Input parameters
Path to a specific resource within a public folder. Use this to get a download link for a file inside a shared folder.
Comma-separated list of attributes to return in the response. If not specified, all available attributes are returned.
Public key or public URL of the resource to download. This is the share link from Yandex Disk (e.g., 'https://disk.yandex.ru/d/3TNxutqLD1ZqdA').
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
YANDEX_GET_ROTOR_ACCOUNT_STATUSTool to retrieve authenticated user's rotor account status with supplementary fields. Use to check user subscription status, permissions, and radio-specific settings like skips_per_hour.
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
YANDEX_GET_ROTOR_STATIONS_DASHBOARDTool to retrieve recommended radio stations for the current user. Use when you need to get the user's personalized station dashboard.
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
YANDEX_GET_SETTINGSTool to retrieve Yandex Music settings including available purchase products and payment configuration. Use when you need to check available subscription options, pricing, or payment methods.
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
YANDEX_GET_STATIONS_LISTTool to retrieve all radio stations with user settings from Yandex Music. Use when you need to get the list of available radio stations and their configurations.
Input parameters
Language for station information. Common values: 'ru' for Russian, 'en' for English, 'uk' for Ukrainian.
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
YANDEX_GET_TRACK_DOWNLOAD_INFOTool to retrieve available download options for a Yandex Music track. Returns a list of download variants with different codecs (MP3/AAC) and bitrates. Use this when you need to get download links for a specific track ID.
Input parameters
Unique identifier of the track to retrieve download information for. Use the track ID from Yandex Music.
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
YANDEX_LIST_FILTERSTool to retrieve all filters configured for a Yandex Metrica counter. Use when you need to view existing filters for data filtering or analysis.
Input parameters
Counter ID for which to retrieve filters
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
YANDEX_LIST_GOALSTool to retrieve all goals configured for a Yandex Metrica counter. Use when you need to list or inspect goals for analytics tracking.
Input parameters
Counter ID to retrieve goals for. This is the unique identifier of the Yandex Metrica counter.
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
YANDEX_LIST_GRANTSTool to retrieve the list of permissions (grants) for a Yandex Metrica counter. Use when you need to check who has access to view or manage a counter and their permission levels.
Input parameters
JSONP callback function name (optional)
Counter ID for which to retrieve grants (permissions)
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
YANDEX_LIST_LOG_REQUESTSTool to retrieve a list of log requests for a Yandex Metrica counter. Use when you need to view all log requests associated with a specific counter ID.
Input parameters
Counter ID (tag ID) for which to retrieve log requests
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
YANDEX_LIST_STORAGE_BUCKETSTool to list all Yandex Object Storage buckets owned by the authenticated user. Use when you need to retrieve a list of available S3-compatible storage buckets.
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
YANDEX_ORGANIZATION_SEARCHTool to find businesses and organizations by name, address, or TIN. Use when you need to search for companies in a specific region or text query.
Input parameters
Longitude,latitude of search center. Used with spn or bbox to bound search area.
Longitude span,latitude span for search area. Used with ll.
Identifier from previous geosuggest result. If set, text is ignored.
Bounding box as 'lon1,lat1~lon2,lat2'. Overrides ll+spn if provided.
Preferred response language and regional settings in format language_region. Supported: ru_RU, uk_UA, be_BY, en_RU, en_US, tr_TR.
Restrict search to defined area (ll+spn or bbox). True to restrict, False to allow outside search.
Number of results to skip. Must be a multiple of `results` if > 0.
Search query text: business name, address, TIN, coordinates, or phone number.
Type of search results; fixed to 'biz' for organization search.
API key issued in the Yandex Developer Dashboard for Places API. Activation takes up to 15 minutes.
Maximum number of results to return (1-50). Default is 10.
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
YANDEX_ROUTETool to generate detailed route for driving, walking, or public transport. Use when planning a route between specified geographic points.
Input parameters
Transport mode for the route.
Vehicle width in meters (truck only).
Yandex Maps API key. Activation may take up to 15 minutes.
Vehicle height in meters (truck only).
Vehicle length in meters (truck only).
Comma-separated floor levels per waypoint (must match number of waypoints). Available for walking and transit modes on paid plans.
Vehicle weight in tons (truck only).
Vehicle load capacity in tons (truck only).
Disable traffic-aware routing (only for driving or truck modes).
Vehicle emission standard (truck only).
Route waypoints in WGS84 'latitude,longitude' format separated by '\\ | '. Use up to 50 points for driving/truck modes, and up to 25 for other modes.
Maximum allowed vehicle weight in tons (truck only).
Avoid toll roads (only for driving or truck modes).
Polygons to avoid during routing, each formatted as 'lat,lon\\ | lat,lon\\ | ...'. Only for driving or truck modes.
Vehicle axle load in tons (truck only).
Indicates if the vehicle has a trailer (truck only).
Departure time as UNIX timestamp in seconds. Ignored for walking, bicycle, or scooter modes, or when traffic is disabled.
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
YANDEX_TILESTool to fetch individual map tile images by x/y coordinates and zoom level. Use after calculating tile indices for custom map rendering.
Input parameters
Map layer type. Only 'map' (roadmap) is supported.
Tile number on the X axis (calculate per docs).
Tile number on the Y axis (calculate per docs).
Zoom level, integer from 0 (whole world) up to 20 (street level).
Map caption language and region, in ISO 639-1_language + ISO 3166-1_region format. Determines feature-label language and regional settings.
Scale factor for tile image size (range: 0.1-4.0). Values >1.0 produce larger hi-res tiles (e.g., 512x512 for scale=2), values <1.0 shrink the tile. Default is 1.0 (256x256 pixels).
Developer API key issued in the Yandex Developer Dashboard. Activation may take up to 15 minutes. If not provided, will attempt to use the API key from the connected account.
Predefined map style mode (default 'map').
Projection: 'wgs84_mercator' for elliptical Mercator (default), 'web_mercator' for spherical Web Mercator.
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 47 agents privately built on Nagent that already use Yandex.
Build on Nagent
Connect Yandex 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 Yandex, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Yandex is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Yandex is connected, you configure its 21 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Yandex 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 Yandex event fires, the agent kicks off automatically.
Every Yandex 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 Yandex ships with 21 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Yandex together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Yandex-based workflows tailored to your business.