📱Native Automation Screens

Native Automation Screens

Native Automation Screens

Native automation screens make workflow activity visible. Without them, automation feels hidden: the maker may know something happened, but the user cannot find the work, status, message, or failure.

Use the actual screen type names from the builder. There are nine native automation screen types:

Screen type	Use it when
Work Queue	A team needs a list of work to claim, assign, prioritize, or complete.
Decision	A reviewer needs to approve, reject, request changes, or escalate one item.
Workflow Status	A requester or manager needs to see where a process stands.
Conversation	Users need to discuss a request or work item.
Exception Resolution	Makers or operators need to diagnose failed routes.
Notification Center	Users need alerts, reminders, or announcements.
Automation Launcher	Users need to intentionally start a process.
Linked App Exchange	Work or data needs to move between apps.
Operator Console	Makers or operators need a higher-level operating view.

Decision screen type in the builder.

Decision is the primary reviewer surface for approvals.

How to choose the right screen

Start with the user job, not the internal workflow object:

• If the user must decide, use Decision.

• If the user must pick work from a list, use Work Queue.

• If the user needs progress, use Workflow Status.

• If users need to talk, use Conversation.

• If users need alerts, use Notification Center.

• If a user should start a route intentionally, use Automation Launcher.

• If work crosses apps, use Linked App Exchange.

• If something failed, use Exception Resolution.

• If a maker needs operational oversight, use Operator Console.

Setup pattern

1. Add the screen from Add New Screen or the automation wizard.

2. Give the screen a plain business name.

3. Set the screen type to the correct native automation screen type.

4. Connect the workflow destination to that screen.

5. Set role access.

6. Show business fields, not internal IDs.

7. Preview as the role that will use the screen.

8. Start a real test route and confirm the item appears.

Important approval note

For approval use cases, combine Decision for reviewer action, Work Queue for shared team review, Workflow Status for requester progress, and Notification Center or Conversation for communication. Those are the screen names makers should search for in the builder.

Deep dives

• Decision and approval work queues

• Work Queues

• Conversations and Messages

• Notification Center

• Workflow Status

• Exception Resolution

• Automation Launcher and Linked App Exchange

• Automation Screens