维修 PDF 文档 n8n

维修 PDF 文档 是一个 PDF4me 节点操作 n8n 修复损坏或受损系统中的结构性错误 PDF 并尽可能恢复可读内容。使用它可以恢复无法打开的电子邮件附件、恢复损坏的存档文件，或恢复因传输失败而损坏的文档，所有这些都无需手动使用桌面修复工具。

此节点的功能

PDF4me：维修 PDF 文档 需要损坏或受损 PDF 来自二进制数据， Base64 String或者 URL并返回一个重建后的文件，其中结构错误已修复，并且只要底层数据仍然存在，即可恢复可读内容。它相当于人们手动使用的修复工具的自动化版本，只不过它可以在由电子邮件附件、云存储上传或文件传输失败触发的工作流中自动运行。

验证您的身份 API 要求

每一个 PDF4me 节点 n8n 需要有效 用于连接的凭证创建或选择一个可以容纳您的 PDF4me API 关键在于确保工作流程能够安全地验证维修请求。

Get your API Key

您不容错过的重要事实

真正需要的字段只有三个。

操作、输入数据类型和匹配的源字段涵盖了整个请求。输出文件名， Async 处理和二进制数据输出名称都具有可用的默认值。

修复的是结构问题，而不是密码问题。

该节点可以修复损坏的交叉引用表、格式错误的对象流以及类似的结构性损伤。但它不会移除加密。如果受密码保护的文件也已损坏，请先对其进行解密。

维修仅尽力而为，不保证一定能修好。

恢复取决于原始数据保留的程度。务必在后续步骤中附加验证步骤，以便工作流程能够检测到仍然无法打开的文件并跳转到备用方案。

n8n 中的 PDF4me 节点设置为“操作：修复 PDF 文档”，输入数据类型为二进制数据，输入二进制字段为 data，输出文件名为 repaired.pdf，异步切换为开启，二进制数据输出名称为 data。 — PDF4me 维修 PDF 文档参数面板 n8n

自动修复（n8n) 与手动在线工具

最多 PDF 排名靠前的修复工具都是手动操作、一次只能上传一个文件的网页上传工具。下面的对比说明了为什么从自动化平台角度来看，结果会与这些工具有所不同。

方法	扳机	最佳匹配
Manual web tool (iLovePDF, Adobe, Sejda)	Person uploads one file by hand	A single one-off file you have open in front of you
PDF4me Repair PDF Document in n8n	Email arrival, cloud storage upload, or file-transfer event	Recurring corruption on incoming attachments, archives, or transfers, with no manual step

维修涉及哪些参数？ PDF 需要文件吗？

必需的： 操作、输入数据类型以及与该输入类型匹配的字段。输出文件名， Async 处理名称和二进制数据输出名称都是可选的，并具有可用的默认值。

范围	必需的	它的作用	例子
Action	Required	Selects the PDF4me node action to run. Choose Repair PDF Document.	`Repair PDF Document`
Input Data Type	Required	Format of the source PDF input. Choose Binary Data (from a previous node), Base64 String, or URL.	`Binary Data`
Input Binary Field	Conditional	Name of the binary property on the incoming n8n item that holds the damaged PDF. Required when Input Data Type is Binary Data. Defaults to data.	`data`
Base64 Document Content	Conditional	Base64-encoded content of the damaged PDF. Required when Input Data Type is Base64 String.	`JVBERi0xLjQK...`
File URL	Conditional	Publicly reachable HTTPS URL to the damaged PDF. Required when Input Data Type is URL.	`https://example.com/corrupted.pdf`
Output File Name	Optional	Filename for the repaired PDF output. Defaults to a generated name when left blank. Include the .pdf extension.	`repaired.pdf`
Async Processing	Optional	Runs repair in the background instead of holding the workflow execution open, useful for large or badly damaged files.	`true`
Binary Data Output Name	Optional	Name of the binary property the output item exposes. Defaults to data.	`data`

输出字段

一次成功的运行返回一个 n8n 携带修复后的二进制文件的物品 PDF。

场地	类型	它包含什么
`Binary (data)`	Binary	The repaired PDF with structural errors fixed and readable content restored wherever recoverable, under Binary Data Output Name (default data).
`fileName`	String	Generated filename, matching Output File Name.
`mimeType`	String	MIME type of the output, always application/pdf.
`fileSize`	Number	Size of the repaired PDF in bytes.

如何设置维修 PDF 文档 n8n？

添加 PDF4me 致你 n8n 工作流程并选择 维修 PDF 文档 行动。
在 用于连接的凭证请选择您的 PDF4me 凭证或点击 创建新凭证 并粘贴你的 API 钥匙。
放 输入数据类型 到 二进制数据 （默认）， Base64 String，或者 URL 并提供相应的损坏部件 PDF 场地。
（可选） 输出文件名 （必须以……结尾） .pdf）。
使能够 Async 加工 如有需要，可对大型文件或严重损坏的文件进行处理。
执行节点并路由修复后的节点 PDF暴露于 二进制数据输出名称进入下一步。

典型配置

工作流程示例Common n8n workflow patterns using Repair PDF Document.

电子邮件附件恢复

当……时，电子邮件触发器会触发。 PDF 附件已送达。
尝试处理附件失败，表明附件已损坏。
维修 PDF 文档会处理附件字节，然后继续处理或通过验证步骤进行确认。 success。

定期存档健康检查

计划触发器按周或按月运行。
已存档 PDFs 检索并验证其完整性。
维修 PDF 文档会对任何验证失败的文件运行，并将存档副本替换掉。

文件传输错误恢复

webhook 接收到 PDF 来自外部系统。
文件未能通过打开或验证检查。
维修 PDF 文档运行方式 Async 正在处理，以及正在恢复处理 success。

从托管服务器批量修复 URL 列表

“循环遍历项目”节点遍历文档列表。 URLs 从数据库导出。
维修 PDF 文档运行输入数据类型 URL 和 Async 为了提高可靠性，已启用处理功能。
每个修复后的文件都会以源记录 ID 作为文件名写入存储设备。

实用技巧

Always validate after repair, never assume success

Chain a follow-up open attempt or a metadata check after the node so the workflow can detect a file that is still broken and branch to a fallback path.

Decrypt before you repair, not after

If a file is both password-protected and corrupted, run a PDF4me unlock node first. Repair PDF Document does not remove encryption.

Enable Async for large or badly damaged files

Repair on a heavily corrupted or high-page-count PDF can take longer than a typical synchronous timeout allows.

Keep the original alongside the repaired copy

Store the source file next to the repaired output, at least until the repair is confirmed, so you can compare or retry with a different approach if recovery is incomplete.

Output File Name only affects the returned filename

It has no effect on the repair logic itself, so it does not need to match the original file name.

Notify rather than silently drop a failed repair

When validation after repair still fails, route the workflow to an alert instead of letting the file disappear from the process silently.

速查表

场地	价值
Action	`Repair PDF Document`
Input Data Type	`Binary Data`
Input Binary Field	`data`
Output File Name	`repaired.pdf`
Async Processing	`true (for large or badly damaged files)`
Binary Data Output Name	`data`
Credentials	`PDF4me API credential`

常见问题

What happens if a PDF cannot be repaired?+

The node attempts to fix structural errors and recover readable content, but repair is not guaranteed for every file. Severely damaged PDFs, such as truncated downloads or files with no recoverable cross-reference table, may fail to repair fully or at all. Add a validation step after the node so your workflow can detect a file that still failed to open and branch to a fallback.

Does Repair PDF Document decrypt password-protected files?+

No. Repair PDF Document fixes structural corruption, broken cross-reference tables, and formatting errors defined in the ISO 32000 PDF specification. It does not remove password protection or decrypt an encrypted PDF. If the source file is both corrupted and password-protected, unlock it first with a PDF4me unlock node, then run Repair PDF Document.

Can Repair PDF Document recover content that was deleted before the file was saved?+

No. The node recovers content that exists in the file but is unreadable due to structural corruption, such as a broken object table or malformed page tree. It cannot reconstruct content that was never saved to the file or was overwritten.

Do I need to enable Async for large or badly damaged PDFs?+

Async Processing lets the node run repair in the background instead of holding the workflow execution open, which helps with large files or when repair takes longer than a typical synchronous timeout allows.

How do I fix a PDF that says "the file is damaged and could not be repaired"?+

That message usually comes from a desktop PDF reader refusing to open a structurally broken file. Route the same file through the PDF4me Repair PDF Document node instead. It targets exactly this class of error, broken cross-reference tables, malformed object streams, and truncated trailers, and returns a rebuilt PDF the reader can open.