Sure. I've made some quick modifications to Andy's workflow that should make it a bit easier to configure for your own use case. Download my fork of andy’s workflow from Codeberg.org. Install the workflow and copy the first five nodes onto your own workflow canvas. Change the trigger keyword to something suitable for your use case. Copy configTest.json to your own workflow folder and edit it to your liking. Add or remove fields as needed. Trigger the workflow. (Note: the first trigger may take a moment, as the binary needs to compile. Make sure you have Xcode Command Line Tools installed – the workflow won't be able to compile without them.) The user-inputted form values will be returned as variables to the resultsReceived External node (inside your own workflow), where you can use them however you like.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Handling User Input via Reusable Config-Driven Input Forms | 1 | 1 | 22-06-2026 |
| 2 | Search Figma files and open them in the desktop app | 2 | 6 | 27-06-2026 |
| 3 | Claude CLI for Alfred | 10 | 8 | 24-06-2026 |
| 4 | Claude CLI for Alfred | 0 | 5 | 23-06-2026 |
| 5 | Search Figma files and open them in the desktop app | 5 | 7 | 26-06-2026 |
| 6 | Request to introduce a Return/Reassign to Previous Step function for Forms utilizing the Section Assignee workflow | 0 | 7 | 26-06-2026 |
| 7 | Finally, visual workflows in WordPress! | 8 | 7 | 27-06-2026 |
| 8 | Search Calibre Library | 0 | 5 | 26-06-2026 |
| 9 | Gavity forms conditionals not working if they are inside a looper consumer | 0 | 7 | 27-06-2026 |