Integrations

Website forms, WordPress and capture SDK

Capture leads from any form on your website (WordPress, Wix, plain HTML) straight into the CRM: paste a ready-made HTML form or the JS capture SDK. Each submission becomes a Lead automatically.

The "Website forms / WordPress" integration captures leads from any form on your site and creates a Lead in the CRM on each submission. It is built by us, with no external account: you just generate a capture address (a public token) and point a form to it. Fields are mapped flexibly (name/email/phone/company/message), and the lead's source stays as "website" (or the value you set in the "source" field).

It accepts the submission as a normal HTML form (application/x-www-form-urlencoded) or as JSON, so it works both with a <form> you paste and with code calls. The address accepts POST from any domain (CORS open), since the whole point is to receive the submission from the customer's site. It starts out inert: nothing is captured until you generate the address and enable it.

Prerequisites

No external account or credential: the capture is built by us.
Access to edit your site: pasting a <form> or a <script> (in WordPress, a "custom HTML" block or the theme footer; it also works with Contact Form 7, Elementor, Wix or plain HTML).
In Sellio, being an administrator to generate the capture address and enable the integration under Settings → Integrations.

How to enable

Open Settings → Integrations and go to the "Website forms / WordPress" card.
Click "Generate capture address" to create the webhook URL (a unique, public capture token).
Copy the ready-made HTML form (or the SDK) and paste it into your site, as below.
Click "Enable". From then on submissions start creating Leads in the CRM.

Option A: ready-made HTML form

On the card, copy the ready-made <form> block (it already points to your capture address) and paste it wherever you want to show the form. In WordPress, use a "custom HTML" block. You can adjust the fields freely: the names name, email, phone, company and message are recognized automatically. An optional hidden "redirect" field takes the visitor to a thank-you page after submission.

Example: <form action="https://app.yourdomain.com/api/inbound/webform/YOUR_TOKEN" method="POST"> … <input name="email" required> … </form>

Option B: JS capture SDK (developers)

For sites that already have their own forms (or apps), paste the SDK's <script> into your site. It exposes two methods in the browser, with no sensitive data (only the public capture token goes in the script):

window.Sellio.capture({ name, email, phone, company, message, source }) sends a lead directly (useful in buttons, popups or app flows).
Sellio.trackForm('#my-form') intercepts an existing form's submission and sends the fields to the CRM, without you touching the form's HTML.

Example: <script src="https://app.yourdomain.com/api/sdk/YOUR_TOKEN/sellio.js" async></script> → then: Sellio.trackForm('.wpcf7-form')

WordPress: Contact Form 7, Elementor and HTML block

HTML block: paste the ready-made form (Option A) into a "custom HTML" block on the page.
Contact Form 7: keep your CF7 form and add the SDK (Option B) to the theme footer; then call Sellio.trackForm(".wpcf7-form"). CF7 field names (your-name, your-email) are already recognized.
Elementor: keep the Elementor Form and add the SDK to the site; use Sellio.trackForm() with your form's selector to send each submission to the CRM.

What becomes a Lead

Each submission with something identifiable (email, phone or name) creates a Lead, with the source defined by the "source" field (default "website"). Fields you send that are not the standard ones are appended to the lead's message, so nothing is lost. Capture is idempotent on a best-effort basis: if you send an "external_id", resubmissions of the same id do not duplicate; without external_id, leads with the same email are not duplicated either.

Security

The URL token is PUBLIC and serves only for capture: it identifies your account, but does not expose data or allow reading anything. Never put a secret in the form or the SDK.
If you need to invalidate the current address, use "Generate new token", and the old form/SDK stops working.
An invalid token or disabled integration returns 404; empty submissions (with nothing identifiable) are silently ignored.

💡 Start with the ready-made HTML form to validate quickly, and move to the SDK (trackForm) when you want to keep the look of your current WordPress form.

How to test

Paste the ready-made HTML form (Option A) on a test page of your site and enable the integration.
Fill in and submit the form with a test email.
In the CRM, open the Leads list and confirm a Lead appeared with source "website" (or the value of the "source" field).
Resubmit with the same email (or the same external_id) and confirm it does NOT duplicate.

Troubleshooting

Does not create a Lead: confirm the integration is "Enabled" and that the <form>/SDK points to the correct capture address. Completely empty submissions (no email, phone or name) are silently ignored.
404 on the URL: the address token changed (you clicked "Generate new token") or the integration is disabled. Copy the current address and update the form/SDK.
SDK does not intercept the form: check the selector passed to Sellio.trackForm() (e.g., ".wpcf7-form"); in CF7/Elementor the SDK must load on the site (theme footer).
Fields do not come through: use the recognized names (name, email, phone, company, message); CF7 names (your-name, your-email) are already accepted. Extra fields are appended to the lead's message.
Do not put secrets in the form: the URL token is PUBLIC and serves only for capture, and it neither exposes nor reads data.

Open this article inside the system →