How to Reference Pipeline Fields in a Web Form

Referencing custom pipeline fields in a web form allows you to collect specific information directly within the request workflow. See how to create and associate these fields with your form.

1st Step: Accessing the Pipeline and Opening Field Settings

1. In the left side menu, click “Pipelines” to open the list of pipelines.

2. Select the pipeline where you want to add the custom field.

3. Click “Module Settings” represented by the “(...)” icon in the upper right corner of the screen.

4. In the modal window, click the “Fields” tab.

2nd Step: Creating a Custom Field

1. Click “Add Custom Field”.

2. In the creation modal, fill in the following information:

• Label: field name/label (e.g., Category).
• Type: select the data type (Text, Number, Date, Dropdown,             etc.).
• Layout: choose “Single” or “Double” to define the width.
• Placeholder (optional): example text displayed inside the                field.
• Mask (optional): format pattern for automatic input                         formatting.
• Is the Field Required? (optional): enable if the field must be            filled in.
• Is the Field Read-Only? (optional): enable if it should be                 view-only.

    1. (Optional) In the “Visibility” tab, configure rules to define when         the field will be displayed.

    1. Click “Create Field” to finish.

3rd Step: Associating the Custom Field with the Web Form

1. In the side menu, go to Settings > Web Forms.

2. Locate the desired form and click it.

3. In the modal window:

• Click the “Fields” tab.
• Click “Add Custom Field” and select “Link to Pipeline                   Field”.     2. Adjust the order of fields by dragging them to the desired                    position. Changes are saved automatically.

4th Step: Publishing and Testing the Form

1. In the Web Forms list, click the form and then click “Open” to preview it in a new tab.

2. Copy the URL and open it in incognito mode for testing.

    1. Verify that the custom field appears and works as configured:

• Correct options
• Placeholder displayed
• Required validation applied

    1. Fill out and submit the form.

    1. In octapipe, confirm that the card created in the pipeline                    contains the value entered in the custom field.

Best Practices:

• Standardize field names to simplify maintenance.
• Test in incognito mode to validate field visibility.
• Review visibility rules to ensure they reflect the correct scenario.
• Document each custom field with its purpose and rules.
• Avoid duplication by checking if the field already exists before creating a new one.
• Update related workflows when modifying or removing fields.

Conclusion:

You have learned how to create a custom field in a pipeline and reference it in a web form, ensuring that information is captured and integrated into the workflow. If you have any questions, contact our support team.