Webhook
New Jira ticket created
issue_created · jira.atlassian.net
Output variables
- requester
- ticket_id
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.
Grant access from a Jira ticket
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
Drag to explore · pinch to zoom
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.
How procedures work
Every part of the process, connected.
Combine flows, rules, approvals, and API calls to run the process from beginning to end.
Webhook
Starts the Procedure when another system sends a signal, and it has to sit first in the chain. Use it when a new ticket, form submit, or outside event should kick off the rest of the steps so nobody has to press Run each time.
- New ticket
- Form submitted
- Employee update
And more building blocks
Sketch a step for later, nest a Procedure you already trust, shape text with AI, and turn finished runs into a short digest.
Procedure
Runs another Procedure as a single step inside this one. Use it when a sequence you already trust should repeat inside a larger process, so you reuse the whole chain instead of rebuilding the same cards again.
AI
Sends values from earlier steps into a prompt and returns text you can use next. Reach for it when you need a short write-up, a classification, or a cleaned message before Slack, a rule, or another card continues.
Draft
Holds a planned step before it is a real card. Drop it in while you are still sketching the process, name what should happen later, then turn it into Extraction, Execution, or another type when you are ready to build it.
Summary
Turns results from Procedure runs into a short readable digest. Use it when people need the outcome of many steps in plain language, without opening every card or replaying the full history.
Extractions
Data from any app, ready for the next step.
Highlight a table once. Each run follows its pages, cleans it up, and hands the rows to the steps that follow.
Tables, lists, and documents- Up to 100 pages, joined into one table
- Cleaned up in plain words
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