HotspotSystem provides public Wi-Fi hotspot management and billing services for businesses.
HotspotSystem provides public Wi-Fi hotspot management and billing services for businesses. On Nagent, Hotspotsystem is exposed as a fully-configurable internet of things integration that any agent can call — 19 actions, and API key authentication. No code is required to wire Hotspotsystem into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Hotspotsystem to automate the kinds of tasks internet of things 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 Hotspotsystem 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 Hotspotsystem, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HOTSPOTSYSTEM_CUSTOMERS_LISTLists all customers in the HotspotSystem account with optional filtering. Use this tool to: - Retrieve all customers with their details (name, email, contact info, registration date, etc.) - Paginate through large customer lists using limit and offset parameters - Sort customers by any field in ascending or descending order - Filter response to only include specific fields to reduce payload size Returns metadata with total customer count and an array of customer objects.
Input parameters
Field name to sort results by. Prepend '-' for descending order (e.g., '-customer_name' for reverse alphabetical by name). Common fields: customer_name, email, registered_at.
Maximum number of customers to return in a single response. Defaults to 100 if not specified.
Comma-separated list of specific field names to include in each customer object. If omitted, all fields are returned. Available fields include: customer_id, customer_name, user_name, email, company_name, address, city, state, zip, country_code, phone, registered_at.
Number of customers to skip before starting to return results (for pagination). Defaults to 0.
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
HOTSPOTSYSTEM_CUSTOMERS_LIST_BY_LOCATIONLists all customers associated with a specific HotspotSystem location. Use this tool to: - Retrieve customer details (name, email, contact info, registration date) for a specific location - Paginate through large customer lists using limit and offset parameters - Sort customers by any field (prepend '-' for descending order, e.g., '-registered_at') - Filter response to include only specific fields to reduce payload size - Query customers at different locations by location ID Returns metadata with total customer count and an array of customer objects. Note: Empty results (total_count: 0) indicate no customers are registered at the specified location.
Input parameters
Property name to sort by; prepend '-' for descending order (e.g., '-registered_at')
Number of items to return per page; must be >= 1
Comma-separated list of fields to include in the response. Available fields: id, user_name, name, email, company_name, address, city, state, zip, country_code, phone, registered_at. If omitted, all fields are returned.
Number of customers to skip before returning results (for pagination); must be >= 0. Use with limit to paginate through results.
Unique identifier of the HotspotSystem location to query customers from
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
HOTSPOTSYSTEM_GENERATE_VOUCHER_V1Generates an access voucher code on-demand for a specific location. This action creates a single-use voucher that can be used for hotspot access. The voucher is generated against available voucher credits in the specified location. Use this when you need to provide immediate access codes to users. Note: Requires an active location with available voucher credits (use the List Locations action first to get valid location_id values).
Input parameters
Response format, either 'json' or 'xml'. Defaults to 'json'.
Custom package ID defining voucher parameters. Defaults to the location's default free access if omitted.
Location ID or location group ID where the voucher can be activated. Defaults to the same location if omitted.
ID of the location from which voucher credits will be deducted. Obtain valid location IDs using the List Locations action. The location must have available voucher credits.
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
HOTSPOTSYSTEM_GET_LOCATIONS_OPTIONSTool to get simplified list of locations as dropdown options. Returns only id/name pairs for each location. Use when you need location options for selection menus or dropdowns.
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
HOTSPOTSYSTEM_GET_METool to verify the resource owner's credentials and retrieve authenticated user information. Use when you need to confirm authentication status or get the current user's ID and operator 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
HOTSPOTSYSTEM_LIST_PAID_TRANSACTIONSTool to list paid transactions globally across all locations. Use when you need to retrieve all paid transaction records with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order (e.g., '-action_date_gmt' for newest first)
Maximum number of items to return per page; must be >= 1
Comma-separated list of field names to include in the response. Available fields: id, operator, location_id, user_name, customer, action_date_gmt, amount, currency, user_agent, newsletter, company_name, email, address, city, state, zip, country_code, phone, language, smscountry
Zero-based offset for pagination; must be >= 0 (use with limit for paging)
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
HOTSPOTSYSTEM_LOCATIONS_LISTTool to list the resource owner's locations. Use when you need to retrieve locations with optional filtering, sorting, or pagination.
Input parameters
Property name to sort by; prepend '-' for descending order.
Number of items to return per page; must be >= 1.
Comma-separated location property names to include in the response.
Zero-based page offset; must be >= 0.
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
HOTSPOTSYSTEM_MISC_PINGTool to perform health check against the HotspotSystem API. Use when verifying connectivity and availability.
Input parameters
Additional optional query parameter for edge-case testing (unicode/special chars).
Optional echo value sent as query parameter for testing; the API ignores it.
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
HOTSPOTSYSTEM_SUBSCRIBERS_LISTList newsletter subscribers across all locations with optional filtering, sorting, and pagination. Returns subscriber information including contact details (name, email, phone, address) and social network data (Facebook, Google, etc.). Supports field selection to retrieve only needed properties, sorting by any field (ascending or descending), and pagination with limit/offset for large result sets. Use this tool when you need to: - Retrieve all subscribers for the account - Filter subscribers by specific fields - Sort subscribers by registration date, name, email, etc. - Paginate through large subscriber lists
Input parameters
Field name to sort results by. Prepend '-' for descending order. Examples: 'email' (ascending A-Z), '-registered_at' (newest first), 'name' (ascending A-Z). Can sort by any subscriber field.
Maximum number of subscribers to return per request. Must be >= 1. Use with offset for pagination through large result sets. Default is API-determined if not specified.
Comma-separated list of subscriber fields to include in response. Reduces response size by returning only specified fields. Available fields: id, username, name, email, company_name, address, city, state, zip, country_code, phone, social_network, social_id, social_username, social_link, social_gender, social_age_range, social_followers_count, registered_at. Example: 'id,email,name' returns only ID, email, and name fields.
Number of subscribers to skip before returning results. Must be >= 0. Use with limit for pagination. Example: limit=10, offset=0 returns first 10; limit=10, offset=10 returns next 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
HOTSPOTSYSTEM_SUBSCRIBERS_LIST_BY_LOCATIONTool to list subscribers by location. Use when you need to retrieve subscribers for a specific location with optional field selection, sorting, and pagination.
Input parameters
Property name to sort by; prepend '-' for descending order (e.g., '-registered_at')
Number of items to return per page; must be >= 1
Comma-separated list of fields to include in the response (e.g., 'id,email,name')
Zero-based page index when paginating; must be >= 0
ID of the 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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_MACTool to list MAC-based transactions. Use when you need to retrieve MAC transaction records with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order.
Maximum number of items to return; must be >= 1.
Comma-separated list of field names to include in the response.
Zero-based offset for pagination; must be >= 0.
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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_MAC_BY_LOCATIONLists MAC address authentication transactions for a specific location. MAC (Media Access Control) transactions track network access granted based on device MAC addresses. Use this action when you need to: - View MAC-based authentication history for a specific location - Monitor which devices accessed the network via MAC authentication - Retrieve transaction records with customer data and custom fields - Filter and paginate MAC transaction records for reporting For transactions across all locations, use the global MAC transactions endpoint instead.
Input parameters
Sort by any field; prepend '-' for descending order
Maximum number of items to return; must be >= 1
Comma-separated list of field names to include in the response. Available fields: id, operator, location_id, user_name, action_date_gmt, package_id, user_agent, customer fields (email, address, city, state, zip, country_code, phone), and custom questions/answers (q1-q5, a1-a5)
Zero-based offset for pagination; must be >= 0
ID of the location to retrieve MAC transactions for
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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_PAID_BY_LOCATIONTool to list paid transactions by location. Use when you need to retrieve paid transaction records for a specific location with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order
Maximum number of items to return; must be >= 1
Comma-separated list of field names to include in the response
Zero-based offset for pagination; must be >= 0
ID of the 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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_SOCIALTool to list social transactions. Use when you need to retrieve social transaction records with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order.
Maximum number of items to return; must be >= 1.
Comma-separated list of field names to include in the response.
Zero-based offset for pagination; must be >= 0.
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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_SOCIAL_BY_LOCATIONTool to list social transactions by location. Use when you need to retrieve social transaction records for a specific location with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order
Maximum number of items to return; must be >= 1
Comma-separated list of field names to include in the response
Zero-based offset for pagination; must be >= 0
ID of the 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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_VOUCHERTool to list voucher transactions globally across all locations.
Input parameters
Sort by any field; prepend '-' for descending order (e.g., '-action_date_gmt' for newest first)
Maximum number of items to return per page; must be >= 1
Comma-separated list of field names to include in the response. Available fields: id, operator, location_id, user_name, customer, action_date_gmt, amount, currency, user_agent, newsletter, company_name, email, address, city, state, zip, country_code, phone, language, smscountry
Zero-based offset for pagination; must be >= 0 (use with limit for paging)
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
HOTSPOTSYSTEM_TRANSACTIONS_LIST_VOUCHER_BY_LOCATIONTool to list voucher transactions by location. Use when you need to retrieve voucher transaction records for a specific location with optional pagination and sorting.
Input parameters
Sort by any field; prepend '-' for descending order
Maximum number of items to return; must be >= 1
Comma-separated list of field names to include in the response
Zero-based offset for pagination; must be >= 0
ID of the 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
HOTSPOTSYSTEM_VOUCHERS_LISTTool to list the resource owner's vouchers across all locations. Use when you need to retrieve vouchers with optional filtering, sorting, or pagination.
Input parameters
Property name to sort by; prepend '-' for descending order.
Number of items to return per page; must be >= 1.
Comma-separated voucher property names to return.
Zero-based page index when paginated by limit; must be >= 0.
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
HOTSPOTSYSTEM_VOUCHERS_LIST_BY_LOCATIONRetrieves all vouchers associated with a specific location in the HotspotSystem. Use this action to: - List all vouchers available at a particular location - Filter voucher results by specific fields - Sort vouchers by any field (e.g., validity, price) - Implement pagination for large voucher lists Each voucher includes details such as serial number, access code, usage limits (traffic/download/upload), validity period, and pricing information.
Input parameters
Field name to sort results by. Prepend '-' for descending order (e.g., '-validity' sorts by validity descending, 'price_enduser' sorts by price ascending).
Maximum number of vouchers to return per page (minimum 1). Use with offset for pagination.
Comma-separated list of voucher fields to include in the response (e.g., 'serial,voucher_code,validity'). If omitted, all fields are returned.
Number of vouchers to skip before returning results (minimum 0). Use with limit for pagination. For example, offset=10 with limit=5 returns vouchers 11-15.
The unique identifier of the location. Obtain location IDs using the Locations List action.
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 84 agents privately built on Nagent that already use Hotspotsystem.
Build on Nagent
Connect Hotspotsystem 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 Hotspotsystem, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Hotspotsystem is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Hotspotsystem is connected, you configure its 19 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Hotspotsystem 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 Hotspotsystem event fires, the agent kicks off automatically.
Every Hotspotsystem 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 Hotspotsystem ships with 19 pre-built internet of things actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Hotspotsystem together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Hotspotsystem-based workflows tailored to your business.