BraiFlow CRM

Product Documentation

Operational documentation to run the platform in production: onboarding, business processes, governance and execution standards.

Automations

Workflow builder and execution lifecycle.

Target Audience

Operations teams building workflow automations with guardrails.

Prerequisites

  • Workflow permissions enabled for target roles.
  • At least one active trigger source available.
  • Execution mode policy (simulate vs execute) decided.

Module Positioning

No-code workflow engine to standardize cross-module execution.

Priority Use Cases

  • Auto-routing, SLA alerts, and status updates.
  • Approval gate before risky actions.

Operating Model

  • Design in simulate mode, release in execute mode.
  • Own a weekly run review with error triage.

KPI

  • Workflow success rate and median duration.
  • Manual steps removed per process.

Recommended Path

Follow chapters in order to move from configuration to production execution.

  1. 1. Workflow Builder

    Goal: Workflow Builder

    Workflow Builder formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Workflow Builder" with measurable controls for safe workflow execution.

    • Workflow graph mirrors real process ownership.
    • Operational evidence is captured for Workflow Builder.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • Definition validation blocks invalid operators.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 2 before edge cases and access scope are confirmed for this step.

    • One giant workflow for unrelated processes.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

  2. 2. Triggers

    Goal: Triggers

    Triggers formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Triggers" with measurable controls for safe workflow execution.

    • Triggers are deterministic and scoped.
    • Operational evidence is captured for Triggers.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • Trigger source and payload contract are tested.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 3 before edge cases and access scope are confirmed for this step.

    • Triggering on noisy events without filters.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

  3. 3. Conditions

    Goal: Conditions

    Conditions formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Conditions" with measurable controls for safe workflow execution.

    • Conditions encode business policy, not guesswork.
    • Operational evidence is captured for Conditions.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • Condition branches produce expected candidates.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 4 before edge cases and access scope are confirmed for this step.

    • Duplicating condition logic across workflows.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

  4. 4. Actions

    Goal: Actions

    Actions formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Actions" with measurable controls for safe workflow execution.

    • Actions are idempotent and permission-safe.
    • Operational evidence is captured for Actions.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • Approval-required actions enforce state machine.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 5 before edge cases and access scope are confirmed for this step.

    • Direct execution of sensitive actions in simulate-only phase.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

  5. 5. Webhooks

    Goal: Webhooks

    Webhooks formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Webhooks" with measurable controls for safe workflow execution.

    • Inbound/outbound webhooks are authenticated and replay-safe.
    • Operational evidence is captured for Webhooks.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • HMAC validation and retries are observable.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 6 before edge cases and access scope are confirmed for this step.

    • Accepting unsigned payloads in production.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

  6. 6. Logs, Retry & DLQ

    Goal: Logs, Retry & DLQ

    Logs, Retry & DLQ formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Logs, Retry & DLQ" with measurable controls for safe workflow execution.

    • Failures are diagnosable and recoverable.
    • Operational evidence is captured for Logs, Retry & DLQ.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/workflows/{id}/run-test), then confirm expected permissions and logs.

    • Run logs include cause, context and retry policy.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 7 before edge cases and access scope are confirmed for this step.

    • Silent failures without alerting threshold.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

Go-live Checklist

  • Run test returns candidates and logs.
  • Failed runs emit actionable error payloads.
  • Retry and dead-letter handling documented.

Success Criteria

  • Faster onboarding for a new team.
  • No critical action depends on implicit tribal knowledge.
  • Support can diagnose an incident in under 15 minutes.