Skip to main content
Create automated workflows using a visual, drag-and-drop interface that connects triggers and actions. Build business process automation without any coding required.
Use to get AI-powered help building workflows, generating configurations, and troubleshooting automation.

​
Create your first workflow

1

Navigate to workflows

Open Workflows from your workspace sidebar and select a collection or create a new one
2

Create new workflow

Click Create Workflow and give it a descriptive name that explains what it accomplishes
3

Add a trigger

Select a trigger that defines what event will start your automation
4

Configure the trigger

Add filters to ensure the trigger only activates for relevant events
5

Add actions

Connect actions that perform the tasks you want to automate
6

Configure actions

Set up each action with the appropriate inputs and dynamic values
7

Test your workflow

Use manual triggers to verify each step works correctly
8

Publish workflow

Publish your workflow to make it active and ready to respond to triggers

​
Triggers

Every workflow needs exactly one trigger that defines what event will start the automation. Triggers respond to events in your workspace, external systems, or run on schedules. Common trigger types:
  • Ticket triggers - Activate when tickets are created or updated
  • Slack triggers - Respond to reactions or messages in Slack
  • Schedule triggers - Run workflows at specific times or intervals
  • Manual triggers - Start workflows on demand for testing or batch operations
Configure filters on triggers to control exactly when workflows activate, such as specific channels, ticket properties, or custom field values.
See all available triggers and actions with detailed configuration options

​
Actions

Actions perform tasks when your workflow is triggered. Connect multiple actions in sequence to create sophisticated automation that handles complex business processes. Common action types:
  • Ticket actions - Create, update, or manage tickets
  • Messaging actions - Send messages to Slack, email, or other channels
  • Integration actions - Create issues in Jira, Linear, or other tools
  • User management actions - Provision access in Okta or Google Workspace
  • Conditional logic - Branch workflow execution based on conditions
  • HTTP requests - Make custom API calls to external systems
Actions can use dynamic values to reference data from triggers or previous actions, creating intelligent automations that adapt to context.
See all available triggers and actions with detailed configuration options

​
Integration requirements

Some workflow actions require configured integrations to function. Actions that depend on third-party services show an indicator when the required integration is not configured. How actions requiring setup appear:
  • Actions show a Setup Required badge
  • Hover tooltips explain which integration is needed
  • You can select the action, but a banner will appear prompting you to configure the integration
To enable integration-dependent actions:
  1. Navigate to your workspace settings
  2. Connect the required integration following its setup guide
  3. Return to the workflow builder where the action will now be fully available
See the Integrations overview to explore available integrations and their setup guides

​
Converging branches

let you merge multiple parallel paths back into a single step. The converged step waits for all parent paths to finish before it runs. Use them when your workflow needs to branch out for parallel work and then rejoin for a shared next step, like sending notifications through multiple channels before updating a ticket.

​
Connect and disconnect steps

Open the connector menu on a step and drag a connection to the target step. Connect two or more steps to the same target to create converging paths.

Click on the line between two steps and click the delete button that appears to remove a connection.

You can only remove individual connections when a step has multiple parents. If a step has a single parent, delete the step itself to remove it from the workflow.

​
Execution behavior

Update ticket status waits for both Send Slack message and Create Jira issue to finish before it runs. What happens next depends on how those paths resolved:
Parent path resultsConverged step behavior
All parents completedExecutes using data from all paths
Some completed, some skippedExecutes using data from the completed paths only
All parents skippedSkipped
The workflow builder automatically prevents circular dependencies. You cannot create a connection that would cause a step to depend on itself, either directly or through a chain of other steps.

​
Data flow and dynamic values

Reference data from triggers or previous actions using dynamic values, creating intelligent automations that adapt to context.
Access information from the event that triggered your workflow.Available data:
  • Ticket properties (title, description, priority, status)
  • Requester information (name, email, user ID)
  • Custom field values
  • Timestamps and metadata
Example: Use ticket priority to determine which Slack channel receives notifications
Reference results from previous workflow actions.Available data:
  • Created ticket IDs
  • Jira or Linear issue keys
  • Okta user IDs
  • API response data
Example: Add a Jira issue link to the original ticket after creating it
Use the workflow builder’s dynamic value picker to insert references.Format: Click field input and select from available data sourcesAutomatic resolution: Values are resolved when the workflow runsValidation: The builder highlights invalid references before publishing

​
Testing workflows

Test workflows before publishing to verify they work correctly.
1

Use manual triggers

Manually trigger your workflow with test data
2

Check execution logs

View detailed logs showing what happened at each step
3

Verify outputs

Confirm each action produced the expected results
4

Test edge cases

Try different scenarios like missing fields or error conditions
5

Refine and iterate

Make adjustments based on test results
Draft workflows can be edited and tested but won’t execute automatically. Publish your workflow to make it active.

​
Templates

Start building workflows faster with pre-built templates. Templates provide ready-made automation structures for common IT operations that you can deploy and customize for your organization.

​
How templates work

Templates are pre-configured workflows that include triggers, actions, and connections. When you deploy a template, it creates a new workflow in your workspace that you can customize before activating.
1

Browse templates

When creating a new workflow, browse available templates filtered by tags or search by name.
2

Select and deploy

Choose a template and click Create Workflow. The template is copied to your workspace with a pre-filled name and description.
3

Configure inputs

Fill in the step-specific inputs for your organization, such as selecting an Okta application, choosing a Google group, or specifying a Slack channel.
4

Test and publish

Test the workflow to verify it works with your configuration, then publish to make it active.
Templates provide the workflow structure. After deployment, you can modify any step, add new actions, change the trigger, or restructure the workflow to fit your needs.

​
Customizing templates

After deploying a template, you have full control over the workflow:
  • Modify steps by changing action inputs, adding conditions, or updating configurations
  • Add new actions to extend the workflow with additional automation steps
  • Change the trigger to activate the workflow on different events
  • Remove steps that are not needed for your use case
  • Rename and describe the workflow to match your organization’s terminology
Templates are starting points. Customize them to match your specific processes and policies.

​
Best practices

Begin with linear workflows that handle one specific scenario. Add complexity gradually as you become more familiar with the system.
Give steps clear names that explain what they do. This makes workflows easier to understand and maintain, especially when multiple team members work with them.
Test with realistic data that represents actual conditions. Pay attention to edge cases and error conditions to ensure workflows handle unexpected situations gracefully.
Plan for failures by adding conditional logic that checks action results. Consider what should happen if external systems are unavailable.
Create separate workflows for distinct processes rather than one workflow that handles everything. This makes them easier to understand, debug, and maintain.
Add descriptions to workflows explaining their purpose and any special considerations. This helps team members understand what the automation does.