Flow Forge
Design and adjust journeys without redeploys
Steps, delays, fallbacks, and branching you can edit live. Trigger by events and keep users on the right path.
Journey building
Orchestrate without redeploys
Event driven
Start and branch flows from your product events.
Retries & fallbacks
Channel fallback and backoff included.
Live editing
Change timing and steps without code pushes.
Segmentation
Branch by tenant, traits, or channel readiness.
Visibility
Flow-level health, failures, and engagement.
Ops-friendly
Product and ops can adjust without dev queues.
How it works
Trigger, branch, and observe
- 1. Fire an event with user + tenant context.
- 2. Flow Forge applies steps, delays, and retries.
- 3. Observability shows successes, failures, and engagement.
event: user.signupstatus: processing
Step 1: Welcome emailSent
Template v3 · Provider: primary-email
Step 2: Push fallbackRetrying
Channel fallback active · backoff 2m
Flow Forge FAQ
How teams use journeys
Can we edit flows live?+
Yes. Update steps, delays, and conditions without redeploying your app.
Do retries and fallbacks come prewired?+
Yes. Use defaults or customize backoff, channels, and limits.
Is segmentation supported?+
Yes. Branch by tenant, traits, or delivery readiness.