Integration & comparison guide
Filter Framer form spam before forwarding a lead
JevShield is an AI-assisted spam classification API for contact-form messages. For a Framer site, your own webhook can check a submission before forwarding it to email or a CRM. This is a custom backend integration guide, not a native Framer plugin or a hosted JevShield webhook destination.
100
free checks / month
$9
Starter / month
5,000
Starter checks / month
7 days
account detection logs
Compare the workflow
| Stage | Your webhook + JevShield | What to verify |
|---|---|---|
| Receive | Configure Framer to send form submissions to your HTTPS webhook. | The receiver maps your actual field names to text and optional email/name. |
| Authenticate | Verify the Framer signature before calling JevShield; keep both secrets on your server. | Use the unmodified request body and submission ID according to Framer’s documentation. |
| Classify | POST /api/v1/check with x-api-key from the backend. | Read verdict, reason and engine; do not treat review as an automatic block. |
| Deliver | Forward allowed leads only after applying the decision. | A parallel email or CRM destination can bypass this filtering path. |
| Retry safely | Deduplicate submission IDs and durably record handling before acknowledging. | Framer requires a direct 2xx acknowledgement and can retry failed requests. |
1. Make the webhook the delivery decision point
Create an HTTPS receiver on infrastructure you control, then select Webhook under the Framer form’s Send To settings. Do not paste the JevShield check endpoint directly into Framer: your receiver must verify the source, transform fields and authenticate to the API. Audit every email, spreadsheet and CRM destination so an unfiltered parallel route does not send the same lead.
2. Verify, queue and classify on your server
Validate the webhook signature using Framer’s official implementation, reject invalid requests and deduplicate by submission ID. After durable acceptance, process the message and forward it according to your policy. Preserve pending work across retries. Never put the JevShield API key or the webhook secret in Framer custom code delivered to visitors.
3. Test before publishing
Use a staging form to submit a legitimate project inquiry, an unsolicited pitch and an ambiguous message. Simulate provider failure, exhausted quota and a repeated webhook delivery. Verify the actual destination inbox or CRM, not just the API verdict. This workflow has not been verified against a live Framer project by JevShield; it requires implementation and end-to-end testing on your site.
What this workflow cannot prevent
Classification happens after Framer accepts the form submission. It does not erase submissions already recorded by Framer, guarantee protection of platform submission quotas, or recall messages delivered through another route. Keep the platform’s bot controls and decide whether uncertain or failed checks should be queued or allowed.