Shipped an n8n integration today to reach my first users. The forum I built it for won't let me post yet.
Solo founder, sole trader, $0 institutional funding — full unfiltered stage numbers at metrecept.co.uk/docs/status if you want the real picture.
I build Metrecept: a metered LLM gateway that sits behind a one-line baseURL swap. An exact-repeat call returns from cache instead of re-billing the model, and every cache hit comes back with a signed Ed25519 receipt — checkable against a public key by anyone, not just a number in a log you have to trust.
This week I went looking for where my actual first users already are, instead of hoping a landing page finds them. Found a real, recurring thread on n8n's own community forum: people hand-rolling workarounds to see what an AI Agent workflow actually spent, because there's no official way to get that number out. Multiple threads, going back to 2025, still open, no fix.
So instead of just replying, I built and published n8n-nodes-metrecept — a proper community node (credential + 3 operations, real test suite, published to npm this week). It doesn't solve their exact ask (n8n exposing token counts natively) — but it solves what's underneath it: don't pay twice for a repeated call, and get a receipt for what you did pay for.
Then I went to post about it on the same forum where I found the problem, and hit a wall I didn't expect: brand-new accounts there need to earn "trust level 1" before they can post or reply at all. The exact community I built the thing for, and I currently can't talk to inside their own house.
Not asking for a fix to that specific gate — it'll resolve itself in a day or two. What I am curious about: for those of you who've built something aimed at a specific platform's own community (a Slack app directory, a WordPress plugin listing, a forum like this one), did you hit friction actually reaching that community from a cold/new account — and what got you through it faster than just waiting?
Free to poke at the actual thing in the meantime: metrecept.co.uk/demo needs no signup, and n8n-nodes-metrecept is live on npm right now if anyone here runs n8n workflows with an LLM step in them.
I hit the same wall on two platforms.
On X, a new-looking account can reply. It cannot get a fair test from its own posts. Mine sat at 62–222 impressions this week. Replies into threads that already existed were the only place a stranger saw the sentence.
Indie Hackers did the same thing: comment first, post later. After posting unlocked, my own posts still underperformed replies. The gate taught the move. Waiting for the gate to lift did not.
I would not wait the day or two if I could already see the threads. Answer the existing n8n questions as a person, with no node link, until the account can post. The people who wrote those threads are already in the room. The listing can wait until the door opens.
I have not found a faster unlock than useful replies. I have found that unlocking does not replace them.
To what extent do you think this is a fair prejudice and to what extent is it just primitive tribalism? lol
Neither, I think. It is a lazy filter, not a prejudice. Checking account age is free. Checking whether a post is spam costs a human. So the forum charges newcomers a wait instead of paying moderators.
It is fair in aggregate and unfair to the one builder who actually solved the thread's problem. The cost lands on you, not on the spammers it was built for.
The same filter on X is quieter. My own posts sat at 17–205 views this week while one reply under someone else's tweet reached 2,934. Reply first is the only door that opens on day one.
Did the n8n forum tell you what trust level 1 actually requires, or is it a black box too?