Webhook Payload Structure

{
    "event": "lead_created",
    "event_label": "Lead Created",
    "triggered_at": "2026-01-08 10:30:00",
    "data": {
    "id": 123,
    "name": "John Doe",
    "email": "[email protected]",
    "company": "Acme Corp",
    "status": "1",
    "phone": "+1-555-0100"
    },
    "relationships": {
    "status": {
    "id": 1,
    "name": "New Lead",
    "color": "#28a745"
    },
    "assigned_to": {
    "id": 5,
    "firstname": "Jane",
    "lastname": "Smith"
    }
    },
    "metadata": {
    "source": "perfex_crm",
    "event_id": "evt_1234567890_lead_created_123_abc123",
    "triggered_by": {
    "staff_id": 5,
    "staff_name": "Jane Smith"
    }
    }
    }

Payload Sections Overview

• Event Info – Identifies what happened and when

• Data – The main resource affected by the event

• Relationships – Related entities (optional, if enabled)

• Metadata – System-level context for tracking and auditing

1. Event Information

This section describes what happened and when it happened.

• event – Internal event key (e.g., lead_created)

• event_label – Human-readable event name

• triggered_at – Date and time when the event occurred

This helps identify the webhook trigger inside n8n.

2. Data (Main Resource)

The data object contains the primary record related to the event.

Examples:

• Lead details

• Client information

• Invoice, task, or ticket data

The fields inside this object depend on the selected event type.

3. Relationships (Optional)

When Include Relationship Data is enabled, related records are added here.

Common relationship data:

• Status

• Assigned staff

• Source

• Groups or categories

This avoids extra API calls in your automation workflow.

4. Metadata

Additional context about the webhook execution.

• source – Always indicates Perfex CRM

• event_id – Unique ID for this webhook event

• triggered_by – Staff member who performed the action (if applicable)

Useful for logging, debugging, and audit tracking.