Skip to content
Start in the sandbox
All connectors
Cognite Data Fusion logo

Cognite Data Fusion

Oil, gas & energy operations

Connect Cognite Data Fusion to the rest of your business, with the right person approving what changes and a record of every action.

20 ways to read, 4 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Cognite Data Fusion with Nexra

Connected, approved, proven.

The things teams do most with Cognite Data Fusion, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create assetassets.createApproval by rule
  • Create eventevents.createApproval by rule
  • List industrial assetsassets.listRead

Example flow

  1. Cognite Data Fusion · List industrial assetsassets.listDone
  2. Cognite Data Fusion · Create assetassets.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Cognite Data Fusion.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Cognite Data Fusion
  • Cognite Data Fusion's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Cognite Data Fusion assets, time series and datapoints, events, file metadata, sequences, relationships and data sets, with asset and event create and update.

Cognite Data Fusion API docs
Source actions
20
Destination actions
4
Data types
9

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

assets5
  • Create assetDestinationProvider duplicate protectionApproval before production

    Create one asset with a unique external ID.

  • Get assetSource

    Read one asset by ID or external ID, including metadata.

  • List industrial assetsSource

    Read asset identifiers, names and hierarchy from the authorised project.

  • Search or filter assetsSourceIncremental

    Filter assets (paged) or, with a text query, run Cognite's relevance search (one page).

  • Update assetDestinationProvider duplicate protectionApproval before production

    Set supplied asset fields by ID or external ID; metadata keys are added or overwritten.

datapoints2
  • Get latest datapointSource

    Read the latest datapoint for one time series, optionally before a time.

  • List datapointsSource

    Read raw or aggregated datapoints for one time series over a time range.

datasets1
  • List data setsSource

    List data sets the token can see.

events5
  • Create eventDestinationProvider duplicate protectionApproval before production

    Create one event (for example a maintenance or alarm record) with a unique external ID.

  • Get eventSource

    Read one event by ID or external ID.

  • List eventsSourceIncremental

    Filter events by type, asset, data set, time window or update time.

  • Search eventsSource

    Relevance search on event description, optionally filtered by type.

  • Update eventDestinationProvider duplicate protectionApproval before production

    Set supplied event fields by ID or external ID; metadata keys are added or overwritten.

files3
  • Get file metadataSource

    Read one file's metadata by ID or external ID.

  • List file metadataSourceIncremental

    Filter file metadata by name, directory, MIME type, asset or update time.

  • Search file metadataSource

    Relevance search on file names.

relationships2
  • Get relationshipSource

    Read one relationship by external ID.

  • List relationshipsSourceIncremental

    Filter relationships by source or target external IDs and types.

sequence rows1
  • List sequence rowsSource

    Read rows of one sequence, keyed by row number and column external ID.

sequences2
  • Get sequenceSource

    Read one sequence and its column definitions.

  • List sequencesSourceIncremental

    Filter sequences by asset, data set or update time.

timeseries3
  • Get time seriesSource

    Read one time series by ID or external ID.

  • List time seriesSourceIncremental

    Filter time series by asset, data set, unit or update time.

  • Search time seriesSource

    Relevance search on time series name and description.

Access and limits

Authentication
Provider-issued access token
Plans and access
Cognite Data Fusion project with an identity-provider access token. Token must target the configured cluster and project. Grant assetsAcl, timeSeriesAcl, eventsAcl, filesAcl, sequencesAcl, relationshipsAcl and datasetsAcl READ as needed; WRITE only on assetsAcl and eventsAcl, preferably scoped to a data set. This connector cannot control industrial equipment.
Test environment
Use an approved non-production project and synthetic assets.
Rate limits
Cognite throttles per project and returns HTTP 429; Nexra uses bounded retries with Retry-After. Datapoint requests are limited to 100 time series per request.
Pagination
Opaque nextCursor and limit, maximum 1000 items per page (10,000 sequence rows; datapoints use a per-series cursor).
Provider events
Cognite Data Fusion does not provide outbound webhooks for these classic resources. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Writes are limited to creating and updating assets and events. Deletes, datapoint inserts and deletes, sequence row writes, file uploads, relationship writes and data set changes are excluded.
  • The classic API has no single-call upsert.
  • File download links and file contents are not read; only metadata.
  • Access tokens from the identity provider expire (typically after one hour) and are not refreshed automatically; replace the stored token or use a long-lived service token.
  • Data modeling (instances, views) and synthetic time series queries are not implemented.
  • Text search endpoints return at most 1000 results and do not page.

Developer reference

  1. Create the Cognite Data Fusion credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Cognite Data Fusion, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Cognite Data Fusion docsAPI referenceCognite Data Fusion docsAuthenticationCognite Data Fusion docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/cognite-data-fusion and the Connections API.