← All N8N workflows
Data & databasesCronPostgresEdit FieldsTwilio

Monitoring and alerting

Configured with Cron, Postgres, Twilio. Review the connections and setup before adapting this template.

Workflow preview
TriggerCronCronData storePostgresPostgresMessagingTwilioTwilioTransformSetEdit FieldsData storePostgres1Postgres

Node categories in this workflow

  • Trigger
  • Data store
  • Messaging
  • Transform

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
CronTriggerCronSee node parameters
PostgresData storePostgresexecuteQuery
TwilioMessagingTwilioSee node parameters
SetTransformEdit FieldsSee node parameters
Postgres1Data storePostgresupdate

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • postgres
  • twilioApi

Workflow notes

Monitoring and alerting

Monitoring and alerting

Purpose and structure

This folder contains the Monitoring and alerting workflow. Its executable nodes use cron, postgres, set, twilio. 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

Cron

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/Twilio/0842_Twilio_Cron_Send_Scheduled.json MIT; preserve source notices.

More in Data & databases