Resources · n8n integration

n8n Execution Data nodeConfigure Execution Data in n8n.

Every execution looks alike in the list until something labels it. The n8n Execution Data node attaches your own key and value pairs to the run it sits in, so the Executions list can be searched by order number, customer or batch. One operation, keys of 50 characters, values of 512.

Try the Execution Data node on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Execution Data node do?

The Execution Data node writes metadata onto the execution it runs inside. Nothing is sent to an outside service: the key and value pairs you add travel with that run, and the Executions list can then be searched by them.

It is a core node, shipped with n8n, and it fires on every incoming item unless a branch keeps it out of the path.

Picture an order workflow that writes rows into Postgres and finishes quietly. Two days later somebody asks what happened to one specific order. Without metadata, the only way in is scrolling. With a saved field carrying the order reference, the run is one search away.

A second case: a support queue that posts messages into Slack. Saving the ticket reference and the assigned queue on each run turns the execution history into something a colleague can read without opening every run one by one.

Third case, the noisy one. A workflow that starts on a Webhook receives payloads from several senders at once. Saving the sender name and the payload type sorts the history into groups you can actually reason about when a batch fails.

When to reach for something else: this node writes metadata, it never reads it back. Pulling custom execution data during a run is the job of the Code node, which can retrieve it while the workflow is still going. If your goal is to store business data for later reporting rather than to find a run again, a database node is the right home for it.

The limits are worth knowing before you design around them. A key stops at 50 characters and a value at 512. Past that, n8n truncates to the maximum length and writes a log entry, so nothing breaks loudly, it just comes out shorter than you expected, and only the log says so. The node also has a single operation and no trigger of its own: a Schedule Trigger, a Webhook or a tool trigger has to open the workflow before it.

Actions

Which parameter does the Execution Data node expose?

The Execution Data node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Save Highlight Data (for search/review)

save

What you see in n8n

Notes & use cases

The only operation on this node writes your key and value pairs onto the current execution and lets the items continue unchanged. The run then appears in the Executions list carrying that metadata, which is what makes it findable afterwards.

Key parameters

  • Data to Save: a collection where Add Saved Field adds one key and value pair per click. The value is normally an expression pulled from the incoming item, such as {{ $json.orderId }}, so each run carries its own reference rather than a fixed label.
Use cases
tagging an invoicing run with the customer reference it processed, so the person handling the follow-up finds it from the Executions search box instead of asking whoever built the workflow.
Need help

Need help automating Execution Data with n8n?

A person reads every message.

FAQ

Execution Data in n8n: common questions

01Is the n8n Execution Data node included in every n8n plan?
Yes. Execution Data is a core node, shipped with n8n, so there is nothing to install and nothing extra to pay for on the n8n side. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed through Docker or npm, including the Community Edition under the Sustainable Use licence. A workflow built on one runs identically on the other, which means you can prototype on Cloud and move the same workflow to your own server later without touching this node.
02What do you need to set up before using it?
Nothing on the account side. This node has no credential and no Authentication selector, so there is no key to generate, no scope to approve and no connection to test. You drop it into a workflow and it works. What it does need is something upstream: the node runs on incoming items and does not open a workflow on its own, so a Schedule Trigger, a Webhook or the trigger of a tool has to start the run before it. It also needs at least one saved field, otherwise it has no metadata to attach.
03What are the limits of the Execution Data node?
Two hard limits sit on the data itself. A key is capped at 50 characters and a value at 512. If either one goes over, n8n truncates it to the maximum length and writes a log entry, so a long payload turns into a shortened one rather than an error you would notice straight away. Beyond that, the node exposes a single operation and sits at version 1, so an older workflow shows the same panel. It writes metadata for search and review, and it does not read that metadata back during the run.
04Execution Data node or Code node for custom execution data?
It depends on the direction you need. Execution Data is the write side: it saves key and value pairs onto the run so the Executions list can be searched and reviewed later, with no scripting involved. The Code node is the read side, since custom execution data can be retrieved with it while the workflow is still running. If the goal is to find a run again tomorrow, this node does it in a few clicks. If the goal is to branch on that data mid-run, the logic belongs in Code.
05n8n or Make for tagging runs like this?
The honest split is about hosting and cost model rather than features. n8n can be self-hosted through Docker or npm, or used on n8n Cloud, and the workflow is identical either way, which matters when execution metadata carries customer references you would rather keep on your own server. Make is a hosted platform with no self-hosting option and billing per operation, with its own visual logic that some teams find easier to read. Pick on where the data should live, what the volume costs you, and which canvas your team works faster on.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations