A LITTLE DIRECTION GOES A LONG WAY

Find your path through the tools.

Four learning paths connect the guides into a useful order. Start with the problem in front of you, and follow the links as your workflow grows.

01 / FOUNDATIONS

Make your first tool contract

Start with inputs and outputs. Then define what counts as success, how errors are represented, and when a repeated action is safe.

  1. What Is a Tools API? A Practical Guide for Developers
  2. Structured Logs for Reliable Tool Runners
  3. JSON and CSV Exports: Design Data Other Tools Can Use

02 / BROWSER WORK

Build a readable browser flow

Connect meaningful navigation, stable selectors, and evidence capture. Keep the browser context explicit from the first step to the final artifact.

  1. Browser Automation and Selectors That Last
  2. Screenshot API Workflows: From Capture to Review
  3. HTML Parsing: Turn Pages into Structured Data

03 / EXECUTION

Make the workflow repeatable

Choose the execution surface, prepare a known state, and keep failures explainable. Expand the environment matrix only when it answers a useful question.

  1. Tool Runners and Test Flows: Build a Repeatable Workflow
  2. Mac and Windows Tools APIs: Choosing the Right Automation Layer
  3. iOS and Android Tools APIs: A Practical Mobile Automation Guide

04 / CONNECTIONS

Give the result somewhere to go

Understand event delivery, duplicate handling, data contracts, and formats. Design a handoff that another system can interpret without guessing.

  1. Webhooks and API Integrations: Design for Reliable Delivery
  2. JSON and CSV Exports: Design Data Other Tools Can Use
  3. Structured Logs for Reliable Tool Runners

MAKE THE NEXT STEP A GOOD ONE

Have a specific step in mind?

Browse the workflow library for focused checklists covering selectors, screenshots, logs, exports, and connections.

Explore workflows