Form Builder - Synthreo Pylon
Configure a DAG input form in Synthreo Pylon - add fields with labels and keys, choose validation, and test the submitted values before making the draft live.
What you’ll accomplish
Section titled “What you’ll accomplish”Add a structured input form to a Pylon DAG so users can supply fields before the workflow runs. The workflow reads each field’s Key.
What you’ll need
Section titled “What you’ll need”- A DAG you can edit in Pylon.
- The fields your workflow needs and a representative test submission.
- Familiarity with DAG variables.
1. Open the input-form designer
Section titled “1. Open the input-form designer”Open your DAG under Build → DAGs and select its Input Data node. In the configuration panel, find Input form and select Edit input form.
You’ll see the designer with Enable input form, Fields and Add field.
2. Enable the form and add fields
Section titled “2. Enable the form and add fields”Turn on Enable input form. When enabled, users see the form in chat instead of the message box.
Under Fields, select Add field. Set the field’s Label for the user and Key for the workflow. For example, use the label Customer name and key customer_name.
You’ll see the field definition with its label and key.
3. Choose field types and validation
Section titled “3. Choose field types and validation”Choose the type appropriate to the input:
| Type | Use |
|---|---|
| Text | Text input |
| Number | Numeric input |
| Date | Date input |
| Yes / No | A boolean choice |
| Dropdown | A selection |
| File upload | A file |
Where Validation is available, select None, Email, URL, Phone number, Date (YYYY-MM-DD), Alphanumeric (no special chars) or Custom regex. Selecting Custom regex reveals the Custom regex input.
You’ll see the chosen type and any applicable validation configuration.
4. Save and test the submitted values
Section titled “4. Save and test the submitted values”Apply your form edits and save the DAG draft. Run a representative submission with Run test. Open the test console and inspect Steps and the Input Data payload.
Use the field Key in the workflow and compare it with the actual submitted payload. For an output column exposed as customer_name, use {{customer_name}} in node configuration and {{Out.customer_name}} in a terminal Output Data template, following the Variable Syntax Reference. Confirm the payload shape before adding nested paths.
You’ll see the submitted field values in the trace and can verify that downstream nodes received what they need.
5. Make the tested draft live
Section titled “5. Make the tested draft live”When the saved draft behaves as intended, use the lifecycle control’s Make draft live action.
You’ll see the live revision in the header. Saving edits alone does not promote a draft.
If it didn’t work
Section titled “If it didn’t work”- The message box still appears: check Enable input form and which revision the host is using.
- A value is unexpected downstream: compare the field’s Key, the submitted payload and the consuming reference.
- Validation rejects the input: check the selected preset or custom expression with representative valid and invalid values.
Related
Section titled “Related”- Pylon user manual
- Test console reference
- Agent configuration - the separate autonomous Agent editor