Skip to content

[CICD-TEST] Heartbeat Ping

A simple test workflow designed to validate CI/CD deployment processes by providing a basic HTTP endpoint that responds with deployment status information.

Purpose

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

This workflow serves as a CI/CD validation tool, specifically created to test the "First-Deploy" path where a workflow exists in the repository but hasn't been deployed to the live n8n instance yet. It provides a simple health check endpoint that confirms successful deployment and returns basic status information.

How It Works

  1. Webhook receives request: An HTTP request is made to the /cicd-test-heartbeat endpoint
  2. Response generated: The workflow immediately responds with a JSON payload containing status information, workflow name, deployment date, and the CI/CD method used
  3. Request completed: The webhook response is sent back to the caller with deployment confirmation

Workflow Diagram

graph TD
    A[Webhook<br/>cicd-test-heartbeat] --> B[Respond<br/>JSON Status]

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

Trigger

  • Type: Webhook
  • Path: /cicd-test-heartbeat
  • Method: Any HTTP method accepted
  • Authentication: None required

Nodes Used

Node Type Node Name Purpose
Webhook Webhook Receives HTTP requests on the /cicd-test-heartbeat endpoint
Respond to Webhook Respond Returns a JSON response with deployment status information
Sticky Note [CICD] First Deploy Test Documentation note explaining the workflow's CI/CD testing purpose

External Services & Credentials Required

No external services or credentials required. This is a self-contained test workflow that only uses n8n's built-in webhook functionality.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input

  • HTTP request to /cicd-test-heartbeat endpoint
  • No specific payload or parameters required

Output

1
2
3
4
5
6
{
  "status": "ok",
  "workflow": "[CICD-TEST] Heartbeat Ping",
  "deployed_at": "2026-05-04",
  "method": "CICD-First-Deploy"
}

Error Handling

This workflow has no explicit error handling paths. It uses n8n's default error behavior: - If the webhook fails to receive requests, n8n will return standard HTTP error responses - If the response node fails, the workflow execution will fail and n8n will handle the error according to workflow settings

Known Limitations

  • No authentication or rate limiting implemented
  • Static response data (deployment date and method are hardcoded)
  • No logging or monitoring of requests
  • Designed as a temporary test workflow, not for production use

No related workflows specified in the context.

Setup Instructions

  1. Import the workflow:

    • Copy the workflow JSON
    • In n8n, go to Workflows → Import from JSON
    • Paste the JSON and save

  2. Activate the workflow:

    • Open the imported workflow
    • Click the "Active" toggle to enable it

  3. Test the endpoint:

    • The webhook will be available at: https://your-n8n-instance.com/webhook/cicd-test-heartbeat
    • Make a GET, POST, or any HTTP request to test
    • You should receive the JSON status response

  4. Customize if needed:

    • Update the response body in the "Respond" node to reflect your deployment information
    • Modify the webhook path if you need a different endpoint name

Note: This workflow is intended for CI/CD testing purposes and should be deactivated or removed after deployment validation is complete.