​
Overview

Web Forms enable the creation and sharing of secure, interactive web pages designed to gather data, collect responses, share information, and trigger workflows based on user input. This feature combines dynamic, step-by-step functionality with robust support for static and interactive flows, empowering teams to implement versatile, user-friendly workflows efficiently. This feature empowers multiple SOC analysts to make simultaneous decisions efficiently, accelerating response times and more.

​
Web Form Types

Blink provides two distinct types of web forms:
  1. Single Step Web Forms- For standalone web forms
  2. Interactive Web Forms- A series of web forms
  • There are two different types of Interactive Web Forms
    1. New Interactive- The first web form initiates a new interactive session, which is used in subsequent workflow steps, including the use of at least one additional web form within that session.
    2. Existing Interactive- Creates a web form that can be used in an interactive web form session, initiated either by a previous Web Form step or a Web Form Trigger.
  • Both web forms can be triggered either via a static URL (using Web Form Event-Based Triggers) or dynamically within the workflow itself.

​
Action Types

Four key actions define the behavior of web form flows:
  1. Web Form Event Based Triggers- Creates static URL hosting a Web Form that invokes a workflow execution.
  2. New Web Form Action- Generates a web form during execution.
  3. Wait Action- The wait action pauses your workflow until a response is received from the web form. This ensures that the workflow continues only after receiving the required input.
  4. Set Interactive Web Form Status- Sends a status update to an interactive web form session (loading, success, timeout, or failure). You can customize the title and body of the status, if desired.

​
URL Query Parameters

In addition to accepting input values from users, input fields can be populated using URL query parameters. Query parameters are supported for the following input fields:
  1. Text
  2. Long text
  3. Number
  4. Checkbox (boolean)
  5. Single Select
  6. Multi Select- This input type allows you to pass multiple values by repeating the parameter name for each value, joined with an & symbol. For example: ?tags=urgent&tags=customer&tags=iam
  7. Date and/or time- Format is MM/DD/YYYY%20HH:MM (%20 represent a space in the url)
To populate the form’s input fields, the query parameter key must match the form input field. For example, if the field name give to a text input type is email, use ?email=johndoe@gmail.com in the URL. When the page is loaded, any query parameters that match input field names will automatically populate those fields URL Query Parameter Syntax
  1. ? – Indicates the start of the query string in a URL.
  2. = – Assigns a value to a key in a key-value pair.
  3. & – Separates multiple key-value pairs in the query string.
  4. % – Used to encode special characters in URLs (percent-encoding), e.g., a space becomes %20.

​
Use Case Example: Automating Security & IT Requests with Web forms

The following use case is a high-level example demonstrating how Web Form Actions can be used in a workflow. This example automates the process of submitting security and IT service requests through a structured web form. Once the user submits the form, a switch case step evaluates the selected request type. Depending on the choice, the workflow dynamically generates either a single web form or a series of web forms tailored to the specific request. By routing requests efficiently, it ensures streamlined processing, reduces manual effort, and improves response times.

​
Request Options:

When submitting a request, users can choose from the following categories:
  • Report an Issue (e.g., phishing email, security incident, unauthorized access)
  • Security Service Request (e.g., vendor security assessment, firewall configuration)
  • Self-Service Actions (e.g., password reset, account unlock, MFA reset)

​
How the Workflow Operates

1

Web Form Trigger (Start of Workflow)

  • A static web form serves as the entry point, capturing user input.
  • The web form flow type is set as ‘New Interactive’.
  • Users select the type of request they want to submit.
2

Switch Case Logic (Route Request Type)

  • The system evaluates the selected request type.
  • Based on the user’s choice, the workflow follows the appropriate branch.
3

Routing & Request Processing (Executing Actions)

  • Depending on the request type, the system dynamically generates an interactive follow-up web form (if additional details are needed).
  • The web forms are configured to continue an ‘Existing Interactive’ session and are configured to wait for the user’s response
  • The submitted information is then processed and routed to the appropriate ticketing system:
    • Jira (for issue reporting)
    • Zendesk (for general IT support)
    • Automated Actions (for self-service tasks like password resets)
4

User Feedback (Confirmation & Tracking)

  • The workflow sends a confirmation message to the user.
  • If applicable, a ticket ID is generated and shared with the user for tracking.
  • If an automated action was requested (e.g., a password reset), the user is notified once it is complete.