Get Document from PDF4me in n8n

Get Document From Pdf4me is a PDF4me node action in n8n that retrieves a document PDF4me already holds. Use it to collect the result of an earlier processing step, pull a stored file back into a later workflow run, or finish a callback-based job by fetching what was produced.

What this node does

PDF4me: Get Document From Pdf4me is a retrieval utility, not a transformation. It takes just two inputs, a File Name and a Callback URL, and both are required. It returns the stored file unchanged along with its name, size, and MIME type, so anything you need done to the document happens in a separate action chained after it.

Authenticating Your API Request

Every PDF4me node in n8n requires a valid Credential to connect with. Create or select one that holds your PDF4me API key so the workflow can authenticate retrieval requests securely.

Get your API Key

Important Facts You Should Not Miss

Both fields are genuinely required

File Name and Callback URL each show a validation warning while empty. Unlike most PDF4me nodes there is no optional input to fall back on, so the node will not run until both are set.

It retrieves, it does not transform

The file comes back as stored, with its original MIME type reported. Converting, compressing, or securing it is a separate action placed after this one.

The file name must match exactly

Carry the name forward from the producing step with an expression. Retyping it by hand is the most common reason a retrieval finds nothing.

The PDF4me node in n8n with Action set to Get Document From Pdf4me, showing only two input fields, File Name and Callback URL, both marked with required validation warnings — The whole panel is four fields. The red borders on File Name and Callback URL are the node telling you both must be filled in before it will execute.

Retrieval vs Processing Actions

Question	Get Document From Pdf4me	A processing action
What it needs	A file name and a callback URL	A source file plus operation settings
What it changes	Nothing, the file is returned as stored	The document content or format
Where it sits	After the work, to collect the result	In the middle, doing the work
What comes back	The stored file plus its metadata	A newly produced document
Typical use	Finishing a callback-based job	Converting, securing, or editing

What Parameters Does Get Document From Pdf4me Need?

Parameter	Required	What it does	Example
Credential to connect with	Required	The PDF4me account credential the node authenticates with.	`PDF4ME account`
Action	Required	The action this node performs. Select Get Document From Pdf4me.	`Get Document From Pdf4me`
File Name	Required	Exact name of the document to retrieve, including its extension. Best supplied by an expression carrying the name from the producing step.	`document.pdf`
Callback URL	Required	Reachable URL used for callback-based retrieval. The node shows a validation warning until it is set.	`https://example.com/callback`

This node has an unusually small surface. There is no input-type selector, no output naming field, and no advanced options collection, which is why every parameter above is marked required rather than conditional.

Output

Field	Type	What it contains
success	`Boolean`	Whether the retrieval request completed. Branch on this before using the file.
message	`String`	Human-readable status text, including error detail when something went wrong.
fileName	`String`	Name of the retrieved document.
mimeType	`String`	Content type of the retrieved file, which tells you what you actually got back.
fileSize	`Number`	Size of the retrieved document in bytes.
docName	`String`	Document name reference, matching fileName.
retrievalCompleted	`Boolean`	Confirmation that retrieval finished. Worth checking alongside success.

The document itself is returned as binary data alongside these fields, ready to write to storage, attach to an email, or pass into another PDF4me action.

How Do I Set Up Get Document From Pdf4me in n8n?

Add the PDF4me node to your workflow and set Action to Get Document From Pdf4me.
Select your PDF4me credential, or create one and paste your API key.
Set File Name to the exact stored name, ideally through an expression that carries it from the earlier step.
Set Callback URL to a reachable endpoint. The node will not execute while it is empty.
Execute the node.
Check success and retrievalCompleted in the response with an IF node.
Confirm mimeType matches what you expect before handing the file to a step that assumes a format.
Route the binary document to storage, email, or the next PDF4me action.

Typical Setups

Workflow ExamplesCommon n8n workflow patterns using Get Document From Pdf4me.

Collect the result of a long job

An earlier action starts work on a large document.
Get Document From Pdf4me collects the finished file by name.
The workflow continues without holding a connection open.

Fetch then transform

The stored file is retrieved unchanged.
A second PDF4me action compresses or secures it.
Retrieval and processing stay cleanly separated.

Re-send on request

A recipient asks for a document that was generated earlier.
The workflow retrieves it by its stored name.
It is emailed again without regenerating anything.

Guard the handoff

An IF node checks success and retrievalCompleted.
mimeType is compared against what the next step expects.
A mismatch alerts instead of failing deeper in the chain.

Practical Tips

Pass the file name by expression

Carrying the name from the step that produced the document removes the single most common source of failed retrievals.

Check both success flags

success and retrievalCompleted are separate fields. Testing both is cheap and catches partial outcomes.

Use a reachable callback URL

The field is required and the value should be an endpoint that genuinely accepts requests, not a placeholder left in from testing.

Verify mimeType before assuming a format

A downstream PDF step that receives something else will fail confusingly. One comparison up front avoids that.

Do not expect transformation here

If the retrieved file needs changing, chain the relevant action after this one rather than looking for settings this node does not have.

Keep names unique and predictable

Retrieval is by exact name, so a naming convention set at generation time makes this node trivial to wire up later.

Cheat Sheet

Field	Value
Action	`Get Document From Pdf4me`
File Name	`document.pdf`
Callback URL	`https://example.com/callback`
Credentials	`PDF4ME account`
Success check	`success and retrievalCompleted`
Format check	`mimeType`

Common Questions

What does Get Document From Pdf4me actually do?+

It fetches a document that PDF4me already holds rather than transforming anything. It is a retrieval utility, so it belongs at the point in a workflow where a file produced earlier needs collecting, not where a document is created or converted.

Why does the node require a callback URL?+

The action is built around callback-based retrieval, the pattern where a longer running request reports completion to an endpoint instead of holding a connection open. Both File Name and Callback URL are marked required in the node panel, so nothing runs until a reachable URL is supplied. n8n can host such an endpoint through a Webhook node.

What file name should I enter?+

The exact name of the document as it was stored, including the extension. A near miss does not resolve to a different file, it simply finds nothing. Carry the name forward from the earlier step with an expression rather than retyping it.

How do I confirm the retrieval worked?+

The response returns a success boolean and a retrievalCompleted flag, alongside fileName, fileSize, and mimeType. Branch on those before using the file so a failed retrieval raises an alert instead of passing an empty item down the chain.

Does this node convert or modify the document?+

No. It returns the stored file as it is, with its original content type reported in mimeType, following the standard MIME type conventions. If the document needs converting, compressing, or securing, chain the relevant PDF4me action after this one.

Update Hyperlinks Annotation

The other utility action in the same PDF4me node group.

Protect Document

A natural next step once the retrieved file is about to be distributed.

Extract Form Data From PDF

Read data out of the document you just retrieved.

n8n Getting Started

Set up the PDF4me credential this and every other node depends on.