Custom HTTP integration returns error code 422
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Desktop - Windows
Describe the bug
Config Json:
follow-integration-settings-2025-10-21.json
Log:
Description:
I encountered an HTTP CODE 422 error when trying to connect to N8N using a custom HTTP integration. After testing, the error occurs when the Body contains parameters like the following:
-
[summary]
-
[content_html]
-
[content_markdown]
From the log, it seems that \n is causing the problem
Entry ID
https://spring.io/blog/2025/10/21/spring-ws-4-0-16-available-now
Relevant Information
Other Logs
[content_html]
[content_markdown]
Reproduction Video
No response
Environment
Environment
App Version: 0.7.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Folo/0.7.0 Chrome/138.0.7204.97 Electron/37.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: KYd021o_ytkw-lTqW-PZf
Mode: production
Renderer: 0.7.0
Windows Environment
Version Windows 11 Home Chinese Edition
Version number 24H2
Installation date 2025-9-9
Operating system version 26100.6899
Experience the Windows Feature Experience Pack 1000.26100.253.0
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached follow-integration-settings-2025-10-21.json and main.log files, focusing on requests whose body contains [summary], [content_html], or [content_markdown]. Reproduce the custom HTTP integration on Windows with the Spring blog entry, then verify that equivalent requests no longer fail with HTTP 422.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100