Lead Processing Extension Points

This page covers lead processing at the integration level only. Internal hook names, payload shapes, capability identifiers and webhook signing details are implementation details and are not published here.

What lead processing does

When a visitor submits a contact form bound to a vehicle, the plugin stores the lead, notifies the configured recipients, and optionally relays the lead to an external system through the plugin's outgoing webhook mechanism. The recipients, delivery method and authentication used for outgoing webhooks are configured from the plugin's admin UI.

Integrating with downstream systems

The supported way to forward leads to a CRM or marketing tool is to configure the plugin's outgoing webhook from the admin UI. Internal hook names, payload structure and the signing scheme used to authenticate outgoing webhook calls may evolve between releases; verify your downstream receiver against the current plugin version when you configure it, and do not hard-code internal action or filter names into your integration.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.