What the data for this category looks like
Data related to energy storage yield is mainly sourced from public APIs of national power trading centers and local data collection systems of energy storage stations. Full records of the previous day are updated every early morning. Data formats are structured JSON or CSV. Each record includes fields such as station unique ID, total daily charge-discharge capacity, average peak-valley electricity price, operation and maintenance cost, and subsidy amount. Units: total charge-discharge capacity in kilowatt-hours, electricity price in yuan per kilowatt-hour, cost and subsidy in yuan, station unique ID has no unit.
What constraints do these characteristics impose on workflow orchestration
Data sources include public APIs and local collection systems, so workflows must distinguish call methods for the two types of data sources. Public APIs require API key authentication, while local collection needs to connect to station-specific communication protocols. The fixed daily update schedule requires workflows to set scheduled triggers, to avoid resource waste from frequent pulling of unchanged data. The structure with multiple fields and different units requires workflows to configure field mapping and unit conversion logic, to ensure unified format of parameters required for yield calculation. The structured data format requires workflows to include built-in data parsing nodes, to extract and clean fields and provide standardized input for subsequent yield calculation.
How to Set Configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
Scheduled Trigger Configuration | Trigger once daily at 02:00 | Matches the daily update cycle of energy storage yield daily reports, avoids repeated pulling of unchanged historical data |
HTTP Request Timeout | 300 seconds | Adapts to the response delay of public power trading APIs, prevents workflow execution failure caused by API timeouts |
Field Mapping Rules | Group by station ID, extract charge-discharge capacity, electricity price, and cost fields | Adapts to the structured data format with multiple records per energy storage station, facilitates subsequent execution of yield calculation logic |
Webhook Send Condition | Send only when the workflow completes execution without exceptions | Avoids pushing abnormal data to DingTalk, ensures accuracy of broadcast content |
BLOB File Export Configuration | Enable automatic generation of permanent download links | Supports exporting daily report results into downloadable files to meet user download needs |
Advanced Orchestration Permissions | Bind to specified team roles | Complies with permission management specifications for team collaboration, prevents unauthorized personnel from modifying workflow configurations |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- Phenomenon: The workflow returns a "field mismatch" error when calling the data parsing node. Cause: The mapping rules are not configured according to the field structure of energy storage data, resulting in failure to correctly extract the parameters required for calculation.
- Phenomenon: The message pushed by the DingTalk Webhook node contains no valid yield data. Cause: The
Webhook Send Conditionis not set to trigger only upon successful execution, resulting in the push of temporary data that has not completed calculation. - Phenomenon: The BLOB format daily report file returned by the HTTP node cannot generate a clickable download link. Cause: The automatic download link generation switch in the
BLOB File Export Configurationis not enabled, resulting in failure to generate a valid access address.
How to Confirm Proper Configuration
- Manually trigger the workflow once, check if the execution log contains prompts such as "execution successful" and "field matching completed".
- Check the sending records of the DingTalk Webhook to confirm that the message content includes yield-related data for energy storage stations.
- Trigger the workflow in the conversation interface, confirm that the returned message contains a clickable download link.
- Check the role permission configuration to confirm that the target role has access permissions for advanced orchestration.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.