Skip to content

Youth Profile Creation Tool

A workflow that creates new youth profiles in the database by accepting basic participant information including phone number, name, location, and business type. This tool serves as a data entry point for capturing essential details about youth participants in business development programs.

Purpose

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

Based on the workflow structure, this appears to be designed for capturing and storing youth participant information, likely for a business development or entrepreneurship program. The workflow accepts basic demographic and business information to create standardized profiles in a PostgreSQL database.

How It Works

  1. Input Collection: The workflow receives four key pieces of information about a youth participant:

    • Phone number (required for identification)
    • Full name
    • Location/geographic area
    • Type of business they're involved in

  2. Database Storage: The collected information is inserted into a youth_profiles table in PostgreSQL, creating a permanent record of the participant

  3. Profile Creation: A new youth profile record is established with the provided details, ready for use in subsequent program activities

Workflow Diagram

graph TD
    A[Execute Workflow Trigger<br/>youthProfileCreationTool] --> B[Insert rows in a table<br/>PostgreSQL]

    style A fill:#e1f5fe
    style B fill:#f3e5f5

Trigger

Execute Workflow Trigger - This workflow is designed to be called by other workflows or external systems. It accepts the following input parameters: - phone_number (number) - Contact number for the youth participant - name (string) - Full name of the participant - location (string) - Geographic location or area - business_type (string) - Description of their business or entrepreneurial activity

Nodes Used

Node Type Node Name Purpose
Execute Workflow Trigger youthProfileCreationTool Receives input parameters for youth profile creation
PostgreSQL Insert rows in a table Stores the youth profile data in the database

External Services & Credentials Required

PostgreSQL Database

  • Credential Name: "Postgres account 2"
  • Required Access: Write permissions to youth_profiles table
  • Database Schema: Must contain a youth_profiles table with columns for phone_number, name, location, and business_type

Environment Variables

No environment variables are explicitly configured in this workflow. Database connection details are managed through n8n's credential system.

Data Flow

Input

The workflow expects four input parameters: 

1
2
3
4
5
6
{
  "phone_number": "+254712345678",
  "name": "Grace Kioko", 
  "location": "Kiambu",
  "business_type": "selling second hand clothes"
}

Output

Creates a new record in the youth_profiles PostgreSQL table with the provided information. The database may auto-generate additional fields like ID, timestamps, and default values for other columns.

Error Handling

No explicit error handling is implemented in this workflow. Potential failure points include: - Database connection issues - Invalid input data formats - Duplicate phone number conflicts (if database has unique constraints) - Missing required fields

Known Limitations

  • The PostgreSQL insert node is currently disabled, preventing actual database writes
  • No validation of phone number format or uniqueness
  • No error handling for database failures
  • Limited to basic profile information only
  • Workflow is marked as archived and inactive

No related workflows are specified in the current context.

Setup Instructions

  1. Import the Workflow

    • Import the JSON configuration into your n8n instance
    • The workflow will be imported in an inactive, archived state

  2. Configure PostgreSQL Credentials

    • Create a PostgreSQL credential named "Postgres account 2"
    • Ensure the database contains a youth_profiles table with appropriate columns:
      • phone_number (string, required)
      • name (string)
      • location (string)
      • business_type (string)

  3. Enable the Workflow

    • Unarchive the workflow
    • Enable the PostgreSQL insert node (currently disabled)
    • Activate the workflow

  4. Test the Setup

    • Use the pinned test data or create a test execution
    • Verify that records are properly inserted into the database
    • Check that all input parameters are correctly mapped to database columns

  5. Integration

    • Call this workflow from other workflows using the Execute Workflow node
    • Pass the required parameters: phone_number, name, location, business_type