Start Node: Current Trigger Types

Choose a trigger

Add or select Start, then choose What triggers this workflow? The current selection screen contains exactly:

1. Trigger Manually
2. On Webhook Call
3. Schedule Trigger
4. On Email Received
5. Appsmith Integration (HTTP)

On Webhook Call and Appsmith Integration (HTTP) are Enterprise triggers. A workflow should have one entry configuration. Save the Start properties and then save the workflow.

Trigger Manually

Use this when a person should open and submit a workflow form or an authorised designer should start the workflow from Flow Builder.

The manual form configuration supports fields and their View order, followed by publishing controls:

• Who can open this form? — choose public or authenticated/private access according to the available option.
• App name, Logo URL, and Accent color — control the published form identity.
• Success message — text displayed after a successful submission.
• Redirect URL (optional) — destination after success.
• Share link — created or refreshed when Start properties are saved; copy it only after access has been reviewed.

Use Save Start Properties. If the form is private, only signed-in authorised users should receive its link.

On Webhook Call

Use this when an external service starts the workflow with an HTTP request.

1. Select On Webhook Call.
2. Configure the endpoint and the authentication/payload options shown in the panel.
3. Copy the generated endpoint from the UI rather than typing it from memory.
4. Save the Start properties and the workflow.
5. Send a controlled test request, then verify the instance in All Instances.

Treat endpoint URLs, tokens, API keys, and example payloads as integration credentials. The exact current endpoint displayed by the product is the source of truth.

Schedule Trigger

Use this when the platform should create instances automatically.

Configure Schedule Settings for timing and Execution Control for the available run limits or concurrency behavior. Check the timezone before saving. The workflow must be saved and Active for future executions to start.

After the first expected time, confirm that a new row appears in Applications → Workflow → All Instances.

On Email Received

Use this when an incoming message should start the workflow. Selecting it opens the same email-trigger settings used by the separate Email Trigger node.

Configure the mailbox, sender and subject rules, attachment requirements, and any additional Filters, Organization, Schedule, Rate limits, or Testing options available to your account. Save the workflow before starting the subscription. See Email Trigger.

Appsmith Integration (HTTP)

This is the current label shown in Flow Builder for HTTP integration with an App Builder page. Use the guidance inside the panel to connect the page action to the workflow endpoint and configure the expected request.

Keep the label Appsmith Integration (HTTP) in instructions while it remains the visible product label. It is not a separate workflow node; it is a Start trigger.

Trigger availability summary

Troubleshooting