Your site's contact forms - Plugixa CRM

Where this appears: the Integrations screen, as a card called Contact forms. There is no sidebar item.

Pro connector. See the Free vs Pro matrix.

What it is for

Your site already has contact forms. Rebuilding them as web-to-lead forms means maintaining two of everything and losing whatever the existing ones already do: conditional logic, payments, file uploads, the notification routing somebody set up two years ago.

This connector leaves them where they are and reads their submissions.

Four form plugins, one card

Four adapters behind one card, one mapper and one write path. Adding a fifth form plugin would be a fifth adapter and nothing else, which is the point of the shape.

Mapping a form

For each form you want connected, say which of its fields maps to which CRM field, and what the submission should become.

The mapping is per form, because a newsletter sign-up and a quote request are not the same thing and should not produce the same record.

Unmapped fields can still be kept on the record, so nothing a visitor typed is thrown away just because you did not map it.

Submissions are queued, not processed inline

The hook that fires when somebody submits your form does one thing: it enqueues. The work happens minutes later on cron.

That is deliberate, and it protects the thing that matters most. If the CRM is slow, or a mapping is wrong, or something throws, the visitor still sees their confirmation. A form that fails because the CRM behind it failed is a lost enquiry, and a lost enquiry is worse than a late record.

You can see what arrived, and what happened to it, from the card.

What a submission becomes

Usually a lead, which is the right default: somebody filling in a form has not been qualified yet.

Troubleshooting

What to do next

• What they become: Leads.
• A form built for the CRM instead: Web-to-Lead Forms.
• The framework behind the card: Integrations and Webhooks.