Collect approvals mid-flow
The node stores the current execution state in Google Cloud Storage and writes a pending approval record to Firestore. Supply a registered teammate's email to notify them automatically with a branded request, or leave it blank to share the approver page link yourself via chat or any other notification node.
Flexible expiration
Configure how long the request stays open (1–365 days, default 7). After the lifetime expires the stored state is cleaned up automatically and the approval can no longer be used.
Resume where you left off
When the callback URL is invoked with an approve or deny action the workflow resumes from the same point, passing the original value through to downstream nodes when approved. Denied requests emit an execution error event so you can notify the requester.
Shareable approval page
Every request includes a branded Hurozo approval page with the request details, expiration, and approve/deny buttons. Reviewers can open the link without signing in, leave a comment on denials, and their choice is recorded instantly.
Inbox in the toolbar
When you're signed in a bell icon appears in the app header with a badge showing how many approvals are waiting on you. New requests push through instantly via realtime updates, with an hourly background sweep as a safety net. Click the bell at any time to force a fresh fetch, opening a focused inbox that lists each pending request and launches the manual approval page in a new tab so you can review and respond quickly.