Built-in no-code database: save, find and update records

A no-code database is already built into nana800: the database operation internal block saves, finds, updates and deletes records, with no server, logins or keys to connect. Records live in tables you name yourself, and each record is a set of fields such as a name, a phone number and an order status. Each operation costs $0.001, and your balance is topped up to $3.50 for free every month.

Build it in the builder
  • Block run: $0.001
  • Free every month: $3.50
  • No card needed

What you can do

  • Save leads, orders and customer replies one record at a time or as a batch from a list
  • Find a record by the exact value of a field, such as an email or an order number
  • Pick records from a date range, for example all orders from yesterday
  • Find several records at once by a list of values, such as a list of customer IDs
  • Change only the fields you need in one record or in every record found, the other fields stay as they were
  • Update a record or create it when it does not exist yet, handy for a customer card
  • Remember values between scheme runs: the last processed post, the previous price or an order status

Blocks in the builder

  • Built-in database

    Action · $0.001 per run

    Nine operations: create one or many records, get one or many, update one or many, update or create, delete one or many. Records are found by a field value, by a date range or by a list of values.

How to set it up

  1. 1

    Create a scheme and a trigger

    Create a scheme in the builder and add a trigger that brings the data: webhook for website leads or Telegram message from user to bot for bot messages. For the first test the button trigger is enough, it starts the scheme by hand.

  2. 2

    Add the database block

    Add the database operation internal block. Type a short Latin name into the database table name field, for example orders. You do not need to create the table first: it appears with the first record.

  3. 3

    Save your first record

    Choose the CREATE_ONE_OBJECT operation and write the record as JSON in the Input data field: field and value pairs in curly braces, for example {"name": "Anna", "phone": "+15551234567"}. Values can come from the trigger. Write dates like 2026-05-01T10:00:00Z so you can search records by date range later.

  4. 4

    Find or update a record

    In the next block choose GET_ONE_OBJECT or UPDATE_ONE_OBJECT, the KEY_VALUES_SEARCH search type, and put a field and its value into the Search by key and value field, for example the customer email. When updating, put only the fields you want to change into Input data.

  5. 5

    Turn the scheme on and test it

    Turn the scheme on, press the button trigger and open the block result: success_operation shows whether the operation worked, payload holds the record, objects_count tells how many records were touched. The reason of a failure is in error_text. When everything works, keep the scheme on.

Frequently asked questions

Each block operation costs $0.001, and one operation can create or change many records at once. An enabled scheme costs $0.0042 per hour. Your balance is topped up to $3.50 for free every month, no card needed. A scheme kept on around the clock for a month spends most of that on scheme hours.

No. The database is already part of nana800: no server, no login and password, no keys. Add the block and pick a table name.

No. Each scheme keeps its own records: another scheme of the same project will not find them, even with the same table name. If several schemes or your team need the data, keep it in Google Sheets or in your own PostgreSQL, MySQL or MongoDB database, which have their own blocks.

Choose GET_MANY_OBJECTS, turn sorting on (YES in the Item sorting field) and set limit count to the number of records you need. Without a limit the block returns one record. The same place sets the sort field and the order: ASC for ascending, DESC for descending. Without a field, records are sorted by creation time.

Choose the TIME_RANGE search type, name the date field and set the range bounds like 2026-05-01T00:00:00Z. The search works on dates that were saved in the same form: the database stores them as dates, not as text.

Records are read with the same block. Add a block with the GET_MANY_OBJECTS operation, turn the scheme on, start it with the button and open the block result: the records are in the payload field. If your team needs to see the data, save it to Google Sheets as well.

Build your first scheme for free

Sign-up is free and needs no card. Every month the balance is topped up to $3.50 for free, enough for about 3,500 runs of basic blocks.

Build it in the builder