Skip to content

Connect a data source

Connecting a data source in Ronja is a conversation, not a form. Clicking Add Connection opens a chat with Ronja, which asks what you want to connect and walks you through the right flow for that service.

  1. In the admin area, open Connections and click Add Connection. Ronja opens a fresh exploration and asks what service you’d like to connect.
  2. Name the service — “Connect Gmail”, “Connect our Postgres database”. You can also skip the Connections page entirely and just ask in any exploration.
  3. Follow the card Ronja renders: SaaS tools get a one-click sign-in card, databases get a secure credentials form.
  1. Ask Ronja to connect Gmail.
  2. Click Sign in with Google on the Connect Gmail (Read) card.
  3. Approve access in the popup window — the card shows “Waiting for authorization…” until you finish.
  4. Wait for the card to flip to Gmail (Read) connected. Ronja continues automatically.

Chat card titled Connect Gmail (Read) with a Sign in with Google button The one-click connect card Ronja renders for a built-in SaaS integration.

  1. Ask Ronja to connect your Postgres database.
  2. Fill in the secure credentials card: Host, Port, Database, Username, Password, and SSL mode. Password fields are marked “sensitive”; previously saved sensitive values display only as dots.
  3. Click Save Credentials. The values are stored as a secret — the sensitive values are never displayed again anywhere in the product, and Ronja the agent never sees them.
  4. Ask your questions — Ronja can now query the database live in the conversation.
  5. Ask Ronja to set up a scheduled import if you want the data synced into Ronja tables (this step requires Admin), then choose which tables to sync on the connection page.
  1. Open the connection from Connections or from its feature.
  2. Find the Sync Schedule card — “Minimum cadence is once per hour.”
  3. Choose Interval (run every N hours; new connections default to every 24 hours) or Cron (Hourly / Daily / Weekly / Monthly / Custom cron presets, with a timezone).
  4. Click Save Schedule.

Every connection belongs to a feature. Synced tables appear in that feature’s hub under Tables, marked with the Integration kind, ready to query in any exploration.

If a source’s authorization expires, the connection shows Re-auth needed and syncing stops — see Fix data issues.