How It Works
- Connect an application — Installable workflows appear after you connect an integration
- Browse available workflows — See what’s available for each connected app
- Install with one click — The workflow is added to your team
- Customize as needed — Adjust inputs, approvals, and logic for your use case
Finding Installable Workflows
From the Workflow Builder
When creating or editing a workflow, click Browse in the workflow builder to discover installable workflows you can add to your automation. This lets you find and incorporate pre-built templates without leaving the builder.From the Applications Page
- Navigate to Applications in the sidebar
- Select a connected application
- Click the Workflows tab to launch workflows directly from the application context — no need to leave the app
- Browse available installable workflows
From Suggestions
Serval’s AI analyzes your help desk activity and suggests relevant installable workflows. Review suggestions in:- Skills → Suggestions (top right)
- Workflows → Suggestions
Installing a Workflow
1
Select a workflow
Click on an installable workflow to see its description and what it does
2
Review the details
Check the inputs required and default approval settings
3
Click Install
The workflow is added to your team as a draft
4
Configure
Adjust settings:
- Name — Customize for your team
- Approvals — Change who needs to approve
- Inputs — Modify required information
- Execution scope — Set who can run it
5
Publish
Make the workflow available for execution
Example Workflows by Integration
Google Workspace
GitHub
Okta
Available workflows vary by integration. Connect an application to see its installable workflows.
Default Approval Settings
Installable workflows come with default approval configurations:
You can change the approval configuration after installing to match your security requirements.
Customizing After Installation
Installed workflows are fully editable. Common customizations:Add approval steps
Require manager or security team approval for sensitive operations
Modify inputs
Add, remove, or change the information users provide
Extend the logic
Add steps like Slack notifications or logging
Change execution scope
Make available to help desk or restrict to team members
Best Practices
Review before publishing
Check the workflow logic and ensure it matches your requirements
Add approvals for sensitive actions
User creation, deactivation, and access changes should require approval
Test with a real scenario
Run the workflow manually before making it available to help desk
Customize the name
Rename to match your team’s terminology and make it easier to find

