How to use data in `formTrigger` node

Questions
1

Hey. I want to use some data from a http request to pre-fill a formTrigger node (make a Dropdown List filled with usernames from elsewhere). But, since it is a trigger node, I have no input port. How can I achieve that?

Information on your n8n setup

  • n8n version: 1.61.0
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Debian 12
2

You can prefill some fields by adding ?my_field=my_value to the URL when you request the form. But we don’t support dynamic dropdowns or selecting a value from a dropdown yet, sorry…

3

Hi @Gauner
we’ll be soon releasing multi-step support for the form node and dynamic building using JSON syntax.

So what you will be able to do it:

  1. Have a first page of the form with some static form elements
  2. After the user fills the first page, move to the next node in the workflow. this could be an HTTP Request node that retrieves some data
  3. Have another form page dynamically built using the data from the HTTP Request node

The only limitation is that you need to have a first form page to start the flow.
This will be released in a few weeks
Hope it helps

1 Like
4

Thank You very much, that’s great news. I can use it well in my current project. ATM I simulated a multistep form with it’s response URL pointing to a second form.

Will it also be possible to put some arbitrary data (like a special section with own html code) in it?
For the Oauth2 device code authentication I posted here, it would be nice to show the user a form with the link and the device code in it and let him press a button, if he is done authenticating. Up to now I failed putting a clickable link into a form, everything I put there was not clickable.

Thank You very much!

5

At the moment it’s not possible to add content other than form element.
We are aware that it would be great to allow adding other types of content (text, lists, images, HTML) and this is on our list for future improvements (but not coming soon)

2 Likes
6

New version [email protected] got released which includes the GitHub PR 10390.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.