Skip to content

My workflow 7

A simple webhook-based workflow that receives call-related data through two separate webhook endpoints for processing incoming call details and call recordings.

Purpose

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

How It Works

This workflow operates as a passive receiver for call-related data through webhooks:

  1. Incoming Call Details - Receives call metadata and details through a webhook endpoint
  2. Call Recordings - Receives call recording data through a separate webhook endpoint

Both webhooks share the same endpoint path but are configured as separate nodes, allowing for different processing or routing of call details versus recording data.

Workflow Diagram

graph TD
    A[Incoming call details<br/>Webhook] 
    B[Call recordings<br/>Webhook]

    A -.-> C[No connections defined]
    B -.-> C

Trigger

Type: Webhook (HTTP) - Endpoint Path: 0d637452-e31d-4b64-b3b1-f142c093b39e - Method: All HTTP methods accepted - Authentication: None configured

The workflow is triggered when external systems send HTTP requests to the webhook endpoints.

Nodes Used

Node Name Type Purpose
Incoming call details Webhook Receives HTTP requests containing call metadata and details
Call recordings Webhook Receives HTTP requests containing call recording data

External Services & Credentials Required

None currently configured.

The workflow only uses webhook nodes which don't require external service credentials.

Environment Variables

No environment variables are currently used in this workflow.

Data Flow

Input: - HTTP requests sent to the webhook endpoints - Expected to contain call-related data (format not specified)

Output: - Currently no output processing is configured - Data received by webhooks is not connected to any processing nodes

Data Processing: - No data transformation or processing is currently implemented - Webhook data is received but not forwarded to any downstream nodes

Error Handling

No error handling mechanisms are currently implemented in this workflow. The webhook nodes will return standard HTTP responses based on successful receipt of data.

Known Limitations

  • Both webhook nodes share the same endpoint path, which may cause confusion about which node handles which requests
  • No data processing or forwarding is configured
  • No error handling or validation of incoming data
  • Workflow is currently inactive

No related workflows identified from the available 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. Configure Webhooks

    • Both webhook nodes are pre-configured with the same path
    • Consider updating one of the webhook paths if they should handle different types of requests
    • The webhook URL will be: https://your-n8n-instance.com/webhook/0d637452-e31d-4b64-b3b1-f142c093b39e

  3. Add Processing Logic

    • Connect the webhook nodes to processing nodes as needed
    • Add data transformation, validation, or storage nodes
    • Configure error handling for failed requests

  4. Activate the Workflow

    • Click the toggle to activate the workflow
    • Test the webhook endpoints with sample call data

  5. Test the Setup

    • Send test HTTP requests to the webhook URL
    • Verify data is received correctly by checking execution logs
    • Add processing nodes and test the complete flow

Note: This workflow currently only receives data but doesn't process it. You'll need to add additional nodes to handle the incoming call details and recordings according to your specific requirements.