Skip to content

SMS Delivery Report

A webhook-based workflow that receives SMS delivery status reports from external SMS providers. This workflow serves as an endpoint for SMS service providers to send delivery confirmations, failure notifications, and other status updates for SMS messages sent through integrated messaging systems.

Purpose

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

This workflow appears to be designed to receive SMS delivery reports from SMS gateway providers. These reports typically contain information about whether SMS messages were successfully delivered, failed, or are pending delivery to recipients.

How It Works

  1. Webhook Receives Report: An external SMS provider sends a POST request to the webhook endpoint with delivery status information
  2. Data Processing: The webhook captures the incoming delivery report data (currently no processing nodes are configured)

Note: This workflow is currently in a minimal state with only a webhook trigger configured. Additional processing nodes would typically be added to handle the incoming delivery reports.

Workflow Diagram

graph TD
    A[Webhook Trigger] --> B[End]

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

Trigger

Webhook (POST) - Path: 6ce71395-8e3a-47c9-8875-6ad36e1a848e - Method: POST - Purpose: Receives SMS delivery reports from external SMS providers

The webhook URL would be: https://your-n8n-instance.com/webhook/6ce71395-8e3a-47c9-8875-6ad36e1a848e

Nodes Used

Node Type Node Name Purpose
Webhook Webhook Receives POST requests containing SMS delivery status reports

External Services & Credentials Required

Current State: No external services are currently integrated.

Typical Requirements (for a complete SMS delivery report workflow): - SMS Gateway Provider credentials (API keys, tokens) - Database credentials (for storing delivery reports) - Notification service credentials (for alerting on failures)

Environment Variables

No environment variables are currently configured for this workflow.

Data Flow

Input: - SMS delivery report data via POST request to webhook - Typical fields might include: message ID, recipient number, delivery status, timestamp, error codes

Output: - Currently no output processing configured - HTTP 200 response to acknowledge receipt

Data Format: The webhook accepts any JSON or form data sent via POST request.

Error Handling

No error handling is currently implemented in this workflow. The webhook will return standard HTTP responses based on n8n's default behavior.

Known Limitations

  • Workflow is in a minimal state with no data processing
  • No validation of incoming delivery report data
  • No storage or forwarding of delivery status information
  • No error handling for malformed requests

No related workflows identified from the current configuration.

Setup Instructions

  1. Import Workflow:

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

  2. Configure Webhook:

    • The webhook is pre-configured with path 6ce71395-8e3a-47c9-8875-6ad36e1a848e
    • Activate the workflow to enable the webhook endpoint
    • Note the full webhook URL for SMS provider configuration

  3. SMS Provider Configuration:

    • Configure your SMS gateway provider to send delivery reports to the webhook URL
    • Ensure the provider sends POST requests with delivery status data

  4. Add Processing Nodes (Recommended):

    • Add nodes to process incoming delivery reports
    • Consider adding database storage for delivery status tracking
    • Add error handling and validation nodes
    • Configure notifications for delivery failures

  5. Testing:

    • Send a test POST request to the webhook URL
    • Check the workflow execution history to verify data reception
    • Configure your SMS provider's webhook settings with the n8n webhook URL

Note: This workflow requires additional development to be fully functional for SMS delivery report processing.