Inspiration
Campus club officers, especially the president and activity lead, run the same event through too many channels. A workshop has one set of facts — title, speaker, time, room, capacity, deadline — but those facts get rewritten into Instagram, Stories, Linktree, LINE, a Google Form, Gmail, and school paperwork for activity applications, rooms, budgets, and reimbursement. The copy drifts, and filings often happen the night before a deadline. I built ClubFlow after watching this happen in student clubs in Taiwan, starting with a sample workspace for NYCU’s Entrepreneurship & Innovation Club.
What it does
ClubFlow keeps a single event brief as the source of truth. Officers pick modules in a marketplace, run one workflow, and get ready-to-copy previews:
- Instagram caption, hashtags, and a 1080×1350 feed card
- Instagram Stories as a 1080×1920 image with the title, speaker, time, and place burned into the pixels (because Meta’s Graph API has no caption field and cannot add poll, question, countdown, or link stickers)
- Linktree update payload
- LINE Official Account broadcast draft
- Google signup form fields
- Gmail HTML and plain-text draft
- School documents: 活動申請, 場地借用, 預算, and 報銷, plus deadline reminders
- Speaker and attendee certificates
- Reminders for 3 days before and the morning of the event
- A post-event thank-you and survey
Nothing is posted, emailed, or filed. The app never asks for a school password. Sample onboarding is NT$6,800 for one day of setup, plus per-event add-on modules; prices are a demo of the business model, not a checkout.
How we built it
A single-page Vite 6 + TypeScript app with no frontend framework. Generation runs in the browser from bilingual templates, so the demo needs no API key. Canvas draws the Story, feed card, and certificates. The UI defaults to Traditional Chinese, with an English toggle for judges.
Challenges we ran into
Instagram Stories cannot carry API captions or stickers, so any text a member should read has to live in the image itself. School systems also cannot hold an officer’s SSO; the honest product boundary is to fill drafts and remind deadlines, then let a person submit. Shipping a full live-publish stack to Instagram, LINE, Gmail, and Google in this window would have been a demo that fails without keys, so ClubFlow generates previews that always run.
Accomplishments that we're proud of
A judge can load a sample workshop, mix modules, watch the quote change, and see all ten core outputs in a few minutes — including a real Story image with burned-in text and four school-document drafts. The product is bilingual and never pretends it posted anything.
What we learned
The useful layer for student clubs is not “another chatbot.” It is one structured brief, reusable modules, and clear human checkpoints where APIs or school policy stop.
What's next
Live connectors where they are allowed (for example Instagram via a wrapper around Meta’s API, plus Linktree, LINE, Google Forms, and Gmail), check-in, a president-approval step before sending, handover notes for new officers, tracking short links, and school-document templates for more campuses.
Built With
- api
- canvas
- css
- fontsource
- html
- typescript
- vite
