Skip to main content
Setting up your first Data Feed in ~10 minutes — from blank to a Published feed an app can query.

What you’ll need

  • Access to a Workspace (any visibility level — Private is fine for your first attempt)
  • API credentials for a data source (Bearer token, API key, or Basic Auth)
  • A link to that source’s API documentation (Composer reads from it)

Step 1 — Open the Data Feed Composer

In Builder Mode, open Connect Data (the database icon in the left rail) and click + New. The first time you do this, a 3-step tutorial overlay walks you through the pattern. Data feed tutorial step 1, Connect to any data source: an example prompt asks Composer to connect to the CrowdStrike Falcon API, Composer asks for a Client ID and Secret, and a tip suggests pasting links to API documentation Click through to Done and you’ll arrive in the empty editor: Empty data feed editor: a Trigger node set to On Demand, with the note Please publish this data feed in order to trigger a run, a Data Request node with a GET method and an empty URL, and the Composer panel on the right

Step 2 — Describe the source

In the Composer panel on the right, type a one-liner about the source. The more concrete you are about endpoint and auth, the better the scaffold:
Hit Send. Composer:
  1. Sets the HTTP method to GET
  2. Fills in the URL
  3. Sets Authorization to Bearer Token
  4. Configures Pagination to Next Page Link
  5. Asks you for the actual token value

Step 3 — Enter credentials securely

Composer surfaces a Variables panel with named slots for any secrets it needs: Data feed tutorial step 2, Authenticate & Validate: the Variables panel with client_id (encrypted) and client_secret, and a tip about clicking the lock icon to encrypt sensitive values For each sensitive value:
  1. Paste the raw value into the field
  2. Click the lock icon next to the field
  3. The value is encrypted into your tenant’s secret store and the field shows ********
Don’t paste secrets into the Composer chat itself. Composer reads chat messages with its AI model; the Variables panel doesn’t.

Step 4 — Test the feed

Click the Test button at the bottom of the editor (next to the Draft / Published toggle). The feed runs once against the source and reports back inline:
  • ✅ On success — the response preview shows status, headers, and the first page of records pulled
  • ❌ On failure — an error appears inline (typically: 401 = bad token, 404 = wrong URL, 5xx = source is down)
The Test button works on the Draft. Once you Publish, the refresh icon in the editor toolbar (top right of the canvas) re-runs against the Published config. Verify the field shapes look right before moving on.

Step 5 — Refine

If something’s off, iterate via Composer:
Each refinement updates the Trigger / Data Request / Detail Request nodes on the canvas.

Step 6 — Configure the schedule

Click the Refresh data dropdown on the Trigger node and pick On Schedule. Then pick a Type: Schedule type dropdown showing Hourly, Every 4 Hours, Daily, Weekly, and Cron See Sync & Freshness for guidance on which cadence fits which data.

Step 7 — Publish

Click the Published chip at the bottom-left of the editor (it sits next to Draft as a toggle). The feed transitions from Draft → Published. Now:
  • It will run on the configured schedule
  • Studio apps in this workspace can wire it up as a data source
  • The Data Feeds counter on the workspace overview ticks up by 1

What to do next

Build your first app

Use the new Feed in a Studio app

Schema & Fields

Refine the field types and capture extra variables for Detail Requests

Sync & Freshness

Tune the schedule and troubleshoot stale data

Data Sources

Auth patterns and HTTP methods in depth