Introduction
Ingress forms — the intelligent form platform for teams
Build production-grade forms, automate approvals with visual workflows, and collect data securely across your organization.
Ingress forms pairs a drag-and-drop form builder with a visual workflow engine, real-time analytics, and enterprise-grade access controls. It runs wherever you do — as a managed cloud service or self-hosted on your own infrastructure.
Features
- AI-generated forms — describe what you want in plain English, get a production schema back.
- Visual workflows — chain triggers, approvals, and integrations without writing code.
- Real-time analytics — submission trends, completion rates, and workflow health at a glance.
- Enterprise security — SSO, SCIM, role-based access, audit log, and full SOC 2 compliance.
- Custom domains — serve public forms from your own hostname with automated TLS.
- Open API — a clean REST surface plus webhooks to plug Ingress forms into your stack.
Installation
The managed app is available at app.ingressforms.com. For the self-hosted CLI and SDK, install from npm:
# install the CLI
pnpm add -g @ingress/forms-cli
# scaffold a new project
ingress-forms init my-team
cd my-team
ingress-forms devIf you're integrating with an existing Node service, install the SDK:
pnpm add @ingress/forms-sdkA minimal example
This snippet submits a form response programmatically using the server SDK.
import { IngressForms } from "@ingress/forms-sdk";
const client = new IngressForms({ apiKey: process.env.INGRESS_FORMS_API_KEY });
const submission = await client.submissions.create({
formId: "frm_01HABCDXYZ",
data: {
email: "alex@acme.com",
rating: 5,
feedback: "Loving the new workflow builder.",
},
});
console.log(submission.id);How it fits together
At its core, Ingress forms is three loosely coupled systems: a form renderer, a submission store, and a workflow executor. Each one is replaceable, which is why the product works equally well as a hosted SaaS or a self-contained appliance.
The forms service owns schemas and drafts. The submissions service owns responses, files, and search. The workflows service runs triggers — on submission, on a schedule, or on an external webhook — and orchestrates your approvals, notifications, and integrations.