Events and payloads
Subscription availability depends on your integration, access context and environment. Confirm the supported events and operations with LMG rather than assuming every record mutation produces a public notification.
Event families in the implementation
| Family | What the notification concerns |
|---|---|
| Adviser changes | Adviser information |
| Organisation changes | Adviser organisation information |
| Contact changes | Client contact information |
| Deal changes | Deal information |
| Deal pipeline status changes | A deal's pipeline status |
| Task changes | Task information for supported integrations |
Event subscriptions can be filtered to an agreed business context. The event family alone is not a promise that every create, update and delete is emitted. Confirm the subscription's supported operation types during setup.
Payload fields
| Field | Meaning |
|---|---|
action | Operation label, such as created, updated or deleted |
resource.type | Resource type associated with the event |
resource.id | Resource identifier |
resource.url | URL for the resource, when provided |
webhook.name | Subscription name |
The sender does not include a documented unique delivery ID or sequence number in this envelope. Do not invent one in receiver logic or assume the subscription name identifies an individual event.
After an event
Read current data where appropriate, using the normal token, scopes and access rules. A deleted record may no longer be retrievable. A later update may already have occurred by the time your receiver processes an earlier notification.