Repository navigation
Release 0.13.0: Simplify, clearer HTTPS errors, use-case examples - #6
Merged
Merged
Conversation
@n8n/node-cli moves from 0.49.1 to 0.54.2, Vitest to 5.0.5, @types/node to 22.20.5 and Prettier to 3.9.10. The package still ships no runtime dependency: n8n-workflow stays a peer the n8n instance provides. Tests, build, lint and the verification scanner's eslint pass unchanged.
Get returned 40-odd fields per request, timeline and display text included, and Get Many nearly as many, which n8n's guidelines cap at ten behind a Simplify option and which crowd an AI agent's context when the node runs as a tool. Node version 3, the default for new nodes, adds Simplify to Get and Get Many, on by default. It returns id, status, outcome, externalId, formId, recipientEmail, answers (Get only), and createdAt, expiresAt and completedAt as ISO 8601 strings instead of Unix milliseconds. Turned off, or on a version 1 or 2 node, the raw response comes back as before, so saved workflows read the same fields.
An n8n without a public address hands out http://localhost webhook and resume URLs. Execute step and Publish on the trigger then stopped with Formstep's bare "VALIDATION_ERROR: targetUrl must use https", and Wait for the Outcome with a callbackUrl error. Both now stop before calling Formstep, name the URL n8n produced, and point at WEBHOOK_URL and N8N_EDITOR_BASE_URL and the install guide's public-address section. The Fields mapper also names a hidden field once: a hidden field is titled with its key, so it read "reference (reference) · context".
A document entry leaves its Documents block empty when the form has one, which Formstep reads as that block. n8n drew the empty value as an unselected dropdown with a red warning, so a working setting looked broken. The picker now lists 'Automatic' first, the default, with the form's Documents blocks after it.
Each one was run end to end against Formstep from a local n8n: - formstep-expense-approval.json: a manager gets the expense with the receipt attached, approves, declines or asks for changes, and the workflow routes each answer and an unanswered request. - formstep-invoice-ai-confirm.json: an invoice PDF goes through Extract from File and an Information Extractor, the supplier confirms or fixes what the AI read, and a Code node lists what they corrected. The AI result is pinned, so it runs before a model credential is set up. - formstep-claim-documents.json: a Code node turns the claim type into file questions, the node builds that form in the request, and every upload is downloaded and saved. - formstep-ai-agent-onboarding.json: an AI Agent with Formstep tools to send the onboarding form, check it and remind the client. Every example now creates test requests, so a first run emails nobody, and uses example.com addresses. The existing examples move to node version 3. A test checks that each example imports inactive, without credentials, and connects only nodes it has.
The README had grown to every parameter, payload and caveat the docs also carry, so the essentials were hard to find. It now opens with what you can build, each use case with its guide on docs.formstep.io and its example workflow, then install, connect, the two nodes, the handful of facts that trip people up, and links to the reference. Building, testing, running against Formstep from a local or Docker n8n, and releasing move to CONTRIBUTING.md, which also notes the version rules and the scanner command to run before a release. The claim example drops its emoji form option, which respondents never see.
Node version 3 with Simplify on Get and Get Many, clearer errors when n8n has no public HTTPS address, the Automatic Documents block, four use case examples, and a shorter README. Smoke tested against production Formstep from n8n 2.44.6 in Docker: install from npm, OAuth connect, every operation and error path, all five live trigger events, Execute step listening, Wait for the Outcome, New Form, documents and files, and the node as an AI agent tool.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Smoke tested against production Formstep from n8n 2.44.6 in Docker: install from npm, OAuth connect, every operation and error path, all five live trigger events, Execute step listening, Wait for the Outcome, New Form, documents and file uploads, and the node as an AI agent tool.
npm test(149),npm run build,npm run lintandeslint --no-inline-config credentials nodespass.