28 Aug 2026 Release
Live screen updates after Update and Call webhook and wait, so Approve and wait-for-Make buttons can refresh the already-open tab. Off by default. NotionApps turns the switch on per app.
What’s new at a glance
Live screen updates
When NotionApps turns this on for your app, Update → Refresh → Show message updates the tab the user already has open
Call webhook and wait
POST Make, wait for a JSON Webhook response, then Refresh / Open screen / Show message on the same tab
Approve can refresh the open tab.
Make can return JSON, then the same tab updates.
Notify webhook stays fire-and-forget.
The switch is off until NotionApps turns it on.Start here
Approve-style buttons: keep Update (or Change status / Assign user) → Refresh → Show message. No recipe change once live screen updates are on. Make-then-refresh: use Call webhook and wait, not Notify webhook. Make must end with Webhook response JSON.
Features
1. Live screen updates after Update
Until now, Update, Change status, and Assign user ran in the background. Refresh and Show message after those steps could not update the tab the user already had open.
When Live screen updates is on for an app:
Update, Change status, and Assign user can run during the original button tap
Later Refresh / Open screen / Show message reach that same tab
The background worker skips an Update that already succeeded, so the record is not written twice
Create record, Wait, and fire-and-forget Notify stay background-only
This is an ops kill switch, not a builder toggle and not an entitlement. Default is off. NotionApps sets it globally or per app under Workflow Operations → Controls. The app override wins when set; otherwise the app inherits the global value.
The Call webhook and wait tile is visible in the builder either way. Placement warnings follow the switch: Refresh after Update only warns when the switch is off.
2. Call webhook and wait
Use this step when a button must call Make (or another webhook), then Refresh or Open screen on the same open tab. It is not the fire-and-forget Notify webhook.
Maker setup:
Paste the Make webhook URL
Leave the sync timeout at 8000 ms unless you need a shorter wait (max 12 seconds on the tap)
In Make, end with Webhook response and return JSON, for example
{ "ok": true, "cart_record_id": "…" }Map a later Open screen record id to
context.<this_step_id>.cart_record_idwhen Make returns one
What the user sees:
Make answers within 8 seconds: Refresh / Open screen / Show message run on the open tab
Make is still going: the app shows Working… and polls the run for 45 seconds
Still pending after that: “This is taking longer. Refresh to see the cart.”
4xx / 5xx in the 8-second window: error, no refresh, no retry
Inbound webhooks Make fires back at NotionApps still cannot refresh an already-open tab. Use Call webhook and wait when the open tab must update.
What makers need to change
Approve-style Button → Update / Change status / Assign → Refresh → Show message
None
Call Make, then refresh the open tab
Yes — use Call webhook and wait. Make must return JSON via Webhook response
Documentation for this release
Availability notes
Off by default. NotionApps turns Live screen updates on for an app (or globally) from Workflow Operations → Controls
Not a maker toggle. Not an entitlement. Permission to change the switch is
admin.workflows.manageCall webhook and wait is always visible in the builder; Refresh after it only updates the open tab when the switch is on
Create, Wait, and Notify webhook stay background-only
Inbound Make → NotionApps webhooks still cannot refresh an already-open tab