Formcarry is a form API that allows you to collect submissions from your own designed HTML forms without coding any backend, providing features like email notifications, file uploads, spam protection, and integrations with other apps.
Formcarry is a form API that allows you to collect submissions from your own designed HTML forms without coding any backend, providing features like email notifications, file uploads, spam protection, and integrations with other apps. On Nagent, Formcarry is exposed as a fully-configurable forms & surveys integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Formcarry into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Formcarry 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 Formcarry 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 Formcarry, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FORMCARRY_CREATE_FORMCreate a new form with customizable settings including email notifications, webhooks, and thank you pages. This action creates a Formcarry form with extensive configuration options for email notifications (both to form owners and respondents), webhook integrations, Google Recaptcha spam protection, and customizable thank you pages. Use when you need to programmatically set up a new form with specific notification rules or integrations.
Input parameters
Name of the form. This is the identifier you'll use to recognize the form in your Formcarry dashboard.
Email addresses for self respondent notifications. Separate multiple addresses with comma (e.g., 'admin@example.com,support@example.com').
Failed page URL to redirect users after failed submission. Required if returnUrl is present.
Webhook URL. Formcarry will send a POST request to this URL when a new submission is received.
Save incoming submissions to formcarry database. Default is true. Set to false if you only want to forward submissions via webhook.
Thank you page URL to redirect users after successful submission. If provided, failUrl is also required.
Enable auto-response email notifications to be sent to form respondents. This sends a confirmation email to the person who submitted the form.
Enable sending form message in query string to Return URL. When enabled, form data will be passed as query parameters.
HTML email template code if selfEmail_theme is Custom. Supports Dynamic Tags for inserting submission data.
From email address for self email notifications sent to form owner.
Google Recaptcha secret key to enable Google Recaptcha spam protection on the form.
Email template theme options.
HTML code for Custom theme respondent auto-response email. Supports Dynamic Tags for personalization.
From email address for respondent auto-response notifications.
Subject line of self email notifications sent to form owner.
Display mode for the thank you page.
Email template theme options.
Theme options for the built-in thank you page.
Message content for Fancy or Formal theme respondent auto-response emails.
Subject line of respondent auto-response email notification.
Send email notifications for submissions marked as spam. Default is false. Enable only if you want to review spam submissions.
Message text displayed on the thank you page below the headline.
The headline text displayed at the top of the thank you page.
URL to redirect when user clicks the primary button on the thank you page.
Text displayed on the primary button of the thank you page. Defaults to 'Return' if not specified.
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
FORMCARRY_DELETE_FORMDelete an existing form by its Form ID. Use when you need to permanently remove a form from your Formcarry account.
Input parameters
The unique identifier of the form to delete. You can find this in your Formcarry dashboard or by listing forms via the 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
FORMCARRY_RETRIEVE_SUBMISSIONSRetrieves all submissions for a specific Formcarry form. Returns a paginated list of form submissions with their field data, timestamps, and submission IDs. Use pagination parameters to navigate through large submission sets. Default page size is 25, maximum is 50 submissions per page. Useful for: collecting form responses, exporting submission data, integrating form data into other systems, or building custom analytics dashboards.
Input parameters
Page number for pagination. Starts from 1.
Number of submissions per page. Default is 25, Max is 50.
The unique identifier of the form whose submissions you want to retrieve. You can find this in your Formcarry dashboard or by listing forms via the 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
FORMCARRY_VERIFY_AUTHTool to verify API key authentication with Formcarry. Use this endpoint to check if your API key is valid before making other API requests. Returns success status and a confirmation message if the API key is valid.
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 51 agents privately built on Nagent that already use Formcarry.
Build on Nagent
Connect Formcarry 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 Formcarry, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Formcarry is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Formcarry is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Formcarry 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 Formcarry event fires, the agent kicks off automatically.
Every Formcarry 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 Formcarry ships with 4 pre-built forms & surveys actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Formcarry together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Formcarry-based workflows tailored to your business.