Getform is a modern form backend platform that enables developers to handle web forms and submissions without setting up a server or writing backend code.
Getform is a modern form backend platform that enables developers to handle web forms and submissions without setting up a server or writing backend code. On Nagent, Getform is exposed as a fully-configurable forms & surveys integration that any agent can call — 2 actions, and API key authentication. No code is required to wire Getform into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Getform 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 Getform 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 Getform, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GETFORM_GET_FORM_GET_SUBMISSIONRetrieve a specific form submission by its ID from Getform. Use this tool when you have both a form_id and submission_id and need to fetch the details of that single submission. The response includes all form field values submitted by the user, plus metadata like submission date and any uploaded files. Note: The Getform API does not have a dedicated single-submission endpoint, so this action fetches all submissions and filters by ID. For forms with many submissions, consider using get_submissions with pagination if you need to process multiple records. Prerequisites: - A valid Getform API token that corresponds to the specified form_id - The submission_id must exist for the given form
Input parameters
The unique identifier of the Getform form. This is the alphanumeric ID visible in your Getform dashboard URL (e.g., 'bkknozrb'). The API token must be valid for this specific form.
The numeric ID of the submission to retrieve. You can obtain this ID from the get_submissions action or from the Getform dashboard.
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
GETFORM_GET_FORM_SUBMIT_FORMTool to submit form data and files to a Getform endpoint. Use when you need to post fields, files, optional reCAPTCHA or honeypot to a specific form ID.
Input parameters
Key/value pairs representing form fields to submit.
Optional list of files to upload; will be posted as multipart/form-data
Honeypot field value; leave empty (spam filter).
Identifier of the Getform form endpoint (as in /f/{form_id})
Whether to set Accept header to application/json for a JSON response instead of redirect
reCAPTCHA token for spam protection (if enabled on the form).
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 36 agents privately built on Nagent that already use Getform.
Build on Nagent
Connect Getform 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 Getform, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Getform is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Getform 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 Getform 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 Getform event fires, the agent kicks off automatically.
Every Getform 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 Getform ships with 2 pre-built forms & surveys actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Getform together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Getform-based workflows tailored to your business.