Database

Database sources let an organization ingest durable records from a read-only database connection.

Create and manage database sources from the organization dashboard under Integrations > Database.

When to use a database source

Use a database source when records already live in an operational database and should become available to Achiral memory.

Database sources are best for structured records such as orders, accounts, cases, events, documents, inventory, usage records, or internal product state.

Create a source

Select New database source, then provide:

• Source name: a human-readable name for the source.
• Database type: MongoDB, PostgreSQL, or MySQL.
• Database name: the database to read from.
• Collection or table: the specific record set Achiral should read.
• Read-only connection string: a credential with the narrowest possible read access.
• Memory event type: the event label assigned to records from this source.

Use Validate to check the source before creating it. Use Preview rows to inspect sample records.

Advanced read settings

Advanced settings expose lower-level read controls:

• Read operation: the database read operation to run.
• Read filter: JSON that scopes which records should be read.

Keep filters narrow. A database source should ingest only the records that are useful for organization memory.

Security

Use a read-only credential. Limit access to the database, table, collection, and fields that Achiral needs.

Prefer network allow-listing and TLS where supported. Rotate connection strings when access changes or a source is retired.

Operations

Database sources can be paused, resumed, or archived from the Database tab.

• Active sources are available for ingestion.
• Paused sources remain configured but do not run scheduled ingestion work.
• Archived sources are retired and should not be used for new ingestion.

Troubleshooting

If validation, preview, or ingestion fails:

• Confirm the connection string uses a read-only credential.
• Confirm the database and collection or table names are correct.
• Confirm the read filter is valid JSON.
• Check whether network policy, TLS, or allow-listing is blocking the connection.

Related pages

• Connectors — authorize popular apps and tools.
• API sources — read records from APIs that are not available as connectors.
• Organization — manage organization settings and access.