Integrations / MySQL
MySQL
Popular open source relational database
Basic auth
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A MySQL instance Telara can reach.
A dedicated user that can connect to the database Telara should see. Prefer that over root.
Vendor setup
Get the credential
1
Create a login
Create a user with CONNECT on the target database and the least privilege needed to read schemas.
2
Paste in Telara
Settings → Integrations → MySQL. Enter host, port, database name, username, and password. Turn on TLS if the server requires it.
In Telara
Connect in Telara
Basic auth
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
Fields Telara asks for
- Username
- Password
- Host
- Port
- Database
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Table | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Table | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Table.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Security groups and private IPs are the usual failure.
A user that can log in but cannot see schemas produces an empty list, not an auth error.