For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect your first data source

Connect an existing source and check that Jet Admin can access the records your app needs.

Before you start

Choose a provider in Data Sources. You need an account or credentials with access to the intended database, base, spreadsheet, or service. Decide whether the app needs to read data, update it, or call actions.

Connect the source

  1. Open Data and select Add Resource.

  2. Select your provider.

  3. Follow its connection guide to sign in or enter credentials. Select the database, tables, or files when prompted.

  4. If offered a connection mode, choose direct access or a sync connection. See Synced tables.

  5. Complete Add Resource and open the resulting resource.

  6. Select a table or collection. For action-based resources, select an available action instead.

Example: connect a public REST API

Search for Rest API in the resource picker.

REST API provider search result
Select Rest API from the filtered resource picker.

Enter a descriptive resource name and the base URL. This example uses the DummyJSON sample API, which provides fictional records and needs no credentials for this read request.

REST API setup with a resource name and https://dummyjson.com base URL
Enter the name and API base URL, then select Add resource when ready.

To reproduce the record list below, configure a GET request to /users?limit=2&select=id,firstName,lastName and use the transformation in Transform API responses. The connection form illustrates the name Public API example; the saved resource in the next screenshot is named Documentation API demo.

Verify the connection

Compare one known record with the source, including its identifier and a field value. Check that the expected fields appear. For a tool or action, provide the required inputs and inspect the response.

API Users collection showing Emily Johnson ID 1 and Michael Williams ID 2
The public API example returns two records with their IDs. This verifies read access.

If your app needs to write data, test one change on a demo record and confirm the result in the source. A successful read does not establish write access.

Troubleshooting

Symptom
Check

Sign-in or connection fails

Account, credentials, endpoint, and network access.

A table or file is missing

Granted access and resource selection.

Records are missing

Selected view, filters, and pagination.

A newly added field is missing

Continue with Manage app data or SQL queries and API requests.

Was this helpful?