get elastic alert and send email notification and receive schedule events
Configured with HTTP Request, Schedule Trigger, Loop Over Items. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Get Elastic Alert | Web / API | HTTP Request | See node parameters |
| Send Email Notification | Web / API | HTTP Request | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Response is not empty | Routing | If | See node parameters |
| No Operation, do nothing | Routing | No Op | See node parameters |
| Loop Over Each Alert Items | Routing | Loop Over Items | See node parameters |
| No Operation, end of loop | Routing | No Op | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
get elastic alert and send email notification and receive schedule events
get elastic alert and send email notification and receive schedule events
Purpose and structure
This folder contains the get elastic alert and send email notification and receive schedule events workflow. Its executable nodes use httpRequest, if, noOp, scheduleTrigger, splitInBatches. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0624_HTTP_Schedule_Send_Scheduled.json MIT; preserve source notices.