Bot Fieldnotes
Bot Fieldnotes

THE WORKBOOK

Bot workflow examples: triggers, decisions and actions

Classify common automation claims without confusing a label with a capability.

By Onlytool · Published 10 September 2026

These are illustrative planning scenarios, not reports of vendor tests or customer outcomes. Adapt the examples to an account you are authorised to operate. Use the field guide for the underlying method and the interactive tool for your own inputs.

Download the worksheet

THE SITUATION

A dashboard labels a conversation

Software assigns an internal category for an operator to inspect.

Work through it

Map it as analysis if the output stays a label. If the label triggers another action, document that second workflow separately.

What to check

Check who can correct an inaccurate category and what downstream actions depend on it.

THE SITUATION

A tool suggests a reply

The software prepares text and the operator decides whether to send it.

Work through it

Map generation and approval separately. Inspect what context the suggestion used and whether the operator can edit or discard it.

What to check

A suggestion must not silently become an autonomous send when a setting changes.

THE SITUATION

An event launches a sequence

A qualifying event schedules one or more predetermined actions.

Work through it

Map the event, delays, duplicate policy and cancellation conditions. Confirm the source of the event.

What to check

A stopped or changed event must have a defined effect on pending actions.

YOUR WORKING DOCUMENT

Keep the decision
with the evidence.

Use the plain-text worksheet in your own approved system. It contains headings only, so you control which information is recorded and where it is stored. Nothing entered in a downloaded file is returned to this publication.

Save the blank worksheet ↓
WORKFLOW CLASSIFICATION
Product feature / action name:
Trigger event:
Information read:
Generates new text?
Decision rule:
Human approval point:
Action taken:
Downstream effects:
Pause / cancellation:
Correction owner:
Platform and account-authority check:
Questions still unverified:

Common mistakes to avoid

  1. Calling every scheduled message an AI conversation.
  2. Assuming “assistant” means that each action requires human approval.
  3. Using the classifier as a bot detector or a platform-permission checker.

Before implementing a workflow, confirm that it is supported by the chosen product and permitted under current platform rules. A planning example does not establish either. OnlyFans terms.

Classify a workflow