Lesson 14 4 min
Wait for approval, even for days
Pause a run for a set time or until a person decides. In the extension, long waits survive closing the tab.
Wait
Wait pauses for Amount × Unit, then carries on with the same data.
- Under 1 minute: a simple timer; closing the tab cancels it.
- 1 minute or more, in the browser extension: the run is saved and resumes at the deadline, even after you close the tab or restart the browser. It shows as waiting in Executions and can last up to 30 days.
- In the web app: every wait is a simple timer, so a long wait doesn’t survive a closed tab.
Wait For Approval
Wait For Approval pauses until a person approves or rejects, then continues on the Approved or Rejected branch. It has no time limit, and the run is kept if you close the browser.
You’re told a run is waiting by a count in the top bar, a sound and, in the extension, a desktop notification. Answer on the paused run in Executions; in the extension, an Approve / Reject card can also appear on the page you’re looking at.
A typical use: Get All Text reads an article, a chain writes a short summary, and Wait For Approval asks you before it’s posted. From Approved, post it; from Rejected, show a notification.
Wait for the page, not the clock
To wait until something appears on a page, don’t guess a delay. Use Wait For Element: the run continues as soon as the page is ready.
Key takeaways
- In the extension, waits of a minute or more resume at the deadline, up to 30 days.
- Wait For Approval has two outputs, Approved and Rejected, and no time limit.
- Wait For Element waits for the page instead of guessing a delay.