🔍 Summary
This configuration sets up an automated daily refresh of Scope 3 emissions data from the Scope3 platform. The imported data is written to a centralised emissions lookup table.
Job Frequency: Daily
Scheduled Time: 4 AM
Lookback Window: 1 day
Target Table:
scope3_data_emissions
⚙️ Jobs Configuration
🛠️ Job: Scope3 Emissions Data Import
Field | Value |
Feed |
|
Status |
|
Label |
|
Lookback | 1 day |
First Run Hour | 4 AM |
Poll Frequency | 24 hours |
Lookback Window | 0 |
🎯 Target
Priority | Table | Description | Update Mode | Create Target |
1 |
| Scope3 Emissions Import | refresh | true |
🔐 Connection Settings
Key | Description | Type | Required | Notes |
| Scope3 Access Client ID | text | ✅ Yes | Used for API authentication |
| Scope3 Access Client Secret | text | ✅ Yes | Confidential API credential |
Host: (Empty — assumed predefined in connector)
Token / Secret / Password / Username: (Not used in this integration)
Connection Description:
Scope 3 Emissions Connection
📐 Dimensions & Metrics
None declared at this stage. The structure is handled entirely via the refresh operation of scope3_data_emissions.
🔗 Datasource Joins
None required for this job. The emissions data appears to be self-contained and does not join to any metadata or reference tables in the starting configuration.