Form Actions & Scenarios

What is this for?

This guide explains what happens when someone submits your form — the built-in actions (save, email, webhook) and how to attach custom automation scenarios using journeys.

Built-In Form Actions

Every form has a Submit button at the bottom. Clicking the gear icon on the button lets you change its label and style. The button always performs these actions:

Validate — Checks all required fields. Shows inline errors if any are empty.
Save Submission — Stores the attendee's answers in the system.
Identify Subscriber — Uses the Email field (marked as "subscriber identifier") to create or update the subscriber record.
Trigger Webhook — If an Integration URL is set, sends a POST request with the submission data.
Run Journey Actions (Event type only) — If a journey is attached, starts the journey's automation (emails, session assignments, etc.).

Note: The Submit button's "Enable Validation" toggle is currently reserved for future use. Validation always runs.

What You Can Attach to a Form

1. Journey (Event Type Only)

A Journey is a visual automation builder that defines what happens after registration. Attach a journey in the Journey step of the sidebar.

Typical journey actions:

Send confirmation email — Immediate or scheduled.
Assign to session/track — Based on form answers (e.g., "Beginner" track if they select "New to topic").
Wait steps — Delay next action by hours/days.
Conditional branches — Different paths based on field values.
Add tags — Tag subscribers for segmentation.
Web requests — Call external services.
Stop/Finish — End the journey.

Journeys are built in the separate Journey Editor. The Event Constructor only lets you select which journey to attach.

2. Integration Webhook (Both Types)

Set a URL in the Integration step. On submit, a POST request is sent with:

{
  "eventId": "abc123",
  "subscriberId": "sub456",
  "fields": {
    "email": "john@example.com",
    "name": "John Doe",
    "company": "Acme Corp"
  },
  "submittedAt": "2026-07-20T10:30:00Z"
}

Use this to sync with CRM, marketing tools, or custom backends.

3. Email Notification on Activation/Stop

When you activate or stop the event, you can optionally send a one-time email to all current subscribers. Configure subject, body, and template in the activation/stop popup.

Scenario: Event with Journey (Typical Flow)

Attendee fills form → clicks Submit.
System validates → saves → identifies subscriber.
Journey starts:
- Step 1: Send "Registration Confirmed" email immediately.
- Step 2: Wait 1 day.
- Step 3: If "Interested in Workshop" = Yes → Send workshop details email.
- Step 4: If "Interested in Workshop" = No → Send main agenda email.
- Step 5: 3 days before event → Send reminder email with calendar link.
- Step 6: Event day → Send "Starting soon" notification.

Scenario: Custom Form (Simple Lead Capture)

Visitor fills form → clicks Submit.
System validates → saves → identifies subscriber.
Webhook fires → your CRM creates/updates lead.
(Optional) Journey not available for Custom Form type.
You export leads later or use the webhook for real-time sync.

Action Buttons in the Form

The form always has one primary Submit button. You can:

Change the label (default: "Subscribe").
Change background color and width via the button's settings (gear icon).
Add additional buttons — currently only one Submit button is supported.

Future: Multiple action buttons (e.g., "Save Draft", "Submit & Pay") are planned.

Validation Behavior

Client-side: Required fields show red border and message immediately on blur.
Server-side: On submit, all required fields re-validated. Duplicate email handling depends on journey logic.
Spam protection: Activation email content is scanned for blocked words. Rejected if detected.

Common Questions

Can I run a journey without a form?
No. Journeys are triggered by form submissions in the Event Constructor.

What if the webhook fails?
The form submission still succeeds. The integration runs in the background. Check your web service records for failures.

Can I attach multiple journeys?
Only one journey per event. Use conditional branches inside the journey for different paths.

How do I test the form before going live?
Click Preview in the toolbar. The preview page is fully functional — submissions go to a test environment and don't count toward limits.

What happens to submissions if I stop the event?
Submissions stay in the system. The form just stops accepting new ones. You can export all data anytime.

Can I redirect after submit?
Not currently configurable. The form shows a success message on the same page. Custom redirects are planned.

Documentation