Best practices

Use these best practices when building flows in WBA.

Design small, focused workflows

• Keep each workflow focused on one business outcome.
• Split complex logic into smaller reusable steps.
• Use clear names for workflows and steps so purpose is obvious.

Choose robust triggers

• Prefer event-driven triggers over frequent polling when possible.
• Validate trigger payloads before processing.
• Add guards to avoid duplicate starts for the same business event.

Build for retries and failures

• Assume external systems can fail or time out.
• Make steps idempotent so retries are safe.
• Add explicit error branches for known failure scenarios.
• Route failures to alerting channels and include enough context for troubleshooting.

Protect data and credentials

• Store secrets in approved secret storage, never directly in workflow logic.
• Minimize personal data in payloads and logs.
• Validate and sanitize inbound data before using it.

Keep integrations observable

• Add correlation IDs to follow one business event across systems.
• Log key state transitions, not every field.
• Track success rate, failure rate, and processing time for critical workflows.

Control performance and load

• Batch updates when large volumes are expected.
• Respect rate limits in external APIs.
• Use queues or asynchronous patterns for long-running work.