HttpRequest Automate

HttpRequest Automate streamlines alert management by automatically retrieving alerts from your Elastic API and sending timely email notifications. Scheduled to run at regular intervals, it ensures you never miss critical updates, enhancing your response efficiency and keeping your team informed.

7/8/2025
7 nodes
Medium
schedulemediumschedule triggernoopsplitinbatchesautomationapiintegrationcronlogicconditional
Categories:
Schedule TriggeredMedium Workflow
Integrations:
Schedule TriggerNoOpSplitInBatches

Target Audience

This workflow is ideal for:
- IT Administrators who need to monitor alerts from Elastic APIs and respond promptly.
- DevOps Teams looking to automate alert notifications to reduce manual intervention.
- Email Marketing Teams that require timely updates on system alerts for better communication.
- Business Analysts interested in tracking system performance and alert metrics for reporting purposes.

Problem Solved

This workflow addresses the challenge of manual alert monitoring by automating the process of fetching alerts from an Elastic API and sending email notifications. It ensures that relevant stakeholders are informed about critical alerts in real-time, thereby minimizing response time and improving operational efficiency.

Workflow Steps

  • Schedule Trigger: The workflow is triggered based on a specified schedule, allowing for regular checks on the Elastic API.
    2. Get Elastic Alert: It fetches alerts from the specified Elastic API endpoint, providing real-time data on system alerts.
    3. Response Check: The workflow checks if the response from the API is not empty. If there are no alerts, it proceeds to a No Operation node, effectively doing nothing.
    4. Loop Over Each Alert Items: If alerts are present, the workflow processes each alert individually. This is done using the SplitInBatches node to handle multiple alerts efficiently.
    5. Send Email Notification: For each alert, an email notification is sent to the specified recipient with details including the alert name, severity, timestamp, and message content.
    6. No Operation, end of loop: After processing all alerts, the workflow concludes the loop with a No Operation node, ensuring a clean end to the process.

    • Customization Guide

    Users can customize this workflow by:
    - Modifying the API Endpoint: Change the URL in the 'Get Elastic Alert' node to point to your specific Elastic API.
    - Adjusting Email Content: Customize the subject and body of the email in the 'Send Email Notification' node to fit your organization's tone and requirements.
    - Changing the Schedule: Alter the schedule settings in the 'Schedule Trigger' node to adjust how frequently the workflow checks for alerts.
    - Adding Conditions: Implement additional conditional logic in the 'Response is not empty' node to filter alerts based on severity or other criteria, ensuring only relevant notifications are sent.