> 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/advanced-reference.md).

# Advanced Reference

## Advanced Reference

### Advanced Reference

Use this section after you understand the normal wizard path. Advanced automation is for multi-step workflows, integrations, exception operations, launch monitoring, and customer handoff.

#### Advanced topics

* Multi-role approval chains
* Queue assignment and reassignment
* Conditional routing by amount, department, priority, or region
* Conversation-based clarification
* External webhook delivery
* Linked app handoff
* Exception retry and repair
* Post-launch monitoring

#### Rule for advanced setups

Every advanced setup still needs simple visible proof. If the process becomes more complex, add more status, messages, and exception visibility. Do not make the maker inspect hidden records to explain whether the workflow worked.

#### Recommended next page

Read Operations After Launch when the app is already published or close to customer handoff.When to use advanced objects

Most makers should begin with the guided builders. Advanced objects are useful when the app needs behavior that goes beyond a single guided recipe.

Use advanced workflow settings when you need:

* More than one route after the same event.
* Conditional branches by amount, status, region, priority, or role.
* A retry or escalation path after a timeout.
* External webhook delivery or payload mapping.
* A technical payload path that must be inspected or adjusted.

Use advanced messaging settings when you need:

* A specific channel and topic naming pattern.
* A route shared by multiple screens.
* A direct conversation tied to a record or workflow run.
* Announcement delivery separate from private conversation delivery.
* Troubleshooting visibility in Messaging Operations.

Use advanced approval settings when you need:

* Multi-level approvals.
* Claim-before-action queues.
* Approval rules that depend on submitted data.
* Separate requester, reviewer, and operations screens.

Even with advanced objects, the maker-facing goal stays the same: make the route explain itself in business language, then prove it with a visible test.

### When to use advanced objects

Most makers should begin with the guided builders. Advanced objects are useful when the app needs behavior that goes beyond a single guided recipe.

Use advanced workflow settings when you need:

* More than one route after the same event.
* Conditional branches by amount, status, region, priority, or role.
* A retry or escalation path after a timeout.
* External webhook delivery or payload mapping.
* A technical payload path that must be inspected or adjusted.

Use advanced messaging settings when you need:

* A specific channel and topic naming pattern.
* A route shared by multiple screens.
* A direct conversation tied to a record or workflow run.
* Announcement delivery separate from private conversation delivery.
* Troubleshooting visibility in Messaging Operations.

Use advanced approval settings when you need:

* Multi-level approvals.
* Claim-before-action queues.
* Approval rules that depend on submitted data.
* Separate requester, reviewer, and operations screens.

Even with advanced objects, the maker-facing goal stays the same: make the route explain itself in business language, then prove it with a visible test.