Webhook Payload Structure

{
  "event": "lead.created",
  "timestamp": 1768451422,
  "crm_url": "https://yourdomain.com/",
  "entity": "lead",
  "action": "created",
  "data": {
    "id": 37,
    "company_name": "John Doe",
    "type": "organization",
    "owner_id": 1,
    "email": "",
    "phone": "+1-155-2584",
    "address": "Rajkot",
    "city": "Rajkot",
    "state": "Gujarat",
    "zip": "360001",
    "country": "India",
    "website": "",
    "vat_number": "",
    "is_lead": 1,
    "lead_status_id": 1,
    "lead_source_id": 1,
    "created_date": "2026-01-15 04:30:22",
    "custom_fields": []
  },
  "metadata": {
    "user_id": 1,
    "user_name": "John Smith",
    "user_email": "[email protected]",
    "ip_address": "192.168.0.199"
  }
}

Payload Sections Overview

• Event Info – Identifies what happened and when

• Data – The main resource affected by the event

• 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)

• timestamp – Date and time when the event occurred

• crm_url – Your Rise CRM url.

• entity – Indicates entity type (e.g., Lead, Client)

• action – Indicates action of event (e.g. Create, Update, Delete).

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 data

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

3. Metadata

Additional context about the webhook execution.

• user_id – Current logged in user id.

• user_name – Current logged in user name.

• user_email – Email address of current user

• ip_address – IP address of CRM.

Useful for logging, debugging, and audit tracking.