Node-RED Automation
Use the built-in Node-RED environment to create custom automation flows connecting Maecos with external systems and event-driven logic.
Maecos includes a built-in Node-RED environment that enables low-code automation for custom integration and workflow scenarios. Node-RED provides a visual, flow-based editor where you can wire together Maecos events, external APIs, databases, and messaging systems.
When to use Node-RED
Node-RED is the right tool when you need:
Custom event-driven workflows that go beyond standard Maecos configuration
Integration with systems that don't have a dedicated Maecos connector
Data transformation or enrichment before writing to external systems
Scheduled tasks such as automated exports, cleanup routines, or batch processing
Prototyping integration logic before formalizing it
Common use cases
Sending a Microsoft Teams or Slack notification when a critical issue is created
Pushing completed checklist data to an external quality system
Enriching new issues with equipment metadata from a SCADA or historian system
Generating automated PDF reports on a schedule and distributing them via email
Syncing training completion data with an external HR system
Access
The Node-RED editor is accessible to authorized users through the Maecos administration interface. Access is typically restricted to system administrators and integration engineers.
Node-RED flows run within Maecos infrastructure and have access to internal APIs. Changes to flows take effect immediately — test in a non-production environment when possible.
Getting started
Access the Node-RED editor from the Maecos admin panel
Use Maecos-specific nodes (pre-installed) to subscribe to events and interact with platform data
Combine with standard Node-RED nodes for HTTP requests, email, file operations, and data transformation
Deploy your flow and monitor execution in the Node-RED debug panel
Best practices
Version control: Export your flows as JSON and store them in your organization's version control system
Error handling: Always include error-handling paths in your flows — external systems may be unavailable
Naming: Use clear, descriptive names for flows and nodes so other team members can understand the logic
Testing: Test flows with sample data before connecting to production systems
Monitoring: Use the Node-RED debug panel and Maecos logs to monitor flow execution
For questions about Node-RED capabilities or custom integration scenarios, contact your Maecos representative.
Last updated