How to Send an Eligible Shopify Lead to Your Own Webhook
Use AGNURA Add Lead to POST analysis JSON to your webhook: Shopify platform label, detected email, configured URL, n8n-style setup, and security warnings for contact data.
You will be able to click Add Lead so AGNURA POSTs the full website analysis JSON to a webhook URL you own (often n8n), only when the lead is eligible.
Eligibility is strict today:
- Platform name is exactly
Shopify - At least one detected contact email
- A real webhook URL saved in Settings → General (not the example placeholder)
Security warning: Add Lead sends the full analysis, including emails, phones, and other research fields, to your endpoint. Protect that URL. Use HTTPS. Restrict who can read the workflow. Follow your data policy. Do not point the field at a public or untrusted URL.
Hub: What Is Website Intelligence for Sales and Outreach?. Local file export (no webhook): How to Export Website Research as JSON.
When this applies
- The active tab analyzes as Shopify (not WordPress-only, not “Unknown”)
- You already found a public email on the site (or via contact/about fetches)
- You want automation (CRM, sheet, Slack) under your backend
- You accept that clicking Add Lead leaves the browser toward your webhook
Prerequisites
- AGNURA installed; analysis runnable on http(s) tabs
- An HTTPS webhook you control (n8n Production URL, Make, custom API, etc.)
- Permission to store business contact data in that system
- Optional: test webhook that logs the body before you connect a CRM
You do not need AGNURA credits for Add Lead.
Direct answer
- Create a webhook that accepts
POST+Content-Type: application/json. - Paste that URL into Settings → General → Add Lead webhook URL and Save.
- Open a Shopify storefront tab; run analysis.
- Confirm platform is Shopify and
contact.emailsis not empty. - Click Add Lead once; wait for success or error.
- Confirm the payload arrived in your automation; treat contacts as sensitive.
Step-by-step
1. Prepare your webhook safely
| Do | Do not |
|---|---|
| Use https:// endpoints you control | Paste random URLs from the internet |
| Prefer secret paths or auth your platform supports | Expose an unauthenticated open webhook forever |
| Log/redact in a private workflow first | Forward raw leads to a public Slack channel |
| Document retention for contact fields | Assume AGNURA stores the lead in the cloud for you |
AGNURA POSTs with:
- Method: POST
- Header:
Content-Type: application/json - Body:
JSON.stringify(analysisResult)(full last analysis) - Timeout: about 15 seconds
Expected result: A test POST from any HTTP client reaches your workflow.
2. Configure the URL in AGNURA
- Open AGNURA → Settings → General.
- Find Add Lead webhook URL.
- Replace the placeholder (
https://n8n.example.com/webhook/insert-leadstyle) with your URL. - Save settings.
Configured means: valid http:// or https:// URL, and the host is not n8n.example.com or example.com.
Expected result: Settings persist locally in the extension. Add Lead can enable when the tab is eligible.
3. Analyze an eligible Shopify tab
- Open the store’s public site.
- Run website analysis (Run Your First Website Analysis).
- Check the platform label is Shopify (exact name used for eligibility).
- Check that at least one email appears in contacts. If not, open
/pages/contact(or similar) and re-analyze (Find Public Business Contact Details).
Expected result: Header Add Lead is enabled. Hover title: “Post analysis data to your configured webhook.”
4. Click Add Lead
- Click Add Lead once.
- Button may show Adding… while the request runs.
- Success: status/snackbar Lead added successfully.
- Failure: read the error (HTTP status, timeout, network message).
Nothing is sent until you click. There is no background auto-send of leads.
Expected result: Your webhook receives one JSON body matching the popup analysis (same family of fields as the downloadable analysis JSON).
5. Map fields in your automation
Common next steps in n8n (or similar):
- Parse JSON body
- Map
contact.emails[0],domain,tabUrl,platform,theme - Upsert CRM row
- Notify your team in a private channel
Prefer mapping only fields you need. Drop excerpts you do not want stored.
Expected result: One CRM/sheet row you can defend under policy.
Eligibility troubleshooting
| Button / title hint | Cause | Fix |
|---|---|---|
| “Run analysis first” | No result loaded | Run analysis |
| “Requires a Shopify site” | platform.name is not exactly Shopify | Confirm live storefront signals; hybrids may not qualify (platform detection) |
| “Requires a detected contact email” | Empty contact.emails | Find public email; re-analyze contact page |
| “Set your Add Lead webhook URL…” | Still on placeholder / invalid URL | Save a real endpoint in Settings → General |
| Enabled but POST fails | Webhook down, auth, CORS/network, timeout | Check workflow logs; fix endpoint; retry within 15s window |
| “Lead insert timed out” | Slow or hanging endpoint | Optimize workflow; return 2xx quickly |
WordPress-only sites, empty emails, or Unconfigured webhooks cannot use Add Lead in v1. Use JSON download instead if you only need a local file.
Security and data-handling checklist
- Webhook URL is yours and uses HTTPS in production
- Placeholder example host is not saved as “configured”
- Workflow access is limited to people who may see leads
- You verified the email on the live site before relying on it
- Retention/deletion rules exist for stored contacts
- You will not use Add Lead to harass, spam, or phish
- You understand AGNURA does not run your n8n instance
Privacy overview: AGNURA Privacy in Plain Language.
Verification checklist
- Settings show your real webhook URL (saved)
- Analysis platform = Shopify
- At least one contact email shown
- Add Lead succeeds once
- Automation received JSON with expected
domain/ emails - No second accidental click without intent
When to escalate
- Legal/compliance review before bulk Add Lead use
- Secrets/auth on the webhook: involve your security owner
- Platform labeled Shopify incorrectly: do not force the lead; verify manually
How AGNURA helps this job
| Step | Without AGNURA | With AGNURA |
|---|---|---|
| Capture Shopify research | Manual copy | Active-tab analysis |
| Gate on email + stack | Manual checks | Add Lead enabled only when eligible |
| Send to automation | DIY script | One click POST of full analysis JSON |
| Keep a local copy only | Notes | Download JSON (no webhook) |
Compared with common alternatives
| Approach | Fit |
|---|---|
| Always-on scrapers to your CRM | Higher risk; different product job |
| Manual CRM entry | Highest control; slower |
| Analysis JSON download + upload | No live webhook; good for one-offs |
| AGNURA Add Lead | User-triggered POST for eligible Shopify tabs only |
Limits (product-true)
- Shopify exact platform name required (not every “shop-like” site)
- Requires detected email; phones alone do not enable Add Lead
- Placeholder
n8n.example.com/example.comhosts do not count as configured - Sends full analysis JSON (not a trimmed schema)
- ~15s timeout; your workflow should acknowledge quickly
- No AGNURA-hosted lead database or multi-device sync of leads
- Not email send; not auto-send; user must click
- Platform heuristics can be wrong; eligibility follows the label
Related guides
- What Is Website Intelligence for Sales and Outreach?
- How to Export Website Research as JSON
- How to Find Public Business Contact Details on a Website
- How AGNURA Detects Website Platforms and Themes
- Shopify vs WordPress Prospect Research: Which Signals Change?
- Run Your First Website Analysis
- AGNURA Privacy in Plain Language
Soft next step
Point Add Lead at a private test webhook, run one known Shopify store with a public email, click Add Lead once, and confirm the JSON body before you connect a CRM. Install AGNURA if you need the button:
Try AGNURA in Chrome
Draft in Gmail, LinkedIn, WhatsApp, and Reddit. You review every message before send.
Add to Chrome