KeyCRM Form Catcher — leads from any landing page into KeyCRM

KeyCRM Form Catcher is a lightweight form-catcher for sites and landing pages: any HTML form starts sending leads straight into KeyCRM. For a static landing page it’s three files — keycrm-catcher.php (a server-side relay that hides the API key), keycrm-core.php (the core) and keycrm-forms.js (binds to your forms) — no CMS, no composer dependencies, no jQuery. For WordPress, a ready-made plugin for Contact Form 7 is included, built on the same core, with settings in the admin panel and a lead log.

The tool is completely free. The code is open on GitHub: github.com/catcodestudio/keycrm-form-catcher. All you need is an API key from your KeyCRM account and hosting with PHP.

What the customer sees

How it works, step by step

1. A visitor fills in the form on the landing page — just add the data-keycrm attribute to the form, and keycrm-forms.js intercepts it automatically. In WordPress, nothing needs adding: the plugin listens for Contact Form 7 submissions.
2. The JS collects the data: the form fields plus page_url, the referrer and all UTM tags — added automatically.
3. The request goes to the server-side relay, keycrm-catcher.php — the API key lives only on the server and never appears on the front end.
4. The relay checks the submission: a honeypot against bots, IP rate-limiting, Origin checking, validation (either a phone or an email is required) and protection against a double submit.
5. The lead is created in KeyCRM — either as an order (POST /order, works right away even on a trial) or as a lead card in a pipeline (POST /pipelines/cards). Standard UTMs go into KeyCRM’s analytics, while the referrer and page go into a comment for the manager.
6. The visitor sees the result: a message from data-success or a redirect from data-redirect; the form fires keycrm:success / keycrm:error events — handy for hooking up analytics.
7. A copy of the lead is sent by e-mail and to Telegram, so the manager sees it without even opening the CRM.

WordPress + Contact Form 7

The archive contains a wordpress/catcode-form-leads-to-keycrm folder — a regular plugin: drop it into wp-content/plugins/ and activate it. It runs on the same core but takes its data from Contact Form 7 and requires no changes to your forms.

• Field roles are based on CF7 tag types, so auto-generated names like text-32, tel-635, email-278 that CF7 assigns itself work fine.
• Field labels are taken from the form itself — the manager sees “City: Lviv”, not “your-city: Lviv”.
• Product and SKU are pulled from a product-id / product-sku field or from the WooCommerce product page the form sits on.
• A lead log in the admin panel: what went to the CRM, e-mail and Telegram.
• The catcode_lead_captured hook — our Telegram notifications plugin listens for it and sends a message using its own template.

Pricing

Free, open source. Download it from GitHub or the button on this page — no tariffs and no limit on the number of leads on the script’s side.

Technical requirements

• PHP 7.4+ with the cURL extension — any hosting will do
• Any HTML landing page — no CMS needed
• For the WordPress plugin — WordPress 6.2+ and Contact Form 7
• A KeyCRM API key — your KeyCRM account → Settings → API
• For lead-card mode — a pipeline created in KeyCRM (Leads → Pipelines) and its ID

Under the hood

• The API key stays on the server only — the front end talks to the relay, not directly to KeyCRM; the key cannot be extracted from the page’s code.
• A honeypot field: a human doesn’t see it, a bot fills it in. If it’s not empty, a silent fake success is returned — the bot never learns it was caught.
• IP rate-limiting — at most 10 submissions from one IP per hour (configurable via a constant), with counters kept in the system temp directory.
• Origin/CORS checking — list your domains in KEYCRM_ALLOWED_ORIGINS, and the relay will reject requests from other sites.
• Duplicate protection — a repeated submission with the same content within 5 minutes doesn’t create a second card in the CRM and doesn’t send a second e-mail. In WordPress the lock is atomic, so even several simultaneous submissions produce exactly one lead. If the CRM returns an error, the lock is released — the customer’s retry isn’t lost.
• The relay accepts a plain POST (form-encoded or JSON) — you can submit not only via keycrm-forms.js but also from a custom fetch call or any other code.

How to install

1. Download keycrm-form-catcher-1.2.0.zip and unpack it.
2. For a landing page: drop keycrm-catcher.php, keycrm-core.php and keycrm-forms.js into your site’s root (or any convenient folder).
3. In keycrm-catcher.php, enter your API key in the KEYCRM_API_KEY constant and your domains in KEYCRM_ALLOWED_ORIGINS.
4. Add <script src="/keycrm-forms.js"></script> and give your form the data-keycrm attribute.
5. For WordPress: copy the wordpress/catcode-form-leads-to-keycrm folder into wp-content/plugins/, activate the plugin, and fill in “Settings → KeyCRM Form Catcher”.
6. Send a test submission — it will appear in KeyCRM. A working example for landing pages is in the example.html file.

Version history

1.2.0 — August 2026

Protection against double submits (in WordPress, an atomic lock — so even parallel requests produce one lead; the lock is released on a CRM error). The plugin no longer sends a lead to the CRM if another plugin interrupted the CF7 submission. Field labels are taken from the form itself, not from technical names. A clear error message when the API key isn’t set. The core has been split into a separate keycrm-core.php, shared by the relay and the plugin. Removing the plugin cleans up the table and options. English interface with a Ukrainian translation.

1.1.0 — July 2026

A duplicate of the lead by e-mail and Telegram, a lead type for each form, the product SKU, a WordPress + Contact Form 7 plugin with a lead log in the admin panel.

1.0.0 — July 2026

First public release: relay + JS widget, two modes (order / lead card), automatic UTM collection, honeypot, IP rate-limiting, Origin/CORS checking, keycrm:success / keycrm:error events, an example.html sample.