Approvals & secrets

Sample documentation (demo only)
This is an incomplete, outdated docs snapshot shipped with the playground — screenshots were removed on purpose.
For the full, current manuals go to voodflow.com/docs.

Approvals

Approvals pause a run until a human decides. Use them when publishing, fulfilment, refunds, or any step must not continue automatically.

Typical pattern:

1. Trigger starts the workflow.
2. Data / integration nodes prepare context.
3. An approval node waits for an authorised user.
4. The branch continues (or stops) based on the decision.

Secrets

Secrets store credentials outside the canvas so authors do not paste tokens into node fields. Treat them like production credentials:

• Scope secrets to the environments that need them
• Rotate when people leave or vendors change
• Prefer referencing secrets from integration nodes instead of embedding values

Signals

Some flows use signals / webhooks so external systems or operators can resume a waiting run. Keep inbound endpoints authenticated according to your application standards.