Skip to content

[DEMO NEW] First Deploy Test

This workflow demonstrates the CI/CD pipeline's ability to create and deploy a brand-new workflow from development to production. It serves as a proof-of-concept for the first-deploy automation process, showing how workflows can be built in development, committed to version control, and automatically deployed to production with proper credential mapping.

Purpose

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

This workflow was created specifically to test and demonstrate the CI/CD pipeline's first-deploy functionality. It validates that: - Workflows can be created in development and automatically promoted to production - Credential references are properly mapped between environments - The deployment process maintains workflow integrity across environments

How It Works

  1. Manual Trigger: The workflow starts when manually triggered by a user
  2. Set Demo Marker: Creates demonstration data including a unique demo ID and purpose description
  3. HTTP Request: Makes a placeholder HTTP request to demonstrate credential usage and external service integration

The workflow is intentionally kept simple to focus on the deployment mechanics rather than complex business logic.

Workflow Diagram

graph TD
    A[Manual Trigger] --> B[Set Demo Marker]
    B --> C[HTTP Request placeholder]

Trigger

Manual Trigger: This workflow must be started manually by clicking the "Execute Workflow" button in the n8n interface. It does not run automatically on any schedule or external event.

Nodes Used

Node Type Node Name Purpose
Manual Trigger Manual Trigger Initiates the workflow when manually executed
Set Set Demo Marker Creates demo data with ID and purpose information
HTTP Request HTTP Request (placeholder) Demonstrates external API integration with credential usage
Sticky Note [DEMO NEW] explanation Provides documentation about the CI/CD deployment process

External Services & Credentials Required

Required Credentials

  • AT Header Auth (httpHeaderAuth): Used by the HTTP Request node for authentication
    • Type: HTTP Header Authentication
    • Required for: Making authenticated requests to external services

External Services

  • Example API: The workflow makes a request to https://example.invalid/demo-first-deploy-2026-04-29 (placeholder URL for demonstration)

Environment Variables

No environment variables are used in this workflow.

Data Flow

Input

  • No external input required (manual trigger only)

Processing

  • Generates demo metadata:
    • demo_id: "first-deploy-2026-04-29"
    • purpose: Description of the CI/CD demonstration

Output

  • HTTP response from the placeholder API request
  • Demo marker data for validation purposes

Error Handling

No explicit error handling is implemented in this workflow. The HTTP Request node has a 5-second timeout configured to prevent hanging requests.

Known Limitations

  • Uses a placeholder/invalid URL that will not return real data
  • Workflow is inactive by default and must be manually activated
  • Designed for demonstration purposes only, not production use
  • Limited error handling and recovery mechanisms

This workflow is part of the CI/CD pipeline demonstration system, which includes: - Cron-Backup: Pulls workflows from development to version control - CICD-Sync-Deploy: Detects deployment needs and orchestrates updates - CICD-First-Deploy: Handles initial deployment of new workflows to production

Setup Instructions

1. Import the Workflow

  1. Copy the workflow JSON from the repository
  2. In n8n, go to Workflows > Import from JSON
  3. Paste the JSON and click Import

2. Configure Credentials

  1. Create an HTTP Header Auth credential named "AT Header Auth"
  2. Configure the header name and value as needed for your environment
  3. The workflow will automatically reference this credential

3. Activate the Workflow

  1. Open the imported workflow
  2. Click Active toggle to enable the workflow
  3. The workflow is now ready for manual execution

4. Test the Deployment

  1. Click Execute Workflow to run manually
  2. Verify the demo data is generated correctly
  3. Check that credential references are properly mapped

Notes

  • This workflow is designed to remain inactive in production
  • The HTTP endpoint is intentionally invalid for safety
  • Credential IDs are automatically mapped during CI/CD deployment