Client integrationIntegrations· Proprietary

LIGNA Integration

Form submissions on a WordPress site become structured leads in LIGNA CRM automatically, through a REST endpoint and an authenticated API call. Built for a client, published here as an example of the integration work we do.

Pricing on requestv1.0

Discuss a similar integration

Why it exists

A lead that arrives as an email notification is a lead somebody has to retype into the CRM. That step gets skipped when things are busy, which is exactly when leads matter most, and the CRM ends up as an incomplete record nobody trusts.

LIGNA CRM has an API. WordPress has forms. Nothing connected the two, so this plugin was built for a client who needed website enquiries to land in LIGNA as structured leads without a person in the middle.

It is published here as an example of the integration work we do, not as a general-purpose product. Without a LIGNA CRM account and API credentials it does nothing.

A client integration, not a product

This is proprietary software developed by Accurate Web Solutions rather than a GPL plugin, and it is not on WordPress.org. It only does anything for sites connected to LIGNA CRM. If you need something similar for your own CRM, that is work we can do — the page is here to show what it looks like.

What it does

Form submissions become LIGNA CRM leads automatically, with no manual re-entry and no export step

Authenticated API connection — an API ID and secret entered once under Ligna Settings

Field mapping from WordPress form fields onto LIGNA lead fields, including first and last name, email and phone

A REST endpoint at /wp-json/ligna/v1/catch_lead/ accepting POST requests with lead data

Form-agnostic — any form plugin that can fire a webhook, or any custom handler, can post to it

Two admin screens: API for credentials, Form for the workspace ID and form ID leads land against

Credentials stored in WordPress options rather than committed to code

Nonce-protected admin forms, sanitised input, and admin functions gated behind manage_options

How it works

The flow is: a visitor submits a form, the submission is posted to the plugin's REST endpoint as JSON, the plugin maps the payload to LIGNA's lead structure, and it calls the LIGNA API with the stored credentials. The lead appears in the configured workspace and form.

The endpoint accepts a data object with contact fields, so wiring up a new form means pointing it at the endpoint and matching field names, rather than writing a new integration each time. That is what makes the integration form-agnostic rather than tied to one form builder.

Security follows standard WordPress practice. Admin forms use nonces to prevent CSRF, all input is sanitised, and admin functions are gated behind the manage_options capability. API credentials are stored in WordPress options rather than committed to code.

Requirements and limits

WordPress5.0 or higher

PHP7.4 or higher

The cURL extension enabled
A LIGNA CRM account with API access
Proprietary software developed by Accurate Web Solutions — not GPL, and not on WordPress.org

What it does not do

This is a client integration rather than a product. Without LIGNA CRM it has no function — there is no fallback destination for leads.

Version 1.0 handles lead creation in one direction: WordPress to LIGNA. There is no sync back from the CRM, no update or deduplication of existing leads, and no retry queue, so a failed API call is a lead that did not arrive.

Field mappings are configured manually and need updating when either side changes.

Frequently asked questions

Is this available for my site?

Only if you use LIGNA CRM. Without an account and API credentials it has no function.

Is it free?

It is proprietary client software rather than a free product. Talk to us if you need a similar CRM integration.

Which form plugins does it support?

Any form that can POST to a REST endpoint. The plugin exposes /wp-json/ligna/v1/catch_lead/ and is not tied to a specific form builder.

Which fields get sent to the CRM?

Whichever ones you map. Field mapping is configurable rather than fixed, so the form can keep its own field names while LIGNA still receives the lead structure it expects.

Does it sync data back from LIGNA?

No. Lead creation is one-way, WordPress to LIGNA.

What happens if the API is down?

Version 1.0 has no retry queue, so a failed call means the lead does not arrive. Keep form notification emails on as a safety net.

Can you build something similar for my CRM?

Yes. That is the work this came from — get in touch through the contact form.

Related plugins

Integrations

Need an integration like this?

This one was built for a single client and is not distributed. Tell us what you are connecting and we will scope the equivalent.