When you’d need it
The question is not what components exist; it is who talks to whom, in what order, and what happens when the happy path fails. A sequence diagram makes time the organizing axis.
16:91 frame · sequence
Case study
Why this artifact is built the way it is
Key decisions
- Participants are named by role so the interaction stays readable outside engineering.
- The valid and invalid credential paths are both shown because auth flows need failure behavior.
- Activation bars make service responsibility visible without extra commentary.
When to copy vs. adapt
Use this for API flows, auth, checkout, webhook delivery, or any interaction where order matters. Use ERD when you need data structure instead.
Inside
What’s in this artifact
- 01Participants
- 02Requests
- 03Branches
- 04Failure path
Remix
Start with a variant
Same structure, your scenario — pick a starting prompt.
FAQ
Sequence questions
What is a sequence diagram example?
It shows how participants exchange messages over time, including calls, responses, and branches.
When should I use a sequence diagram?
Use it when order and interaction are the main story, such as APIs, auth flows, checkout, or event handling.
Can Toft include failure paths?
Yes. Include error cases or alternate paths in the prompt and Toft can add them to the diagram.
Make your own
Tools that build this.
Make your own sequence.
Describe what you need. Toft returns the finished, editable artifact.