Devbase Super Tool

Control SheetBase Pro / Devbase backend: projects, files, tables and @DBM-BLOCKS (via database).
Join our community

Overview

The Devbase Super Tool node provides comprehensive control over the SheetBase Pro / Devbase backend, enabling management of projects, files, Google Sheets data, and @DBM-BLOCKS within files stored in a database. It supports a variety of database actions such as listing, loading, saving, and deleting projects and files, manipulating code blocks within files, handling Google Sheets data (reading, appending rows, listing sheets), and managing webhooks. This node is beneficial for developers and automation users who need to integrate and automate workflows involving Devbase projects and Google Sheets, such as syncing project files, managing code blocks programmatically, or triggering workflows based on sheet events.

Use Case Examples

  1. List all Devbase projects associated with an API key.
  2. Load a full project including metadata and package files by its appId.
  3. Save or update a project with new metadata and package content.
  4. List and manipulate @DBM-BLOCKS within a file stored in the database, such as extracting or updating specific code blocks by name within HTML, CSS, or JavaScript files stored in Devbase projects, enabling modular code management via automation workflows in n8n.

Properties

Name Meaning
Database Action Specifies the action to execute on the SheetBase Pro / Devbase backend or local @DBM-BLOCK operations based on database files. Options include listing projects, loading/saving/deleting projects and files, managing blocks within files, handling Google Sheets data, and managing webhooks.
Project ID (appId) Identifier of the Devbase project, required for project and file related actions.
File Name Name of the file inside the project, required for file and block related actions.
Project Metadata (JSON string) JSON string containing project metadata such as name, description, prompt, created, and updated timestamps, used when saving a project.
Project Package (JSON string) JSON string representing the list of files in Devbase format, used when saving a project.
File Content (raw text) Raw UTF-8 text content of a file to be saved; converted to base64 for backend storage.
File Language / Type Helps the parser detect @DBM-BLOCK markers in files; can be auto-detected or set to HTML, CSS, or JavaScript.
Block Name Name of the block between @DBM-BLOCK and @DBM-END markers, used for block operations.
Block Content New content for a block, without markers; markers are re-generated on save.
Sheet Name Name of the Google Sheet tab, used for sheet data operations.
Max Rows Maximum number of rows to return from a sheet; 0 or empty means default limit.
Rows (JSON string [[...],[...]]) Rows to append to a sheet, provided as a JSON string of arrays.
Webhook Name Human-readable name for a webhook.
Webhook URL Target URL for the webhook, usually an n8n webhook URL.
Event Type Event type that triggers the webhook, depending on the Apps Script backend.
Target Sheet Optional sheet name filter for the webhook.
Filters (JSON string) Optional JSON string filters interpreted by the backend for webhook events.
Webhook ID Identifier of the webhook to delete.

Output

JSON

  • success - Indicates if the action was successful.
  • action - The database action performed.
  • appId - Project identifier involved in the action.
  • fileName - File name involved in the action, if applicable.
  • fileType - File type used for block parsing, if applicable.
  • totalBlocks - Total number of blocks found in a file, for listblocks_local action.
  • blocks - List of blocks with their names and lengths, for listblocks_local action.
  • name - Name of a block or webhook, depending on context.
  • content - Content of a block when retrieving a single block.
  • message - Informational message about the result of save or delete operations.
  • error - Error message if an operation fails.
  • availableBlocks - List of available block names when a requested block is not found.

Dependencies

  • An API key credential for SheetBase Pro / Devbase backend

Troubleshooting

  • Common issues include invalid or missing API key credentials, resulting in authentication errors from the backend.
  • Errors may occur if required parameters like appId, fileName, or blockName are missing or incorrect for the selected action.
  • Block operations may fail if the specified block name does not exist in the file, returning an error with available block names.
  • File content must be valid UTF-8 text; otherwise, saving files may fail or corrupt data.
  • Webhook creation requires a valid URL and event type; invalid inputs may cause backend errors.

Links

Discussion