Supabase Memory icon

Supabase Memory

AI Tool Agent Memory with Supabase
Join our community

Actions5

Overview

This node integrates with a Supabase backend to manage AI tool agent memory and workflow execution data. Specifically, for the Workflow Execution - Retrieve operation, it fetches stored workflow execution details from Supabase using a provided session ID.

Typical use cases include:

  • Retrieving the state and metadata of a previously executed workflow for auditing or continuation.
  • Accessing detailed execution traces, planner outputs, and final results of workflows managed by AI agents.
  • Debugging or monitoring workflow executions by fetching their stored status and error messages.

For example, after storing a workflow execution's data during an automation process, you can later retrieve it by specifying the session ID to analyze the workflow’s progress or outcome.

Properties

Name Meaning
Session ID The unique identifier for the workflow execution session to retrieve. Must be provided.

Output

The output JSON object contains the retrieved workflow execution data merged with the sessionId. Its structure includes (but is not limited to) the following fields:

  • plannedWorkflowId: Numeric ID of the planned workflow (or null if none).
  • originalUserQuery: The original query string that triggered the workflow.
  • plannerOutput: JSON object representing the planner agent's output.
  • executionTrace: JSON object containing the trace of the workflow execution.
  • status: Current status of the workflow execution (e.g., "in_progress", "completed", "failed").
  • finalOutput: JSON object with the final output of the workflow execution.
  • errorMessage: String describing any error message if the workflow failed.

The output is structured as an array of items, each with a json property holding the above data and a pairedItem reference to the input item index.

No binary data is produced by this operation.

Dependencies

  • Requires a configured Supabase backend accessible via URL and API key credentials.
  • The node depends on a Supabase client utility internally to perform database operations.
  • Users must provide valid credentials for Supabase API access in n8n.
  • The node uses UUID generation for session IDs when storing data but requires explicit session ID input for retrieval.

Troubleshooting

  • Missing Session ID Error:
    If the session ID is not provided for a retrieve operation, the node throws an error indicating that the session ID is required. Ensure you supply a valid session ID to fetch workflow execution data.

  • Invalid Credentials or Connection Issues:
    Failure to connect to Supabase due to incorrect URL or API key will cause errors. Verify your Supabase credentials and network connectivity.

  • Malformed JSON Inputs:
    Although not directly relevant to retrieval, other operations expect JSON-formatted inputs. Invalid JSON may cause failures in those contexts.

  • Empty or No Data Returned:
    If no workflow execution matches the given session ID, the output may be empty or null. Confirm the session ID corresponds to existing stored data.

Links and References

Discussion