Portal Community
What This Node Does The Form Trigger is a two-phase node. In Phase 1, BizFirstAI renders a hosted form page from your configured form schema and presents it to the assigned user via a URL link or an embedded portal task. The workflow waits in a suspended state. In Phase 2, when the user fills in the form and clicks submit, the workflow resumes with all submitted field values available as structured data for downstream processing. This pattern eliminates the need for separate form-building tools and keeps the entire intake-to-action pipeline within BizFirstAI.

Two-Phase Execution Model

Phase 1 — Form Presentation

Workflow starts, Form Trigger node generates a secure, hosted form URL and presents it to the assigned user. Workflow suspends and waits.

Phase 2 — Form Submission

User fills in the form and submits. Workflow resumes with all form field values as structured output data for downstream nodes.

Key Capabilities

Business Benefits

Structured Data Collection

Every submission arrives as validated, structured JSON — no more manual parsing of email requests, ambiguous notes, or incomplete information. Downstream systems receive clean data every time.

No External Tools Needed

Replace Google Forms, Microsoft Forms, or Typeform for business process intake. The form lives inside BizFirstAI, connected directly to the automation — no middleware, no data copy-paste.

Asynchronous Human-in-the-Loop

Workflows can pause for days waiting for a form submission. The system tracks outstanding forms, sends reminders, and escalates if a form is not completed before the deadline — all automatically.

Secure and Auditable

Every form submission is tied to an authenticated user identity and timestamped. The full submission history is stored in the execution log, providing a complete audit trail for compliance.

Use Cases

Employee Leave Request

An employee submits a leave request through a BizFirstAI-generated form embedded in the HR portal. The form collects leave type, start/end dates, and a description. On submission, the workflow routes the request to the employee's manager for approval, checks leave balance, and updates the HR system.

Customer Onboarding Intake

A salesperson sends a new customer a secure form link for onboarding intake. The form collects business name, contact details, service tier selection, billing information, and compliance declarations. On submission, the workflow creates accounts in CRM, billing, and the provisioning system simultaneously.

Support Ticket Submission

A support intake form is embedded on the company's customer portal. Customers fill in the issue description, severity, product area, and attach a screenshot. On submission, BizFirstAI creates a ticket in Jira, assigns it to the correct team based on product area, and sends the customer a confirmation with a ticket number.

Purchase Request Initiation

Employees fill in a purchase request form (vendor, items, justification, budget code) via a link in the company intranet. BizFirstAI validates the budget code against the finance system, routes for manager approval, and — if approved — generates a purchase order in the ERP automatically.

HR Change Request

A manager submits a personnel change form (salary adjustment, role change, department transfer) via a secure URL sent by the HR team. The form enforces required fields and validates effective dates. On submission, the change workflow initiates the approvals chain, IT provisioning updates, and payroll adjustments.

In This Guide

Configuration

Define the form schema, title, description, assignment, expiry, and submission behavior. Full property reference with field type examples.

Input & Output

The form submission data structure available downstream, including all field values, submitter identity, and file attachment URLs.

Examples

Leave requests, customer onboarding, support intake, and purchase approvals — complete configurations with form schemas.