Create a database

Plan availability #

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

Choose what to store #

A database holds tables. Each table holds records, and each column defines one kind of information. For a customer request table, you might use Name, Request, Priority, and Resolved columns.

Chatigram Database is built into your organization. It is separate from an external MySQL or PostgreSQL connection.

Create the structure #

1. Open Databases and create a database with a clear purpose, such as Customer requests.
2. Open the database editor and add a table, such as Requests.
3. Add the columns your process needs.
4. Create a small test record before wiring workflows to the table.

If database creation is unavailable, check the plan table above and your role in the organization. An external integration connection does not grant access to built-in database features.

Pick the right column type #

Use Text for identifiers that must preserve leading zeroes. Use Number when you need numeric comparisons. Define what an empty value means for your process.

Use the database editor #

The editor lets you prepare changes to tables, columns, and several rows before saving them together. Choose a table, use Columns to define its fields, and use Data to work with its records. Keep names clear and consistent so colleagues can map workflow values correctly.

1. Add the table and columns you need.
2. Open Data and enter several example rows. Check numbers and true/false values against the column types.
3. Review your unsaved changes. Use Undo or Redo while preparing the draft when you need to correct an edit.
4. Save to open Review changes. Check the created, updated, and deleted items, especially any data-loss warnings.
5. Choose Save changes to apply the reviewed batch together in a single transaction, or Cancel to return without applying it.

Saving several rows in the editor is different from calling the REST API once per row. Editor Undo is for the editing draft; do not rely on it to recover records after a committed deletion.

Work with records #

Add or edit records in the table. Check the table and row carefully before deleting information. Deleting a table or database can remove many records at once and can break workflows that depend on it.

Records have system identifiers, including a row ID and creation time. Workflows can use those values to retrieve or target a specific row.

Keep workflows aligned #

After changing a table’s columns, reopen the workflows that use it and review their selections, filters, and value mappings. A renamed column can retain its identity, but deleted or changed resources still need attention.

Continue with database workflows for insert, search, update, delete, and trigger patterns.

Connect your data to other tools #

• Import tables from JSON to build a reusable table structure.
• Enable the database REST API to connect business software, generate a key, and download your database’s OpenAPI specification.
• Choose a database event trigger to react inside a workflow, notify an external service, or request monitoring through a supported AI connection.