> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/automation/automation-glossary.md).

# 📖 Automation Glossary

## Automation Glossary

### Automation Glossary

This glossary explains the words you will see in automation setup. Use it when a builder control or validation message feels technical.

#### Action

An action is something the app does. Examples are send a message, route a request, update a status, create work for a reviewer, or send data to another app.

#### Automation

Automation is the overall feature that makes the app do work after something happens. It is the bridge between a user action and the visible result.

#### Automation Launcher

Automation Launcher is a native screen type. Use it when users should intentionally start a process, such as Start onboarding, Request approval, Send to finance, or Escalate issue.

#### Conversation

Conversation is a native screen type for discussion around work. Use it when users need to ask questions, request clarification, or keep a message thread attached to the process.

#### Decision

Decision is a native screen type for reviewing one item and choosing an outcome. Use it when someone must approve, reject, request changes, escalate, or complete a review.

#### Destination

Destination means where the result appears. A destination can be a Decision screen, Work Queue, Conversation, Notification Center, Workflow Status screen, Linked App Exchange, webhook delivery, or another user-facing place.

#### Exception

An exception is a visible failure that needs attention. Examples include missing reviewer, missing required field, failed message delivery, permission problem, or webhook failure. Exception Resolution is the screen where makers and operators should diagnose and fix these problems.

#### Notification Center

Notification Center is a native screen type that shows alerts, reminders, announcements, or status updates. Use it when users need to be told something happened but do not need a full conversation.

#### Preflight

Preflight is the final readiness check before publishing or demoing. It should answer: can a real user start this, can the right person see it, can the maker diagnose it, and can failures be repaired?

#### Recipient

A recipient is the person, role, team, or field-selected user that receives work or a message. Use roles and teams when possible. Named people are harder to maintain when a customer adds or removes staff.

#### Repair

Repair is a guided fix for generated setup that is missing or disconnected. Repair is useful for reconnecting a generated screen, message route, approval route, or exception path. Repair is not a substitute for choosing the right business trigger, reviewer, status, or message.

#### Submit button

A submit button is the user-facing button that starts many workflows. It must be connected to the trigger. If the button only saves the record and the workflow listens for something else, the user will think automation is broken.

#### Trigger / When this happens

A trigger is the exact event that starts automation. The builder may label it When this happens. Examples are button click, form submission, status change, manual launcher action, incoming webhook, or scheduled event.

#### Validation

Validation checks whether the setup is connected. A blocker means do not publish. A warning means read the message, decide whether it matters, then test the visible result.

#### Work Queue

Work Queue is a native screen type for lists of work that need to be claimed, assigned, prioritized, or completed. Use it when a team handles multiple items, not just one reviewer making one decision.

#### Workflow

A workflow is the saved route. It connects the trigger to actions, recipients, messages, destinations, status updates, and exception handling.