Reference · Nodes
Data & Storage integrations and nodes
Data and storage nodes read and write the places your records and files live: spreadsheets such as Google Sheets and Airtable, databases such as PostgreSQL, MySQL and MongoDB, and file stores such as Google Drive, Dropbox and AWS S3. The category also holds BusyBot's own Knowledge Base and Search Knowledge Base nodes, which add documents to a knowledge base and search it from inside a workflow.
54 nodes — 47 actions and 7 triggers. Every page documents the shipped node: real parameters, real outputs, real error behaviour.
Spreadsheets, databases, files and knowledge
Spreadsheets and table databases. Google Sheets reads, appends, updates and upserts rows. Airtable, Baserow, NocoDB, SeaTable and Grist do the same for their tables.
SQL and warehouses. PostgreSQL, MySQL and Oracle SQL run selects, inserts, updates, upserts and raw parameterized queries. Snowflake and Google BigQuery run queries and insert rows into warehouse tables, and TimescaleDB, QuestDB and CrateDB cover time-series workloads.
Document and key-value stores. MongoDB, AWS DynamoDB, Google Cloud Firestore, Redis and Elasticsearch.
Files. Google Drive, Dropbox, Box, Microsoft OneDrive and Microsoft SharePoint upload, download, search and share. AWS S3, S3 (for any S3-compatible service), Google Cloud Storage and Microsoft Azure Storage manage buckets and objects.
Knowledge. Knowledge Base creates knowledge bases and adds, replaces or removes their documents. Search Knowledge Base sends an AI research agent into a knowledge base and returns its findings and an answer.
Triggers
Polling: Google Sheets Trigger, Airtable Trigger, SeaTable Trigger, Google Drive Trigger and Microsoft OneDrive Trigger. Webhook: Box Trigger and AWS SNS Trigger.
Example workflows
- Copy new Drive files to S3. Google Drive Trigger fires when a new file is created in a folder, Google Drive downloads it, and AWS S3 uploads it to a bucket.
- Keep a knowledge base current. Dropbox searches for PDFs and downloads each one, and Knowledge Base adds it to a product manuals knowledge base.
- Sheet rows into Postgres. Google Sheets Trigger fires when a row is added, Edit Fields renames the columns to match the table, and PostgreSQL upserts each row with ON CONFLICT so a re-run does not duplicate it.
Actions
Triggers
Nodes that START a workflow when something happens.
Frequently asked questions
Which data sources can start a workflow?
Google Sheets Trigger, Airtable Trigger and SeaTable Trigger poll for new or updated rows. Google Drive Trigger and Microsoft OneDrive Trigger poll for new or changed files and folders. Box Trigger receives webhooks for file, folder and comment events, and AWS SNS Trigger starts a run when a message is published to an SNS topic. The databases have no trigger of their own, so a workflow that reads new database rows usually runs on a schedule.
What credentials do database nodes need?
Connection details for that database: PostgreSQL and MySQL take a host, port, database, user and password, Oracle SQL a connection string, and Snowflake an account, a warehouse and either a password or a private key. Google Sheets, Google BigQuery and Google Cloud Firestore accept either an OAuth2 credential or a Google API service account. Knowledge Base and Search Knowledge Base need no credential, because they work on your own BusyBot knowledge bases.
How do these nodes work with AI and core nodes?
Read rows, process each one, and write the result back. Google Sheets reads all rows from a sheet, an AI node such as Gemini Structured Output extracts fields from a free-text column, and Google Sheets updates the matching rows. For documents, Knowledge Base adds a file from binary data and indexes it the way a manual upload would, so agents and chats pointed at that knowledge base can search it.
Last reviewed . Spotted something wrong? Tell us.