Avatar

Arpit Mishra

Developer

HomeAboutProjectsArticlesContact

Socials

LinkedInGithub
Read Resume
thumbnail

Flowly

NextjsRAGHugging FaceKafkaPostgresWebsocketDockerNode

AI Enabled Visual Workflow Automation — From Trigger to Action.

A Zapier-style automation platform that lets you build event-driven workflows without writing a single line of code. Connect an incoming webhook to an email action, configure your flow in minutes, and let the platform handle the rest — automatically routing data from trigger to delivery every time an event fires.

Built for developers and non-technical users alike who want to automate repetitive tasks without stitching together APIs manually. The flow builder gives you a clear visual of what happens at each step, and the extensible integration model means new triggers and actions can be added as the platform grows.

AI-Powered Email Assistant AI Chat integrated with Flowly's AI — ask questions, brainstorm, think out loud. But the moment you say something like "tell Ravi the meeting is pushed to Friday" or "send Arpit the milk message", the assistant shifts gears. It detects the intent to send, infers the recipient, generates a subject and body if you didn't spell one out, and silently triggers your Flowly webhook — turning a casual message into a delivered email without you ever leaving the chat. No forms. No compose window. Just say it.

AI AGENT AS TRIGGER

ai

System Architecture

Flowly/How it works

A Zapier-style automation platform that lets you build event-driven workflows

thumbnail

The frontend where users define a flow — pick a webhook as the trigger and an action (e.g. send email), then save it. The API server responds with a unique webhook URL like hooks.flowly.com/a/b/<uuid>.

  • Pick a trigger type — currently: incoming webhook
  • Configure an action — currently: send email
  • Save the flow to get a unique webhook URL
  • URL format: hooks.flowly.com/a/b/<uuid>

Data flow

UI→API→DB→Hooks→Sweeper→Kafka→Workers→Email
Scaling guide

Flowly — shortcomings & fixes

9 areas to address before taking Flowly to production scale.

Recommended fix order: DLQ → Sweeper CDC → Flow config cache → Kafka tenant partitioning → Observability → Circuit breakers

One service receiving all webhook calls becomes a bottleneck under high traffic. 10k GitHub pushes firing simultaneously will overwhelm a single instance. Without idempotency keys, caller retries create duplicate outbox rows.

  • FixHorizontal scaling behind a load balancer — stateless service, scales linearly
  • FixIdempotency key on every ingest request — hash of (flow_id + caller_event_id)
  • FixDedup on outbox insert using INSERT ... ON CONFLICT DO NOTHING
  • RiskWithout idempotency, a caller retry during a network blip creates two executions

Priority summary

4
HIGH
4
MEDIUM
1
LOW
Live Preview
2026 — Built by Arpit Mishra