How do you handle a Wait node that waits on a customer, not a colleague? Looking for honest feedback

Feedback
,
1

Hi guys,

I’m a solo founder from Norway, looking for honest opinions on something I built for n8n. Write-up: How to pause an n8n workflow until a customer answers - DEV Community

I was working on complex loan applications. Our biggest challenges were outdated customer information, wrong documents, bad answers and drop-offs. For the advisors, that meant phone calls and emails back-and-forth.

So we tried a different approach. Customers started with a tiny public lead form: just their email and the product they wanted. Then we emailed them a request, prefilled with what our AI could find about them.

Customers had less to write, we got up-to-date information, and more people actually finished the application. In the end, quality answers = less time used by both sides.

That turned into a hobby project and then a full product called Formstep, a general-purpose form builder (this part inspired by Tally), where you send each form as a request. It was meant to work with workflows and AI agents from the start.

In a nutshell: the n8n node creates the request, the Wait node pauses on On Webhook Call, and the same run continues with the answers.

It is similar to the built-in n8n form, but with more:

  • Prefill, lock and context for each request
  • Branding and multilingual support
  • Complex logic, calculator, Stripe payment, cal.com schedule etc.
  • A dashboard where you can see all requests, retry etc.
  • Reminder on e-mail if they forget to send in
  • AI that checks documents and answers
  • Create forms on the fly by sending a schema with the request

… and dozens of features and built-in integration :slight_smile:

Before you try: the node isn’t verified yet, so it isn’t on n8n Cloud and runs on self-hosted n8n only. Formstep has a free plan, so you can send 10 emails to your own account or hand off the request link yourself.

I would love your feedback, for example to try some of the examples mentioned in the dev.to post.

If you try the node: what broke or confused you, and what is missing before you’d use it in a real workflow? Is there anything I should fix before I submit it for verification?

PS: if this is the wrong forum, let me know. I can move it or delete. I am sorry!

2

I haven’t tried the node yet, but before using this for loan applications I’d want a clear failure-path example alongside the happy path.

Pass {{$execution.resumeUrl}} to the request creation step for that specific run, and treat that URL as a secret. If the callback can send credentials, configure authentication on the Wait node. After the Wait, use an IF node to check the returned request ID and required fields before any CRM or document updates.

I’d also test a duplicate submission, a customer who never responds, and an n8n restart while waiting. Show how to set a wait limit and route expired requests to a follow-up queue, and document what happens to a late callback. A small example with fake customer data would make those cases easier to verify before handling real applications.