Fintech Automation Studio

Visual Flow Builder for the Sapliy Fintech Ecosystem

Build event-driven automations for payments, notifications, and financial events — no code required.

Core Concept

Automation Studio implements the Zone → Event → Flow model:

┌─────────────────────────────────────────────────────┐
│  Zone (isolated automation space)                   │
│  ┌───────────┐    ┌───────────┐    ┌────────────┐  │
│  │  Events   │ → │   Flows   │ → │  Actions    │  │
│  │ from SDK  │    │ (logic)   │    │ (webhooks) │  │
│  └───────────┘    └───────────┘    └────────────┘  │
└─────────────────────────────────────────────────────┘

Each zone has:

• Test mode — Safe experimentation with pk_test_* keys
• Live mode — Production events with pk_live_* keys
• Separate logs, flows, and events per mode

Features

🎯 Event Triggers

Source	Events
Payments	payment.succeeded, payment.failed, refund.created
Wallets	balance.changed, low_balance
Ledger	transaction.created, entry.posted
Schedule	Cron-based triggers
Manual	Trigger from UI or CLI

🧠 Logic Nodes

• Condition — If/else branching
• Filter — Event filtering
• Rate Limit — Prevent flooding
• Approval — Human-in-the-loop
• Timeout — Delay and timeout

📤 Action Nodes

• Webhooks — HTTP to external services
• Notifications — WhatsApp, Email, Slack, Discord
• Audit Log — Create audit entries
• Debugger — Log and inspect

Architecture

┌─────────────────────────────────────┐
│  Fintech Automation Studio         │
│  (This repo - UI only)             │
└──────────────┬──────────────────────┘
               │ REST / WebSocket
               ▼
┌─────────────────────────────────────┐
│  fintech-ecosystem                  │
│  (Events, Flows, Execution)         │
└─────────────────────────────────────┘

Important: This UI does NOT execute flows. All logic runs in fintech-ecosystem.

Quick Start

# Install dependencies
npm install

# Start development server
npm run dev

Open http://localhost:3000 to access the Flow Builder.

Environment Variables

# API endpoint (required)
NEXT_PUBLIC_API_URL=http://localhost:8080

# WebSocket for real-time events
NEXT_PUBLIC_WS_URL=ws://localhost:8080/events

Project Structure

src/
├── app/              # Next.js App Router pages
├── components/       # UI components
│   ├── flow/         # Flow builder components
│   ├── nodes/        # Node type components
│   └── ui/           # Shared UI components
├── hooks/            # React hooks
├── services/         # API client
├── store/            # Zustand state
└── types/            # TypeScript definitions

User Roles

Role	Capabilities
Admin	Full access, manage org settings
Finance	View transactions, approve flows
Developer	Create and edit automations
Viewer	Read-only access

Template Variables

The Flow Builder supports Handlebars template syntax to dynamically reference event data in your automation nodes. This allows you to create personalized messages, conditional logic, and dynamic webhooks.

Available Variables

Variable	Description	Example Value
{{event.type}}	Event type that triggered the flow	payment.succeeded
{{event.id}}	Unique event identifier	evt_abc123
{{event.payload.*}}	Any field from the event payload	{{event.payload.amount}}
{{event.createdAt}}	Event creation timestamp	2024-01-15T10:30:00Z

Usage Examples

1. Approval Node Messages

Create dynamic approval messages that include event data:

Approval required for payment of ${{event.payload.amount}} {{event.payload.currency}}

Customer: {{event.payload.customerId}}
Transaction ID: {{event.id}}
Requested at: {{event.createdAt}}

Result:

Approval required for payment of $5000 USD

Customer: cust_456
Transaction ID: evt_abc123
Requested at: 2024-01-15T10:30:00Z

2. Webhook Payloads

Send dynamic data to external services:

{
  "event_type": "{{event.type}}",
  "transaction": {
    "amount": {{event.payload.amount}},
    "currency": "{{event.payload.currency}}",
    "customer_id": "{{event.payload.customerId}}"
  },
  "timestamp": "{{event.createdAt}}"
}

3. Conditional Logic

Use template variables in condition nodes:

{{event.payload.amount}} > 10000

This evaluates to true if the payment amount exceeds $10,000.

4. Notification Messages

Create personalized notifications:

🎉 Payment received!

Amount: ${{event.payload.amount}}
From: {{event.payload.customerName}}
Status: {{event.payload.status}}

Best Practices

1. Always validate data: Use condition nodes to check if required fields exist
2. Use default values: Handlebars supports {{event.payload.name || "Unknown"}}
3. Format numbers: For currency, ensure proper formatting in your webhook handlers
4. Test with real events: Use the CLI sapliy listen command to see actual event payloads

Supported Node Types

Node Type	Template Support
Approval	✅ Message field
Webhook	✅ URL, headers, body
Notification	✅ Message content
Condition	✅ Expression evaluation
Debugger	✅ Log messages

Roadmap

• Phase 1 ✅ — Core flow builder, events, automations
• Phase 2 — Approvals, manual actions
• Phase 3 — Marketplace, templates, paid plans

Part of Sapliy Fintech Ecosystem

Repo	Purpose
fintech-ecosystem	Core backend (events, flows, execution)
fintech-sdk-node	Node.js SDK
fintech-sdk-python	Python SDK
fintech-sdk-go	Go SDK
fintech-ui	React components
sapliy-cli	Developer CLI

License

MIT © Sapliy