Built a form tool that writes directly to Notion. Looking for feedback.
Hey everyone,
I use Notion for pretty much everything and kept hitting the same wall. I needed to collect info from people outside my workspace and nothing really worked the way I wanted. Typeform and Google Forms don't connect to Notion natively and every time I looked into fixing that it involved setting up a whole Zapier workflow just to move data from one place to another.
So I just built my own thing. It's called Rowdrop.
You paste in your Notion database, it reads your columns, you pick which ones become form fields and you get a link you can share with anyone. Every submission goes straight into your database as a new row. That's it.
It also does conditional logic, file uploads, password protection, webhooks, email notifications and has a submission viewer with CSV export built in.
Been working on this solo for the past few weeks. It works, it's live, 7 day free trial no card needed at rowdrop.us.
Honest question though, if you use Notion and have dealt with this problem before, what did you end up doing? And what would actually make you switch to something new? Would love real feedback.
Notion-native forms are a smart wedge — the friction with most form tools is that the data ends up siloed in yet another dashboard. Curious what happens when fields don't map cleanly (e.g., select options created via the form that don't exist in the Notion property yet) and whether you're planning support for relations/rollups. Happy to test if you have a free tier.
Yeah that friction point is exactly why I built it. Data ending up in a third dashboard defeats the whole purpose of using Notion.
On the select mapping question - right now Rowdrop reads the existing options from your Notion property when you set up the form, so the dropdown on the form only shows what's already in Notion. If a new option gets submitted that isn't in the property yet, Notion rejects it. It is a real limitation. The workaround most people use is a text field instead of select when they want open-ended answers. I am looking at whether I can auto-create new select options on submission but haven't shipped that yet.
Relations and rollups are on the roadmap but honestly further out. They are complex to map to a form input in a way that makes sense to someone filling out the form. Rollups especially are read-only computed fields so they don't really apply. Relations I could see working as a dropdown that pulls from the related database - just haven't built it yet.
And yes there is a free tier and a 7 day trial when signed up.
The Notion-native angle is the right wedge. The question aryan raises about messy workspaces is worth digging into -- in my experience the buyers who get most value from tools like this are the ones with the most structured Notion setups (templated client databases, property-heavy dashboards). Those are also the hardest to reach because they're deep power users who've already tried and abandoned a few integrations.
The distribution move that works for this type of tool is Reddit threads and Notion-specific Discord/Slack communities, not Product Hunt. The people posting 'I need clients to fill in X' in r/Notion or the Notion community Slack are experiencing the pain right now, actively looking. That's where your first 20 users are hiding.
On the AI angle to watch: Notion's own AI features are expanding. The risk isn't that Notion ships forms -- it's that the intake layer increasingly looks like a chat interface ('Tell me your requirements'), not a structured form. If that shift accelerates, the value of Rowdrop migrates to the submission viewer and the structured output side (clean rows, CSV export, webhooks), not the form-filling UX.
What does your 7-day trial data show -- what percentage of people who start a form actually share it externally vs. abandon?
Totally agree on the distribution - r/Notion and the Notion Slack communities are exactly where I'm focused right now. Product Hunt is not the move for this.
The AI intake shift is a good point. I think you're right that the durable value ends up on the output side - clean rows, webhooks, CSV. That's where I'm leaning on the roadmap anyway.
On the trial data - too early to have clean numbers honestly. Still instrumenting that. Early gut feeling is most drop-off happens at the field mapping step before anyone even shares the form.
The Notion integration angle is smart — people already live in Notion.
Main question: how are you handling cases where the Notion workspace structure is messy?
That's usually where integrations break down.
Good call. Right now Rowdrop maps directly to whatever properties exist in your database so a messy setup does show up in the form. Working on a database health check that flags issues like missing title fields, unsupported property types, and duplicate names before you build the form. That way you catch the problems in Notion first instead of finding out when something breaks.
This is a clean wedge because the pain is not really “forms.” It is removing the integration layer between external people and an internal Notion database. That is much sharper than competing with Typeform or Google Forms directly.
I’d probably position Rowdrop around “turn any Notion database into a shareable intake flow” rather than just “forms for Notion.” The strongest buyer is probably someone already using Notion as a lightweight CRM, client portal, content ops tracker, hiring tracker, or request system, and they hate needing Zapier just to collect structured input.
One thing I’d watch is the name. Rowdrop explains the row-submission mechanic, but it may keep the product tied to a small utility frame. If this expands into a broader Notion workflow/intake platform, a cleaner SaaS brand like Xevoa .com would give it more room than a name tied only to dropping rows.
The positioning point is really good and honestly better than how I have been describing it. "Turn any Notion database into a shareable intake flow" is way sharper than "forms for Notion." Thanks! I will be Updating my pitch.
The use cases you named are exactly who is using it right now - people running lightweight CRMs, hiring trackers, client portals in Notion who just need external people to put structured data in without touching Notion itself.
On the name - fair point. Rowdrop made sense early on but I can see how it boxes the product in. Something to think about as it grows.