N8N Security Controls API Layer
Budget: $250 – $750 AUD
I’m building a light-weight API layer on top of several security controls and need it wired through n8n. The goal is to pull telemetry from my EDR, MFA, and DLP platforms, funnel everything into n8n workflows, and expose the results through carefully-designed Express endpoints or Direct to Firestore DB.
Here’s what I need built and handed back:
• A set of n8n workflows that call each product’s native API, normalise the payloads, and forward them to an internal collection queue.
• An Express server that acts as the single entry point. Each endpoint should return aggregated data in JSON and trigger automated report generation when requested.
• Reporting jobs (inside n8n) that run on a schedule or via endpoint hit, producing summary reports in a common format (CSV and JSON).
Key details
– Integration method: Direct Firestore, or Express endpoints (not generic webhooks).
– Functionality focus: data aggregation, live data, and automated reporting; real-time monitoring is out of scope for this phase.
– The code must be clearly commented, environment-variable driven, and ready to drop into my existing Docker stack.
I’ll test the deliverable by pointing it at staging instances of the three tools and confirming the aggregation output and scheduled reports. Once it passes those checks, we’re done.
Here’s what I need built and handed back:
• A set of n8n workflows that call each product’s native API, normalise the payloads, and forward them to an internal collection queue.
• An Express server that acts as the single entry point. Each endpoint should return aggregated data in JSON and trigger automated report generation when requested.
• Reporting jobs (inside n8n) that run on a schedule or via endpoint hit, producing summary reports in a common format (CSV and JSON).
Key details
– Integration method: Direct Firestore, or Express endpoints (not generic webhooks).
– Functionality focus: data aggregation, live data, and automated reporting; real-time monitoring is out of scope for this phase.
– The code must be clearly commented, environment-variable driven, and ready to drop into my existing Docker stack.
I’ll test the deliverable by pointing it at staging instances of the three tools and confirming the aggregation output and scheduled reports. Once it passes those checks, we’re done.
Related categories:
JavaScript
Data Processing
JSON
Docker
Backend Development
API Development
API Integration
Microservices
Data Collection
n8n