Extraction
Extract Open Tickets - Final
Extracted variables
- request_type
- key
- summary
- reporter
- assignee
- status
- created
- time_to_resolution
Procedure
All the moving parts, working as one.
Connect flows, decisions, approvals, and applications into one Procedure that completes the process from beginning to end.
How procedures work
Every part of the process, connected.
Combine flows, rules, approvals, and API calls to run the process from beginning to end.
Extraction
Pulls data from an app or page so later steps can use it.
Webhook
Starts the Procedure when another system sends a signal.
API
Calls an external service and can capture the response.
Rule logic
Chooses the next path based on conditions.
Execution
Runs a recorded flow in an app — the step that does the work.
Procedure
Nests another Procedure so you can reuse a whole sequence.
Slack
Posts a message in Slack using values from earlier steps.
Draft
A planning placeholder until you turn it into a real step.
AI
Runs a prompt with earlier values and returns generated text.
Summary
Turns earlier results into a short, readable digest.
Built for change
Adapt your procedures as your work evolves
Change individual steps, connect systems in new ways, and keep your processes moving without rebuilding everything from scratch.
Modular by design
Change one part, not the whole process.
Update, replace, or reuse individual parts of a Procedure while keeping everything else intact.
What you can change
Update a single part- Replace a card without rebuilding
- Add or remove a step
- Reuse a Procedure inside another
API Sandwich
Connect the steps your APIs can’t reach.
Use APIs or webhooks to start and finish a Procedure, while Stepwork coordinates the human work, decisions, and follow-ups in between.
What happens in between
- Start a Procedure from an API or webhook
- Assign tasks that require human input
- Keep approvals and decisions moving
- Send the completed outcome back to your systems
Grant access from a Jira ticket
Webhook
New Jira ticket created
issue_created · jira.atlassian.net
Output variables
- requester
- ticket_id
Extraction
Pull HR details from Rippling
Input variables
- requester
Extracted variables
- department
- job_title
- office
Execution
Grant access in Google Workspace
Input variables
- department
- job_title
- office
API
Create user in internal tool
Input variables
- requester
- job_title
- department
Output
- user_id
Procedure in practice
From request to completion
See how a Jira access request moves through four connected cards to retrieve the right details, grant access in Google Workspace, and create a user in an internal tool.