API for enriching user and company data, providing endpoints for token validation and generic search.
API for enriching user and company data, providing endpoints for token validation and generic search. On Nagent, Onepage is exposed as a fully-configurable productivity integration that any agent can call — 2 actions, and BEARER_TOKEN authentication. No code is required to wire Onepage into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Onepage to automate the kinds of tasks productivity 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 Onepage 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 Onepage, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ONEPAGE_SEARCH_INPUT_POST_REQUESTThe SearchInput endpoint allows users to perform a search query within the OnePage platform. It accepts a required search string and optional parameters for language and output format customization. This endpoint is designed for retrieving relevant information based on user-specified search terms, with the ability to filter results by language and choose between structured (JSON) or plain text output. Use this endpoint when you need to search for specific content or information within the OnePage ecosystem. It's particularly useful for integrating search functionality into applications or workflows that interact with OnePage data. Note that this endpoint focuses solely on search functionality and does not provide additional features like content creation or modification.
Input parameters
Language specifies the language code for the search results.
Output specifies the format of the search results (e.g., JSON, TEXT).
Search specifies the search query. This field is required.
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
ONEPAGE_TOKEN_DETAILS_REQUESTRetrieves detailed information about a specific token in the OnePage system. This endpoint should be used when you need to obtain comprehensive data about a token, such as its associated permissions, expiration date, or other metadata. It's particularly useful for token management tasks, such as verifying token validity or checking token attributes. The endpoint accepts a single token and returns its corresponding details. It should not be used for token creation, deletion, or modification operations. Note that the specific details returned may vary based on the OnePage implementation and the token's type or purpose.
Input parameters
The OnePage authentication or API token to retrieve details for. This token is typically obtained from your OnePage account settings or during initial authentication.
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 39 agents privately built on Nagent that already use Onepage.
Build on Nagent
Connect Onepage 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 Onepage, and click "Connect Now." You'll authenticate with BEARER_TOKEN — Nagent handles credential storage and refresh automatically. Once connected, Onepage is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Onepage is connected, you configure its 2 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Onepage 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 Onepage event fires, the agent kicks off automatically.
Every Onepage 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 Onepage ships with 2 pre-built productivity actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Onepage together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Onepage-based workflows tailored to your business.