Cloudpress enables exporting content from Google Docs and Notion to various Content Management Systems.
Cloudpress enables exporting content from Google Docs and Notion to various Content Management Systems. On Nagent, Cloudpress is exposed as a fully-configurable documents integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Cloudpress into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Cloudpress to automate the kinds of tasks documents 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 Cloudpress 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 Cloudpress, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CLOUDPRESS_GET_ACCOUNT_INFORMATIONTool to retrieve authenticated account information. Use after authentication to get current account 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
CLOUDPRESS_LIST_COLLECTIONSTool to list all collections in the user's Cloudpress account. Use when you need to browse or manage collection metadata. Supports pagination via pageNo and pageSize.
Input parameters
Page number to return, must be >=1.
Number of items per page, must be >=1. Default is 50.
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
CLOUDPRESS_LIST_CONNECTIONSTool to list all connections with pagination. Use when you need to retrieve Cloudpress connections page by page with optional filters like kind, type, or sourceReference.
Input parameters
The kind of connection to filter by. Cannot be used in conjunction with type.
The type of connection to filter by. Cannot be used in conjunction with kind.
The page of results you would like to return. Starts at 1.
The number of items to return per page. Default is 50.
The connection properties to filter by. Can only be used in conjunction with type.
An optional source document reference. If provided, lastExport indicates when this document was last exported.
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
CLOUDPRESS_LIST_DOCUMENT_EXPORTSTool to retrieve a paginated list of document exports. Use after initiating export jobs to fetch export history.
Input parameters
Page number to return, must be >= 1.
Number of items per page, must be >= 1. Defaults to 50.
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
CLOUDPRESS_LIST_WEBHOOKSTool to retrieve a paginated list of webhooks. Use when you need an overview of all configured webhooks.
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 80 agents privately built on Nagent that already use Cloudpress.
Build on Nagent
Connect Cloudpress 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 Cloudpress, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Cloudpress is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Cloudpress is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Cloudpress 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 Cloudpress event fires, the agent kicks off automatically.
Every Cloudpress 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 Cloudpress ships with 5 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Cloudpress together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Cloudpress-based workflows tailored to your business.