Autom8 AI Docs
  • Introduction to A8I
  • Quick Start
    • Your First Workflow
  • Workflows Explained
    • Create and Run a Workflow
    • Workflow Components
    • Executions
    • Manual, Partial, and Production Executions
    • Workflow Executions
    • All Executions
    • Custom Execution Data
    • Debug and Re-run Past Executions
    • Tags
    • Export and Import Workflows
    • Workflow Templates
    • Workflow Sharing
    • Workflow Settings
  • Flow Logic
  • Data
    • Data Structure
    • Data Flow Within Nodes
    • Transforming Data
    • Processing Data with Code
    • Data Mapping
  • AI Assistant
  • Glossary
  • Integrations
  • Build an AI Chat Agent in Autom8 AI
Powered by GitBook
On this page
  1. Workflows Explained

Custom Execution Data

Autom8 AI allows you to attach custom metadata to each workflow execution. This is useful for tracking internal state, tagging runs, or filtering execution logs.

You can set custom data using the Code Node or Execution Data Node, and then use it:

  • To filter execution logs

  • Inside the workflow for conditional logic

  • For debugging and context tracking

Setting Custom Data in the Code Node

You can define custom key-value pairs using JavaScript or Python within the Code Node.

Set a single key/value:

javascriptCopyEdit$execution.customData.set("key", "value");

Set multiple values at once (overwrites existing):

javascriptCopyEdit$execution.customData.setAll({
  "userId": "123",
  "source": "webhook"
});

Accessing Custom Data in the Workflow

To retrieve previously set values during the same execution:

Get the full custom data object:

javascriptCopyEditconst data = $execution.customData.getAll();

Get a specific value:

javascriptCopyEditconst value = $execution.customData.get("key");

Limits

  • Keys and values must be strings

  • Max key length: 50 characters

  • Max value length: 255 characters

  • Max items per execution: 10

Note: The Execution Data Node can set data but cannot retrieve it.

PreviousAll ExecutionsNextDebug and Re-run Past Executions

Last updated 5 days ago