Form

The Form trigger turns a workflow into a form. Each submission runs the workflow once.

Build it

1. Add a Form trigger. A workflow with a Form trigger has no other trigger.
2. Under Fields, add the fields the visitor fills in. Each field is available to later blocks as <form.<field name>>.
3. Optionally end with a Form Reply block: its message is shown to the visitor after they submit. Without one, the visitor sees the trigger's Thank-you message (or is sent to its Redirect URL).
4. Before you deploy, click Deploy (it reads Versions once everything is deployed), open Execution settings, pick the environment and choose a service account under Run as. A Live URL always runs as that account, never as you, and a form without one cannot be deployed or promoted. The Test URL runs as that account too or, while none is chosen, as you. The Run as menu beside the toolbar's Run button changes only one manual run.

The Form trigger's other settings are Title, Description, Submit button, Redirect URL and Reply wait (seconds). The redirect URL must be https: a URL that is not https is ignored, and the visitor sees the thank-you message instead. The reply wait (0 to 60, default 30) is how long the page waits for a Form Reply before it shows the thank-you message. The run continues either way.

What a form's run can read and write

A form's runs follow the same rules as a chat's: see What visitors can read and write. Nothing a visitor submits is written into a knowledge base, memex or storage.

Test, go live, embed

The Test URL, Live URL, Allowed origins (the same rules and limits: at most 50 origins, 512 characters each), password and limits work as for the Chat trigger: a Test URL once the workflow is saved in an environment (a workflow that belongs to no environment gets no interface), a Live URL per promoted environment, and the iframe snippet in the trigger's panel once a Live URL exists. In an environment you cannot edit, such as production, the editor does not open: the workflow page's Share tab shows the Live URL, the iframe snippet and whether Interface on is set, and Monitor shows the Live URL on the workflow's trigger line, with a copy button. The hosted page is /form/<identifier>, for example https://app.example.com/agentic/form/<identifier> in subpath mode. A form has no launcher bubble, and its panel's Open test form opens the form in a new tab, as Open test chat does for a chat.

A form's Limits are Submissions per day, all visitors only (default 1,000; the allowance refills every 24 hours). A form keeps no conversations.

A password-protected interface needs https on both the embedding page and the Scrydon host. The sign-in cookie is SameSite=None; Partitioned, which browsers reject over plain http.

From your own UI

submitForm(values) in the interface client returns { status: "replied", message } when a Form Reply answered in time, otherwise { status: "submitted" }.

Troubleshooting

Form publications

Form publications were removed (see Upgrades). Recreate a published form as a workflow with a Form trigger.