Build a full-stack application that aggregates customer interaction data from multiple sources — Firefly.ai meeting notes, forwarded emails, and screenshots — and produces daily AI-generated summaries organized by customer. Technical Requirements: ∙ Backend/Database: Use Supabase (Postgres + Auth + Storage) as your primary backend. Store all ingested data (meeting notes, emails, screenshots) in structured tables with proper relations to customer records. ∙ Authentication & Access Control: Implement Supabase Auth with domain-restricted sign-up — only users with a @vamo.app email address should be able to create accounts. Enforce data access at the database level using Supabase Row Level Security (RLS) policies — all tables must have RLS enabled, and policies should ensure that only authenticated users with a verified @vamo.app email domain can read, insert, or modify any data. No application-level authorization checks alone — RLS must be the primary enforcement layer. ∙ Firefly.ai Integration: Connect to the Firefly.ai API to pull in meeting transcripts/notes from sales and customer success calls. Categorize and associate them with the correct customer automatically (using attendee metadata, meeting titles, or NLP matching). ∙ Email Ingestion: Set up an inbound email processing pipeline — users should be able to forward customer emails to a dedicated address, which then parses the sender, subject, body, and any attachments, and stores them against the appropriate customer record. ∙ Screenshot Capture: Allow users to upload screenshots (stored in Supabase Storage) and tag them to a customer, with optional OCR or AI-based description extraction. ∙ Daily Summaries: Generate AI-powered daily summaries per customer that synthesize all interactions (calls, emails, screenshots) from that day. These summaries should be viewable in-app and optionally delivered via Resend (email delivery is a nice-to-have, not required). ∙ Resend Integration: If implemented, use Resend to email daily summary digests to team members. Deliverable: Submit a screen recording / video walkthrough of you using the application end-to-end with a real Firefly account — demonstrating the ingestion of real meeting notes, email forwarding, screenshot uploads, and the generated daily summaries.
vetEntry's Attempt
Started February 13, 2026
Waiting for Contribution
vetEntry is working on their contribution. Once they push commits and request a review, the submission will be evaluated.
Work Environment
Setting up your work environment
We're creating a fork and setting up your development environment. This usually takes a few seconds.
Work Progress
Commit message
Initial commit
You'll need to use these external services to complete the challenge. During development you will use your own API keys and accounts.
Use Vercel to easily host your NextJS app out of your GitHub repository. Handles auto-deploy, etc.
None needed, you do not need to host their website.
Use Supabase for an easy back-end (database, login, etc).
Use env variables: PUBLIC_SUPABASE_PROJECT_URL PUBLIC_SUPABASE_ANON_KEY
You MUST ensure all Supabase migrations, etc are present in supabase/migrations. Ensure these work from a clean slate.
Do not use service role keys. Bounties that use these will be rejected. Use idiomatic Supabase with RLS
The all-in-one platform for agents. Build, deploy, and optimize production-ready agents faster with pre-built components or from scratch.
Use OPENAI_API_KEY for the API key. You will need to use your own account for local development.
Email API for developers. Send transactional and marketing emails at scale with a modern, developer-friendly API.
You must sign-up for your own Resend account to use during development. Do not use templates, etc. Ensure your API key is stored as an environmental variable named RESEND_API_KEY.