Description
Overview
This COVID-19 testing data automation workflow streamlines the ingestion, filtering, and update of pandemic testing metrics for DACH countries in 2023. Designed as an orchestration pipeline, it targets data analysts and public health professionals requiring precise updates to centralized spreadsheets based on the European Centre for Disease Prevention and Control (ECDC) dataset.
The process is manually triggered and initiates with an HTTP request node that downloads the raw CSV file before parsing and filtering. It deterministically produces a dataset limited to Germany, Austria, and Switzerland, ensuring focused data management.
Key Benefits
- Automates COVID-19 data extraction and processing from an official public health CSV source.
- Applies precise country and date filters, retaining only 2023 data for DACH region integration.
- Generates unique composite keys facilitating reliable append or update operations on spreadsheets.
- Integrates seamlessly with Google Sheets using OAuth2 for secure, authenticated data management.
Product Overview
This automation workflow begins with a manual trigger node, allowing controlled execution on demand. Upon activation, it performs an HTTP GET request to fetch the latest COVID-19 testing CSV dataset from the ECDC public endpoint. The CSV file is then imported and parsed into structured JSON, with the first row treated as headers to map column data correctly.
Next, a unique identifier is constructed by concatenating the country code and year-week fields, enabling deterministic matching during subsequent spreadsheet updates. A filter node confines the dataset exclusively to records corresponding to Germany, Austria, and Switzerland, and only those dated within the year 2023. This targeted filtering reduces extraneous data processing and storage.
Finally, the filtered data is uploaded to a specified Google Sheets document and sheet called “COVID-weekly”. The upload operation intelligently appends new records or updates existing rows based on the unique key, using the Google Sheets OAuth2 credentials for authentication. The entire process executes synchronously within the workflow, with no explicit error handling configured beyond platform defaults.
A workflow annotation notes Google API rate limits, recommending batch splitting and delays for full dataset imports beyond this subset.
Features and Outcomes
Core Automation
This no-code integration pipeline accepts manual triggers to initiate a multi-step data flow, executing data download, parsing, and filtering based on defined criteria. It employs deterministic branching to isolate DACH countries and 2023 records using a filter node.
- Single-pass evaluation of CSV data into structured JSON.
- Deterministic filtering based on string operations and array membership checks.
- Unique key generation for exact row matching in downstream spreadsheet operations.
Integrations and Intake
The workflow integrates with an external HTTP API providing a public COVID-19 testing CSV dataset and with Google Sheets for data output. Authentication to Google Sheets is handled via OAuth2 credentials, ensuring secure access. The input payload is a CSV file parsed into JSON with header-based mapping.
- HTTP Request node retrieves official ECDC COVID-19 testing data CSV.
- Google Sheets node uploads data using OAuth2 authentication.
- Filter node restricts data by country code and year-week string prefixes.
Outputs and Consumption
The processed COVID-19 testing data is output as rows appended or updated in a Google Sheets document. The operation is synchronous and leverages the unique key field to avoid duplicates. Data fields include region, case counts, testing rates, and positivity metrics.
- Google Sheets spreadsheet named “COVID-weekly” as destination.
- Append or update operation keyed by composite unique identifier.
- Data columns cover epidemiological and demographic indicators.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow is initiated manually via the “Execute Workflow” button in the n8n interface, allowing controlled runs on demand rather than automated scheduling.
Step 2: Processing
The workflow retrieves the COVID-19 testing dataset with an HTTP GET request configured to download the response as a file. The CSV file is then imported and parsed to JSON format with headers recognized. Basic presence checks ensure correct header parsing before further processing.
Step 3: Analysis
A set node creates a unique key by concatenating the country code and year-week fields. A filter node applies exact criteria, retaining only records where the year-week starts with “2023” and the country code matches “DE”, “AT”, or “CH”. This filtering ensures the dataset matches the DACH region and current-year requirements.
Step 4: Delivery
The filtered dataset is uploaded to a Google Sheets document using OAuth2 credentials. The upload node performs an append or update operation, matching rows by the unique key to update existing data or add new entries. Data is formatted as user-entered cells for correct Google Sheets interpretation.
Use Cases
Scenario 1
Public health analysts require up-to-date COVID-19 testing data limited to the DACH region for weekly reporting. This automation workflow downloads, filters, and uploads the relevant data to a shared spreadsheet, providing timely structured datasets for analysis within a single execution cycle.
Scenario 2
Data teams aiming to maintain synchronized epidemiological spreadsheets benefit from this orchestration pipeline by reducing manual copy-paste errors. The workflow’s unique key mechanism ensures consistent updates and appends, improving data integrity across reporting periods.
Scenario 3
Organizations monitoring COVID-19 testing trends need filtered, focused datasets for Germany, Austria, and Switzerland. This automation workflow filters the large ECDC dataset to the 2023 DACH subset, minimizing storage and analysis overhead while maintaining data relevance.
How to use
Integrate this workflow into your n8n environment by importing the JSON configuration. Authenticate the Google Sheets node with your OAuth2 credentials linked to the target spreadsheet. Trigger the workflow manually via the “Execute Workflow” button to start data retrieval and processing. Expect filtered COVID-19 testing data for the DACH region in 2023 to be appended or updated in the designated Google Sheets document under the “COVID-weekly” sheet.
For full dataset ingestion beyond this subset, extend the workflow by adding batch splitting and wait nodes to respect Google API rate limits.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual downloads, filtering, key generation, and spreadsheet updates. | Single-step manual trigger initiates full automated pipeline. |
| Consistency | Prone to human error in filtering and key matching. | Deterministic filtering and unique key generation ensure consistent data updates. |
| Scalability | Limited by manual effort and error rate as dataset grows. | Scales with API rate limits; batch splitting needed for large datasets. |
| Maintenance | High; requires repeated manual data handling and validation. | Low; configured once, runs reliably with minimal intervention. |
Technical Specifications
| Environment | n8n workflow automation platform |
|---|---|
| Tools / APIs | HTTP Request (CSV download), Google Sheets API via OAuth2 |
| Execution Model | Manual trigger with synchronous processing |
| Input Formats | CSV file from HTTP response |
| Output Formats | Google Sheets rows with user-entered cell formatting |
| Data Handling | Transient JSON transformation with unique key generation and filtering |
| Known Constraints | Google API rate limits require batch throttling for full dataset imports |
| Credentials | Google Sheets OAuth2 account authentication |
Implementation Requirements
- Authorized Google Sheets OAuth2 credentials with access to the target spreadsheet.
- Network access allowing HTTP requests to the ECDC public data endpoint.
- Manual execution via n8n interface with capability to trigger workflows.
Configuration & Validation
- Confirm Google Sheets OAuth2 credentials are valid and have write permissions for the target document.
- Verify the HTTP Request node successfully downloads the CSV file from the ECDC source.
- Test workflow execution manually and check that filtered data appears correctly in the “COVID-weekly” Google Sheets tab.
Data Provenance
- Trigger node: manualTrigger initiates the workflow on demand.
- Download CSV node: HTTP Request fetches official COVID-19 testing CSV data from ECDC.
- Upload to spreadsheet node: Google Sheets node uses OAuth2 to append or update filtered data rows keyed by unique composite keys.
FAQ
How is the COVID-19 testing data automation workflow triggered?
The workflow is triggered manually by the user clicking “Execute Workflow” within the n8n interface, initiating a controlled data processing cycle.
Which tools or models does the orchestration pipeline use?
The pipeline uses an HTTP Request node to download CSV data, a spreadsheet file node to parse CSV, a set node to generate unique keys, a filter node to isolate specific records, and a Google Sheets node with OAuth2 for data upload.
What does the response look like for client consumption?
The workflow outputs filtered COVID-19 testing data as rows in a Google Sheets spreadsheet named “COVID-weekly”, formatted as user-entered cells and keyed by unique composite identifiers.
Is any data persisted by the workflow?
Data is transiently processed within the workflow nodes and permanently stored only in the target Google Sheets document; no other persistence is configured.
How are errors handled in this integration flow?
No explicit error handling or retries are configured; the workflow relies on n8n platform defaults for error propagation and failure handling.
Conclusion
This COVID-19 testing data automation workflow provides a reliable method for extracting, filtering, and updating epidemiological data specific to the DACH region for 2023. By combining manual control with deterministic filtering and unique key matching, it ensures consistent, accurate updates to a centralized Google Sheets document. The workflow maintains data integrity through structured processing but requires consideration of Google API rate limits for larger data volumes. Overall, it facilitates streamlined data management without persistent intermediate storage or complex error recovery configurations.
Reviews
There are no reviews yet.