Skip to content

CEA Alert Tool Workflow

This workflow creates and manages CEA (Customer Engagement Alert) alerts by inserting alert records into a database and updating user engagement status. It serves as a centralized tool for triggering alerts with specific reasons, priorities, and profit snapshots while maintaining proper tracking in the user database.

Purpose

No business context provided yet — add a context.md to enrich this documentation.

How It Works

  1. Receives Alert Data: The workflow is triggered by another workflow with alert details including phone number, reason, priority, summary, and profit snapshot
  2. Creates Alert Record: Inserts a new CEA alert into the ceaAlerts table with status set to 'open'
  3. Updates User Status: Flags the corresponding user record in youthEntrepreneursReal table with alert timestamp, reason, and engagement status
  4. Returns Confirmation: Outputs a formatted message confirming the alert creation with relevant details

Workflow Diagram

graph TD
    A[When Executed by Another Workflow] --> B[insertCeaAlert]
    B --> C[flagUserRecord]
    C --> D[setOutput]

Trigger

Execute Workflow Trigger: This workflow is designed to be called by other workflows, not triggered directly. It expects the following input parameters: - phoneNumber: Target user's phone number - reason: Reason for the alert - priority: Alert priority level - summary: Alert summary description - profitSnapshot: JSON data containing profit information

Nodes Used

Node Name Type Purpose
When Executed by Another Workflow Execute Workflow Trigger Receives input parameters from calling workflow
insertCeaAlert PostgreSQL Creates new alert record in ceaAlerts table
flagUserRecord PostgreSQL Updates user record with alert information
setOutput Set Formats and returns confirmation message

External Services & Credentials Required

PostgreSQL Database

  • Credential Name: PostgresOnSupabase
  • Purpose: Database operations for alert management and user tracking
  • Required Permissions: INSERT and UPDATE access to ceaAlerts and youthEntrepreneursReal tables

Environment Variables

No environment variables are directly referenced in this workflow. All configuration is handled through the PostgreSQL credential.

Data Flow

Input Data

1
2
3
4
5
6
7
{
  "phoneNumber": "string",
  "reason": "string", 
  "priority": "string",
  "summary": "string",
  "profitSnapshot": "object/array"
}

Output Data

1
2
3
{
  "output": "CEA alert created (ID: {alertId}) for {phoneNumber}. Reason: {reason}. Priority: {priority}."
}

Database Operations

  • ceaAlerts Table: New record with auto-generated ID and timestamp
  • youthEntrepreneursReal Table: Updated with alert timestamp, reason, and engagement status

Error Handling

This workflow does not implement explicit error handling. Database constraint violations or connection issues will cause the workflow to fail at the respective PostgreSQL nodes.

Known Limitations

  • No input validation for required parameters
  • No error handling for database failures
  • Assumes profitSnapshot can be safely cast to JSONB
  • No rollback mechanism if user record update fails after alert creation

This workflow is designed to be called by other workflows but no specific relationships are documented in the current context.

Setup Instructions

  1. Import Workflow: Import the workflow JSON into your n8n instance

  2. Configure PostgreSQL Credential:

    • Create a PostgreSQL credential named "PostgresOnSupabase"
    • Configure connection to your Supabase/PostgreSQL instance
    • Ensure the credential has access to both ceaAlerts and youthEntrepreneursReal tables

  3. Verify Database Schema:

    • Ensure ceaAlerts table exists with columns: phoneNumber, reason, priority, summary, profitSnapshot, status, id, createdAt
    • Ensure youthEntrepreneursReal table exists with columns: phoneNumber, ceaAlertTimestamp, ceaAlertReason, ceaEngagementStatus

  4. Test the Workflow:

    • Call this workflow from another workflow with sample data
    • Verify alert record creation and user status update
    • Check the output message format

  5. Integration: Reference this workflow from other workflows using the Execute Workflow node with the required input parameters