Supabase Memory icon

Supabase Memory

AI Tool Agent Memory with Supabase
Join our community

Actions5

Overview

This node interacts with a Supabase database to manage workflow execution data, specifically allowing users to update the status of an existing workflow execution record. It is useful in scenarios where workflows are monitored or orchestrated externally and their execution states need to be tracked or updated dynamically. For example, after a workflow completes or fails, this node can update its status along with final output data and any error messages, enabling downstream processes or dashboards to reflect the current state accurately.

Properties

Name Meaning
Status The current status of the workflow execution. Options include "in_progress", "completed", "failed".
Final Output The final output of the workflow execution in JSON format.
Error Message An optional error message describing why the workflow execution failed (if applicable).
Workflow Execution ID The numeric identifier of the workflow execution record to update.

Output

The node outputs a JSON object containing:

  • sessionId: A session identifier string associated with the operation.
  • Other fields returned from the Supabase client update operation, which typically include confirmation or details of the updated workflow execution record.

The output does not include binary data.

Example output structure:

{
  "sessionId": "some-session-id",
  "id": 123,
  "status": "completed",
  "finalOutput": { /* JSON object */ },
  "errorMessage": null
}

Dependencies

  • Requires a Supabase API key credential and Supabase URL configured in n8n credentials.
  • Uses a Supabase client utility internally to perform database operations.
  • The node depends on the external Supabase service for storing and updating workflow execution data.

Troubleshooting

  • Missing Session ID: If the session ID is not provided for update operations, the node will throw an error. Ensure the correct workflow execution ID and session ID are supplied.
  • Invalid JSON Input: The finalOutput property must be valid JSON. Malformed JSON will cause parsing errors.
  • Supabase Connection Issues: Errors related to authentication or network connectivity with Supabase may occur. Verify that the API key and URL are correctly set and that the Supabase service is reachable.
  • Workflow Execution ID Not Found: If the specified workflow execution ID does not exist in the database, the update will fail. Confirm the ID is correct.

Links and References

Discussion