Headout is a travel experiences and activities booking platform offering tours, attractions, and entertainment bookings worldwide.
Headout is a travel experiences and activities booking platform offering tours, attractions, and entertainment bookings worldwide. On Nagent, Headout is exposed as a fully-configurable scheduling & booking integration that any agent can call — 8 actions, and API key authentication. No code is required to wire Headout into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Headout to automate the kinds of tasks scheduling & booking 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 Headout 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 Headout, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HEADOUT_GET_PRODUCT_BY_IDTool to retrieve detailed product information by product ID. Use when you need comprehensive product details including pricing, images, location, variants, and availability.
Input parameters
Language code for product details (defaults to EN). Supported languages include EN, ES, FR, IT, DE, PT, NL, etc.
The unique identifier for the product to retrieve.
Currency code for pricing in ISO 4217 format (e.g., USD, EUR, GBP, AED). If not specified, default currency will be used.
Controls whether to include variant data in the response. Defaults to true if not specified.
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
HEADOUT_LIST_CATEGORIES_V2Tool to fetch all available activity categories for a specific city using V2 API. Use when you need to list categories of activities available in a particular city location.
Input parameters
The city code to fetch categories for (e.g., 'NEW_YORK', 'LONDON').
Language code for the response. Defaults to 'EN' if not provided.
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
HEADOUT_LIST_CITIESTool to list all active cities with pagination support. Use when you need to retrieve available cities from the Headout platform. Supports pagination through offset and limit parameters.
Input parameters
Maximum number of results to return. Used for pagination purposes.
Starting point for retrieving results. Used for pagination purposes.
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
HEADOUT_LIST_COLLECTIONS_V2Tool to fetch all collections for a specific city using V2 API with pagination support. Use when you need to browse collections available in a particular city, with optional language-specific content and pagination controls.
Input parameters
Limit for pagination. Defaults to 10 if not provided. Specifies the maximum number of collections to return.
Offset for pagination. Defaults to 0 if not provided.
The city code to fetch collections for (e.g., 'DUBAI', 'LONDON', 'NEW_YORK').
Language code for localized content. Defaults to 'EN' if not provided.
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
HEADOUT_LIST_INVENTORY_BY_VARIANTTool to retrieve available inventory and pricing for a specific product variant. Use when you need to check availability and pricing details for booking.
Input parameters
Maximum number of records to return per page.
Pagination offset for result set navigation.
The identifier for the product variant needing inventory lookup.
End date-time for inventory query in fm-date-time format; treated as unlimited if not provided.
Three-letter currency code for pricing presentation (e.g., USD, AED) per ISO 4217 standard.
Start date-time for inventory query in fm-date-time format; defaults to current timestamp if omitted.
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
HEADOUT_LIST_PRODUCTS_BY_CATEGORYTool to list product listings filtered by category ID with pagination support. Use when you need to retrieve products for a specific category.
Input parameters
Number of results to return per request. Controls pagination.
Offset value for pagination. Use to retrieve next set of results.
Language code for the response. Supported languages include EN, ES, FR, IT, DE, PT, NL. Defaults to EN.
The ID of the category to filter products by.
Currency code following ISO 4217 standard (e.g., USD, EUR, AED).
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
HEADOUT_LIST_PRODUCTS_V2Tool to fetch products using Headout V2 API with filtering by city, collection, category, or subcategory. Use when you need to retrieve product listings for specific locations or categories with pagination support.
Input parameters
Pagination limit - maximum number of products to return. Defaults to 20.
Pagination offset - the number of items to skip. Defaults to 0.
The city code for product filtering. Required parameter to fetch products for a specific city.
Optional category identifier to filter products by category.
Optional campaign name for filtering products by marketing campaign.
Optional collection identifier to filter products by collection.
Currency code for pricing display.
Language preference for product content. Defaults to EN if not specified.
Optional subcategory identifier to filter products by subcategory.
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
HEADOUT_LIST_SUBCATEGORIES_V2Tool to fetch all subcategories for a specific city using V2 API. Use when you need to list subcategories of activities available in a particular city location.
Input parameters
The city code to fetch subcategories for (e.g., 'NEW_YORK', 'LONDON', 'PARIS').
Language code for the response. Defaults to 'EN' if not provided.
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 44 agents privately built on Nagent that already use Headout.
Build on Nagent
Connect Headout 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 Headout, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Headout is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Headout is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Headout 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 Headout event fires, the agent kicks off automatically.
Every Headout 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 Headout ships with 8 pre-built scheduling & booking actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Headout together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Headout-based workflows tailored to your business.