> 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/notionapps-workflow-how-to-guide.md).

# NotionApps Workflow How-To Guide

Redirect. Full trigger detail (what starts the run, **Where it happens**, and **Target**) is in the [Trigger catalog](https://docs.notionapps.com/automation/advanced-reference/trigger-catalog). Full **Add a step** detail (each tile, fields, what users see) is in the [Step catalog](https://docs.notionapps.com/automation/advanced-reference/step-catalog). Deep book: [Workflow Foundation User Guide](https://docs.notionapps.com/automation/workflow-foundation-user-guide).

In **Build**, every workflow has three trigger fields together:

1. **Trigger** — the kind of event (form save, button, Notion row, schedule, webhook, message).
2. **Where it happens** — Entire app, Screen, Button, Data source, Form, or Record.
3. **Target** — the exact screen, button, or sheet. Entire-app workflows leave this blank.

Then **Add a step**. Each tile is one action. Click the node and fill the inspector. Put Refresh / Show message / Open screen **before** Create, Notify, or Wait when the open tab must update. Typical writes: Create record (new row), Update record (this row), Notify (email), Call webhook and wait (Make, then refresh the same tab).

Typical bindings: form save → Screen + the form screen; one button → Button + that control; new Notion row → Data source + that database; webhook/schedule/manual → Entire app, no target.

#### Live screen updates (read this first if Approve or Make leaves the tab stale)

**Live screen updates** is an ops switch. It is off by default. NotionApps turns it on per app from Workflow Operations → Controls. It is not a builder toggle.

When it is **on**:

* `Update` / `Change status` / `Assign user` → `Refresh` → `Show message` updates the tab the user already has open. Approve-style buttons need no recipe change.
* **Call webhook and wait** POSTs Make, waits for a JSON **Webhook response**, then Refresh / Open screen can run on that same tab.
* Create, Wait, and fire-and-forget Notify stay background-only.

When it is **off**, Refresh after Update cannot update the open tab. That older sentence is still true until the switch is on.

Make that must refresh the open tab: use Call webhook and wait, not Notify webhook. Inbound webhooks Make fires at NotionApps still cannot refresh an already-open tab.

Details: [Step catalog](https://docs.notionapps.com/automation/advanced-reference/step-catalog), [Webhooks and Integrations](https://docs.notionapps.com/automation/webhooks-and-integrations), [Workflow Foundation User Guide](https://docs.notionapps.com/automation/workflow-foundation-user-guide).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/automation/notionapps-workflow-how-to-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.