Enqilo.

Enqilo / help

Know what was checked. Know what comes next.

A practical guide to monitoring coverage and its limitations.

01 /

Getting started

Register with a verified email link, create an organisation and add your website. Add the exact DNS TXT challenge at _formpulse.your-hostname. Verify it in the website screen before configuring form tests.

02 /

Configure a form

Choose a page URL on the verified origin, a unique form selector, field selectors, a submit selector and a success selector or exact success URL. Use {{testId}} in synthetic values. For example: monitoring+{{testId}}@example.invalid. Human CAPTCHA challenges stop automatic testing. A protection script alone does not prove a challenge occurred.

03 /

Connect Webflow

An operator must register a Webflow Data Client with sites:read and forms:read. Connect it in Settings, select an authorised site matching the website domain and discover its forms. Copy the matching form ID into the form configuration.

04 /

Understanding results

PASSED: the displayed verification level succeeded. FAILED: the configured check failed. INCONCLUSIVE: evidence could not be established. NOT CONFIGURED: prerequisites are missing or execution is disabled. PAUSED: monitoring is paused. Blank history means no check has run.

05 /

Alert behaviour

Two consecutive failures open a deduplicated incident. A subsequent passing result resolves it. Owner email alerts are enabled when creating an organisation; you can change your own alert preference in Settings. Delivery history records provider acceptance, not inbox delivery.

06 /

Current support

Webflow supports OAuth, form discovery and bounded submission-record verification. The optional WordPress connector observes Gravity Forms saved entries and CF7 processing events. Shopify native contact forms support conditional browser checks; configured Shopify Forms/Flow receipts are a separate capability. Monitoring-inbox arrival, booking availability, DNS observations, eligible activity analysis, review windows and monthly PDF reports require their respective setup. Guided static discovery, explicit activation, trials, secure invitation links and Stripe test-mode billing are implemented; external provider validation and production launch gates remain open.

07 /

Operational setup

Run PostgreSQL, Redis, the web service and a separate worker. Configure Resend and verified sender details for sign-in and alerts. Active browser checks remain disabled until the operator enables them after reviewing worker network isolation. See the repository documentation for all environment variables.

Permission-first monitoring. Evidence you can inspect.