FlowPilot

FlowPilot detects important events across your apps and safely handles the next steps automatically—saving time, reducing manual work, and keeping you in control.

Comment

Inspiration

I wanted to build something that does more than answer questions. Many useful tasks begin with a real event: a flight email, a new client message, a subscription renewal, or a salary credit. I built FlowPilot to handle the next steps automatically while keeping the user in control.

What it does

FlowPilot is an event-driven personal automation app. It connects to services such as email, calendar, files, GitHub, weather, and notifications.

A user can create a standing order like:

“Whenever I receive a flight confirmation, create my itinerary, update my calendar, save the ticket, check the weather, and ask before notifying my family.”

FlowPilot detects the event, prepares the required actions, asks for approval when needed, and shows a clear activity timeline.

How I built it

I built the frontend as a responsive web app using Next.js and TypeScript. The backend uses FastAPI and PostgreSQL.

The system converts incoming emails, files, and webhooks into structured events. It then matches them with saved standing orders, creates an action plan, checks permissions and risk levels, and runs approved tasks through connected services.

Challenges I ran into

The hardest part was making the system reliable and safe. External events can be incomplete, duplicated, or misleading. I had to add event validation, duplicate protection, permission checks, retries, approval steps, and clear error handling.

Connecting different services with different authentication and response formats was also challenging.

Accomplishments that I’m proud of

I built a working system that can turn one event into a complete multi-step workflow.

I am especially proud of the Travel Autopilot, which can detect a flight booking, create calendar events, organize travel files, check the weather, prepare a packing list, and request approval before sending a message.

I also built a clear action timeline so the user can understand what happened and why.

What I learned

I learned that useful automation is not only about connecting apps. It also needs clear rules, reliable execution, strong permission controls, and simple explanations.

I also learned that small, focused workflows are more useful and easier to trust than a system that tries to automate everything.

What’s next for FlowPilot

I plan to add more connectors, reusable automation templates, better mobile notifications, and more real-life workflows for freelancers, students, families, and small businesses.

I also want to improve the standing-order builder so non-technical users can create reliable automations with simple instructions.

Built With

Share this project:

Updates