...
Itential Platform Pricing Explore flexible plans and options for your team
Itential logo
Self-Service Infrastructure Operations

Itential Service Requests

Not everyone who needs automation should have to know how it works. Service Requests gives users a dedicated place to launch workflows and FlowAgents, schedule recurring operations, and track results. They see only the services they’re authorized to run, with no need to navigate workflow canvases, agent sessions, or Operations Manager.

One Place to Request & Track Automation

Make Infrastructure Automation Accessible to Everyone Who Needs It

Your engineers build the automation. Everyone else just needs a way to use it. Service Requests gives teams a self-service catalog of approved infrastructure operations, with simple forms to submit requests, flexible scheduling, and a complete view of what’s running and what’s finished. Whether a workflow or FlowAgent handles the execution, the experience stays the same.

Run Automation Without Learning the Platform

Give users a straightforward way to request infrastructure services without navigating Operations Manager, workflow canvases, or agent sessions.

Icon symbolizing a self-service catalog
One Catalog for Workflows & FlowAgents

Expose deterministic workflows and FlowAgents through the same request experience. Users choose what they need done, not how the automation runs.

Icon symbolizing a tool
Stop Building Custom Request Portals

Give teams a built-in interface for requesting automation without developing and maintaining a separate front end.

Icon symbolizing governance
Self-Service Without Unnecessary Access

Users see only the services they’re authorized to execute. Builders and administrators retain control over the automation behind every request.

Self-Service Catalog

Find the Right Service. Request It. Done.

Stop making users dig through automations and triggers just to run one operation. Service Requests presents available infrastructure services in a searchable catalog, organized around what users can request rather than how the automation was built.

Select a service, complete its request form, and submit. No workflow canvas, no execution configuration, and no platform expertise required.

Icon symbolizing validation
Only What You’re Authorized to Run

The catalog displays services based on existing execution permissions, so users only see the operations available to them.

Icon symbolizing finding
Find Services Faster

Browse available services, search by name, and return to recently used services without navigating through unrelated automations.

Forms Built for Requesting

Open a dedicated request form with the inputs required to launch the service. No need to find the right trigger or work through a technical execution interface.

On-Demand & Scheduled Execution

Run It Now. Or Put It on a Schedule.

Not every infrastructure operation needs to start immediately, and not every recurring task needs someone to launch it manually.

Service Requests lets users execute services on-demand or configure recurring schedules directly from the request form. Manage those schedules in the same workspace, without returning to Operations Manager to find and modify triggers.

Icon symbolizing closing the loop
Execute On-Demand

Submit a request and launch the underlying workflow or FlowAgent when the work needs to happen.

Icon symbolizing event-driven automation
Schedule Recurring Operations

Configure recurring execution for routine infrastructure tasks, with scheduling options for different operational requirements.

Icon symbolizing an ordered list
Manage Schedules in One Place

Review upcoming runs, edit schedules, pause or resume execution, and remove schedules that are no longer needed.

Request History & Status

Know What’s Running Without Opening the Automation

Submitting a request shouldn’t mean losing track of what happens next. Service Requests gives users a dedicated view of their request history, with execution status, submitted inputs, and results available from one place.

Whether a request completes successfully, encounters an error, or needs additional action, users can follow its progress without digging through job graphs or agent sessions.

icon showing a checkmark on lines of text or code
Track Every Request

See submitted requests, execution status, and the latest updates in a centralized history.

Review Inputs & Results

Open a request to see what was submitted and inspect its output once execution completes.

Icon symbolizing an end-to-end process
Repeat Without Starting Over

Relaunch previous requests with their original inputs already populated, making repeated operations faster and more consistent.

Built on the Itential Platform

Self-Service Access. Platform-Level Control.

Giving more people access to automation shouldn’t mean giving them access to change it.

Service Requests uses the Itential Platform’s existing execution permissions to determine which services each user can request. Every eligible manual trigger becomes an available service without rebuilding workflows, creating new entry points, or duplicating access configuration.

Builders continue designing workflows and FlowAgents. Administrators retain their operational tools. Users get a dedicated interface for requesting the services those teams make available.

icon showing connections between nodes
Existing Automation. No Rebuild Required.

Use existing manual triggers as services without recreating the underlying automation.

Icon symbolizing operations teams
Permissions Carry Through

Service visibility and execution follow the platform’s existing access controls, with dedicated permission to access Service Requests.

Icon symbolizing PSE
One Experience Across Execution Models

Workflows and FlowAgents are requested and tracked through the same interface, while execution remains governed by the Itential Platform.

Use Cases

Self-Service Infrastructure Operations, Without the Complexity

From routine network tasks to recurring infrastructure operations, Service Requests makes existing automation easier to consume across teams.

Icon symbolizing finding
Network Discovery On-Demand

An engineer needs updated network discovery data. They select Network Discovery from the service catalog, provide the required inputs, and track the result.

Icon symbolizing event-driven automation
Scheduled Configuration & Compliance Tasks

An operations team needs an approved configuration or policy task to run regularly. They submit the service with a recurring schedule, then manage future executions without modifying the underlying automation.

Icon symbolizing PSE
Infrastructure Provisioning Requests

A team needs a new infrastructure resource or service provisioned. They submit the required details through a request form, and the underlying workflow or FlowAgent handles execution. Any configured human approval checkpoints are handled through Work Center.

icon showing multiple silhouettes, symbolizing a team
Repeatable Operations Across Teams

Network, cloud, and security teams each access the services they’re authorized to run. Frequently used requests can be relaunched with their original inputs, reducing repetitive data entry without expanding access to automation configuration.

Itential for Operations Teams

Give infrastructure operations teams the tools to request, execute, and oversee automation without exposing the complexity behind every task. From self-service execution in Service Requests to human decisions in Work Center, Itential gives every role a purpose-built way to participate in infrastructure operations.

Keep Learning

Dive Deeper into Self-Service Infrastructure Operations

Get Started

Make Automation Available to Everyone Who Needs It

See how Service Requests gives teams a simple, governed way to launch workflows and FlowAgents, manage recurring operations, and track results without navigating the tools behind them.

Frequently Asked Questions

–+

Service Requests is a self-service application within the Itential Platform where authorized users can browse available infrastructure services, submit requests to execute workflows or FlowAgents, configure recurring schedules, and track execution results. It provides a dedicated experience for people who need automation to run without needing access to the tools used to build or manage it.

–+

Service Requests is designed for people who need to execute automation. Operations Manager is designed for administrators and technical users who manage and troubleshoot automation. Service Requests removes the need for end users to navigate workflow canvases, triggers, and execution details simply to run an approved service.

–+

Yes. Service Requests presents workflows and FlowAgents through the same service catalog and request experience. Users submit a request without needing to know which execution model handles the work.

–+

No. Service Requests uses existing manual triggers to expose available services. Customers do not need to recreate their workflows or configure a separate service for every automation.

–+

Users must have permission to access Service Requests and execute the underlying trigger. The catalog displays only services for which those permissions are satisfied. Access is managed through the Itential Platform’s existing permission model.

–+

Yes. Users can run a service immediately or configure recurring execution. Scheduled Requests provides a dedicated place to review and manage recurring requests, including editing, pausing, resuming, and deleting schedules.

–+

Yes. Service Requests maintains a history of submitted requests, including execution status, request inputs, and available results. Users can review the progress of their requests without opening Operations Manager or agent sessions.

–+

Service Requests is where users initiate and track automation. Work Center is where operators review and complete human tasks that arise during execution. If a workflow or FlowAgent requires human input, that task is handled through Work Center while the originating request remains trackable in Service Requests.

–+

No. Service Requests provides a built-in self-service experience for teams that need a way to launch Itential automation directly. Organizations already using ServiceNow or another request portal to invoke Itential automation can continue using their existing integrations.

–+

Service Requests is designed for both cloud and on-premises deployments of the Itential Platform. Availability depends on the applicable platform release.