Formsite helps users create online forms and surveys with drag-and-drop tools, secure data capture, and integrations to simplify workflows
Formsite helps users create online forms and surveys with drag-and-drop tools, secure data capture, and integrations to simplify workflows On Nagent, Formsite is exposed as a fully-configurable forms & surveys integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Formsite into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Formsite to automate the kinds of tasks forms & surveys 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 Formsite 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 Formsite, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FORMSITE_GET_FORMThis tool retrieves detailed information about a specific form in Formsite. It provides comprehensive details including the form's internal description, directory identifier, name, publishing information (embed code and form link), current state (e.g., "open"), and statistics (file size and number of results). **Important**: If the connection's base_url doesn't include the user directory, you must provide the 'user_dir' parameter. Find this in your Formsite form URLs (e.g., if URL is https://fs8.formsite.com/user123/forms/abc, user_dir is 'user123') or in Settings -> Integrations -> Formsite API.
Input parameters
The form's directory identifier (also called form ID). This can be found in your form's URL after '/forms/' (e.g., in 'https://fs8.formsite.com/abc123/forms/xyz789', the form_dir is 'xyz789').
The user directory for your Formsite account. If not provided, it will be extracted from the base_url. You can find this in your form URLs (e.g., if your form URL contains '/vSkOfz/forms/', your user_dir is 'vSkOfz') or in Settings -> Integrations -> Formsite API.
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
FORMSITE_GET_FORM_ITEMSRetrieves all items (questions) for a specific form using the Formsite API. This action returns detailed information about each form item including: - Item ID (unique identifier for the form question) - Position (sequential order in the form) - Label (the question text) - Children (optional, for Matrix and Multi Scale items with sub-items) The item data can be used to label results data by matching item IDs from this action to item IDs from the Get Form Results action. **Important**: If the connection's base_url doesn't include the user directory, you must provide the 'user_dir' parameter. Find this in your Formsite form URLs (e.g., if URL is https://fs8.formsite.com/user123/forms/abc, user_dir is 'user123') or in Settings -> Integrations -> Formsite API.
Input parameters
The form's directory/ID to retrieve items from
The user directory for your Formsite account. If not provided, it will be extracted from the base_url. You can find this in your form URLs (e.g., if your form URL contains '/vSkOfz/forms/', your user_dir is 'vSkOfz') or in Settings -> Integrations -> Formsite API.
Optional. Results Labels ID to apply for item labels
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
FORMSITE_GET_FORM_RESULTSThis tool retrieves form results from a specified FormSite form. It uses the GET https://{server}.formsite.com/api/v2/{user_dir}/forms/{form_id}/results endpoint to fetch results, handling required parameters such as form_id, user_dir, limit, page, and sort direction. **Important**: If the connection's base_url doesn't include the user directory, you must provide the 'user_dir' parameter. Find this in your Formsite form URLs (e.g., if URL is https://fs8.formsite.com/user123/forms/abc, user_dir is 'user123') or in Settings -> Integrations -> Formsite API.
Input parameters
Page number if results exceed limit
Maximum number of results to get (1-500, API max is 500)
The form directory/ID to fetch results from
The user directory for your Formsite account. If not provided, it will be extracted from the base_url. You can find this in your form URLs (e.g., if your form URL contains '/vSkOfz/forms/', your user_dir is 'vSkOfz') or in Settings -> Integrations -> Formsite API.
Sort direction for results (asc or desc)
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
FORMSITE_GET_WEBHOOKSRetrieves all webhooks configured for a specific form in FormSite. This action returns webhook configurations including URL, event type (e.g., 'result_completed'), and optional handshake_key for security. Webhooks notify external URLs when form events occur. **Important**: If the connection's base_url doesn't include the user directory, you must provide the 'user_dir' parameter. Find this in your Formsite form URLs (e.g., if URL is https://fs8.formsite.com/user123/forms/abc, user_dir is 'user123') or in Settings -> Integrations -> Formsite API.
Input parameters
The form directory/ID to fetch webhooks from
The user directory for your Formsite account. If not provided, it will be extracted from the base_url. You can find this in your form URLs (e.g., if your form URL contains '/vSkOfz/forms/', your user_dir is 'vSkOfz') or in Settings -> Integrations -> Formsite API.
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
FORMSITE_LIST_ALL_FORMSRetrieves a list of all forms in the user's Formsite account. This action returns detailed information about each form including: - Form directory (identifier for accessing the form via API) - Form name (the display name of the form) - Description (optional internal description) - Publish information (embed code and public link) - State (open/closed status) - Statistics (file storage size and results count) The form directory returned by this action can be used with other Formsite actions like Get Form Details, Get Form Items, and Get Form Results. **Important**: If the connection's base_url doesn't include the user directory, you must provide the 'user_dir' parameter. Find this in your Formsite form URLs (e.g., if URL is https://fs8.formsite.com/user123/forms/abc, user_dir is 'user123') or in Settings -> Integrations -> Formsite API.
Input parameters
The user directory for your Formsite account. If not provided, it will be extracted from the base_url. You can find this in your form URLs (e.g., if your form URL contains '/vSkOfz/forms/', your user_dir is 'vSkOfz') or in Settings -> Integrations -> Formsite API.
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 31 agents privately built on Nagent that already use Formsite.
Build on Nagent
Connect Formsite 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 Formsite, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Formsite is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Formsite 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 Formsite 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 Formsite event fires, the agent kicks off automatically.
Every Formsite 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 Formsite ships with 5 pre-built forms & surveys actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Formsite together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Formsite-based workflows tailored to your business.