Pipedrive Lead Forms releasesself-updates

Configurable front-end forms that log every submission locally and create leads in Pipedrive, with file uploads, bot protection and cache safe submission.

Description

Pipedrive Lead Forms renders configurable front-end lead forms, logs every submission to a custom database table, and pushes leads to Pipedrive with retries. It is built to never lose a lead and to stay safe behind page caches and CDNs.

Forms support an optional file upload field. By default every file type that WordPress considers safe is accepted; site owners can narrow the allowed file types and set a maximum file size in the settings. Uploaded files are stored in a protected directory, attached to the backup email and attached to the Pipedrive lead.

Updates are delivered via GitHub, not wordpress.org.

Installation

1. Upload the pipedrive-lead-forms folder to /wp-content/plugins/.
2. Activate the plugin through the Plugins screen in WordPress.
3. Configure your Pipedrive API token and forms under the plugin settings.

Changelog

1.5.0

• New: custom field support. Pick one of your Pipedrive custom option fields (leads share them with deals) and its value(s) in the settings; every new lead is created with that field set. Single-choice fields render as radios, multi-choice fields as checkboxes.
• Changed: settings are now validated against the connected Pipedrive account on save. Lead labels, the default owner ID and the selected custom field and its values that do not exist in the connected account (for example after switching the API token to a different account) are removed with an admin warning instead of being kept and breaking lead creation with "Provided labelId does not exist". When the Pipedrive API cannot be reached during save, stored values are kept unchanged, so a temporary outage never wipes your settings.
• Improvement: the settings page now shows admin notices, including the standard "Settings saved." confirmation and the new validation warnings.

1.4.0

• New: lead labels are now selected by name in the settings. The free-text "Lead label IDs" field is replaced by a checkbox list populated from your Pipedrive account, so you no longer have to look up and type label IDs. Existing saved label IDs keep working unchanged, and labels deleted in Pipedrive are preserved. When no valid API token is configured the selector shows a hint instead and never overwrites your saved labels.

1.3.0

• New: lead visibility setting. Choose whether new leads, persons and organizations are visible to the owner only or shared with the owner's visibility group (optionally including sub-groups, or the entire company). Defaults to Pipedrive's own default, so existing installs keep their current behavior until changed. Visibility groups require a Professional or Enterprise Pipedrive plan; on lower plans the group option behaves like "Entire company".

1.2.1

• New: form fields can now be reordered by drag and drop in the form settings. Grab the handle on the left of a field row to change the order; the new order is used both in the editor and on the front-end form.

1.2.0

• New: per-form submission messages. The success, validation, general error and sending texts can now be set individually for each form, with HTML links allowed and a fallback to the built-in defaults when left empty.
• New: each field label is also used as the input placeholder for text, email, tel and textarea fields.
• New: the submit button stays disabled until all required fields are filled.
• Improvement: the consent text is now a full-width textarea shown in its own row only for consent fields, moved out of the "Maps to" column.
• Improvement: the success and error message now appears below the submit button.

1.1.1

• Fix: the release packaging excluded the bundled update checker vendor directory, causing a fatal "Class PucReadmeParser not found" error when checking for updates. The .distignore rule is now anchored to the repository root so only the development tooling vendor directory is omitted.

1.1.0

• New: file upload form field with support for multiple files per field.
• Uploads default to all file types WordPress considers safe; allowed file types and a maximum file size are configurable in the settings.
• Uploaded files are stored in a protected uploads directory, attached to the backup email, and attached to the Pipedrive lead. They are removed again when their submission is cleaned up by the retention policy.

1.0.2

• Security audit pass: verified nonces, capability checks, input sanitization, output escaping and prepared SQL across the plugin. No vulnerabilities found.
• Hardening: documented the safe, constant table name database queries and other deliberate exceptions with justified phpcs annotations.
• Tooling: added a WordPress-Extra phpcs ruleset, composer dev dependencies and a GitHub Actions lint workflow so coding standards are enforced on every push. No functional changes for site visitors.

1.0.0

• Initial release.
• Front-end lead forms with local-first persistence and Pipedrive dispatch.
• Bot protection (honeypot, HMAC time token, rate limiting, optional Turnstile).
• GitHub based automatic updates via the Plugin Update Checker library.