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.
Blink provides two distinct types of web forms:
There are two different types of Interactive Web Forms
Both web forms can be triggered either via a static URL (using Web Form Event-Based Triggers) or dynamically within the workflow itself.
Four key actions define the behavior of web form flows:
Web Form Event Based Triggers- Creates static URL hosting a Web Form that invokes a workflow execution.
New Web Form Action- Generates a web form during execution.
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.
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.
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:
&
symbol. For example:
?tags=urgent&tags=customer&tags=iam
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
?
– Indicates the start of the query string in a URL.=
– Assigns a value to a key in a key-value pair.&
– Separates multiple key-value pairs in the query string.%
– Used to encode special characters in URLs (percent-encoding), e.g., a space becomes %20
.URL Query Parameters Examples
If a web form has a short text field with the name “email” and a checkbox field with the name “subscribe”; the page URL: https://your-tenant.blinkops.com/forms/trigger/123e4567-e89b-12d3-a456-426614174000?email=ash@gmail.com&subscribe=true
When visited, this will populate the email field with the input ash@gmail.com
and check the subscribe checkbox.
If a web form has a number input field with the name “quantity” and a multi-select option field with the name “tags” and values “urgent”, “internal”, “customer”; the page URL: https://your-tenant.blinkops.com/forms/trigger/123e4567-e89b-12d3-a456-426614174000?quantity=3&tags=urgent&tags=customer
When visited, this will populate the quantity field with the number 3 and select both “urgent” and “customer” options in the tags field.
your-tenant.blinkops.com
This is a placeholder for your actual Blink tenant URL. Replace your-tenant
with your own organization’s tenant subdomain.
/forms/trigger/{form_id}
The long string after /trigger/
(123e4567-e89b-12d3-a456-426614174000
) is the Form Trigger ID.
This unique identifier is automatically generated by Blink when you publish a web form, and it’s used to route the submission to the correct workflow.
Query parameters (e.g. email=ash@gmail.com
, tags=urgent
)
These are optional values that get passed into the form when it’s triggered. They populate the dynamic fields defined in the form.
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.
When submitting a request, users can choose from the following categories:
Web Form Trigger (Start of Workflow)
Switch Case Logic (Route Request Type)
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:
User Feedback (Confirmation & Tracking)
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.
Blink provides two distinct types of web forms:
There are two different types of Interactive Web Forms
Both web forms can be triggered either via a static URL (using Web Form Event-Based Triggers) or dynamically within the workflow itself.
Four key actions define the behavior of web form flows:
Web Form Event Based Triggers- Creates static URL hosting a Web Form that invokes a workflow execution.
New Web Form Action- Generates a web form during execution.
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.
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.
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:
&
symbol. For example:
?tags=urgent&tags=customer&tags=iam
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
?
– Indicates the start of the query string in a URL.=
– Assigns a value to a key in a key-value pair.&
– Separates multiple key-value pairs in the query string.%
– Used to encode special characters in URLs (percent-encoding), e.g., a space becomes %20
.URL Query Parameters Examples
If a web form has a short text field with the name “email” and a checkbox field with the name “subscribe”; the page URL: https://your-tenant.blinkops.com/forms/trigger/123e4567-e89b-12d3-a456-426614174000?email=ash@gmail.com&subscribe=true
When visited, this will populate the email field with the input ash@gmail.com
and check the subscribe checkbox.
If a web form has a number input field with the name “quantity” and a multi-select option field with the name “tags” and values “urgent”, “internal”, “customer”; the page URL: https://your-tenant.blinkops.com/forms/trigger/123e4567-e89b-12d3-a456-426614174000?quantity=3&tags=urgent&tags=customer
When visited, this will populate the quantity field with the number 3 and select both “urgent” and “customer” options in the tags field.
your-tenant.blinkops.com
This is a placeholder for your actual Blink tenant URL. Replace your-tenant
with your own organization’s tenant subdomain.
/forms/trigger/{form_id}
The long string after /trigger/
(123e4567-e89b-12d3-a456-426614174000
) is the Form Trigger ID.
This unique identifier is automatically generated by Blink when you publish a web form, and it’s used to route the submission to the correct workflow.
Query parameters (e.g. email=ash@gmail.com
, tags=urgent
)
These are optional values that get passed into the form when it’s triggered. They populate the dynamic fields defined in the form.
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.
When submitting a request, users can choose from the following categories:
Web Form Trigger (Start of Workflow)
Switch Case Logic (Route Request Type)
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:
User Feedback (Confirmation & Tracking)