Sentway does not make your original Claude artifact URL email-gated. Instead, ask Claude to create or adapt a standalone version, publish it through Sentway, and configure a site-wide email capture gate before final publication. Your recipients open a new URL, not the original Claude link.
Email before entry, not a form after entry
Claude can publish and share artifacts; you do not need Sentway simply to share one. An email gate is useful when you deliberately want visitors to provide an address before seeing a separately hosted resource. It is not an embedded newsletter form, and it does not track visits to your old Claude link.
Choose the access pattern that matches your audience. The distinctions below matter more than the appearance of the email field.
Compare the five approaches
Public link: visitors enter without providing an email. Choose this for maximum reach and easy sharing.
Email capture: visitors enter an address before entry. Without verification, this is whatever they type, potentially mistyped or invented.
Verified email gate: visitors follow a magic link sent to their inbox before entry. This proves inbox control, not legal identity. It does not restrict entry to particular addresses by itself.
Allowlist: only approved addresses or domains can enter, with email verification required. Choose this for named client recipients rather than an open lead magnet.
Embedded form: visitors see the content first and choose whether to submit details afterwards. A submitted form is a different record from passing an access gate.
Set up email capture in Claude
1. Create a free Sentway account, then connect Sentway through the Claude Connector Directory. Sign in with that account and approve the connection. You can find setup help in the links below.
2. Ask Claude to adapt your calculator, guide or quiz into standalone browser-ready HTML or JSX. Have it identify any features that depend on Claude's model, storage or connected apps before promising an equivalent experience.
3. Have Claude use create_site and save_page to prepare the site and its page. Save the main page at the root path. Explain what visitors will receive and why you want an email address.
4. Before publication, ask it to use set_gate_access with mode: "email_capture". Add require_email_verification: true if inbox verification matters. This is the site's primary gate, not an extra form inserted into the page.
5. Run publish_site only after setting access. Configuring the gate alone does not change the published experience. If you later change access, publish again before expecting visitors to meet the new setting.
6. Test the new URL yourself in an incognito window, without an owner session. Check that entry is blocked first and that the expected email or magic-link step works. Then share the new URL, replacing the old Claude link wherever appropriate.
Keep three records separate. get_analytics provides aggregate site activity, not an address book. get_submissions returns submitted forms, not a list of everybody who passed an email gate. A gate entry does not automatically create a form submission.
Gate identity belongs to visitor records. Detailed visitor listing through list_visitors and per-visitor readback through get_visitor_activity require Pro, as does the Visitors view in the app. On Free, do not expect those tools or that view to reveal email-gate-only identities. Upgrade if that readback is essential to your workflow.
Free includes aggregate analytics and limited form-submission visibility. That does not turn gate entries into submissions, or make get_submissions an alternative visitor export. Confirm your plan before building a lead follow-up process around named records. No marketing integration or automated mailing is assumed here.
Lead magnet or interactive assessment: offer a budgeting calculator with a clear explanation of its value before asking for email. If people cannot judge the benefit first, a gate may reduce signups. Consider a separate public preview or a normal form after the result instead. A site-wide gate also covers pages inside that site, so do not assume its homepage remains a free preview.
Private client resource: publish a standalone onboarding guide and choose verified access if knowing the inbox matters. If only your client team should enter, use an allowlist rather than accepting any verified email. Neither option prevents an authorised visitor from copying or forwarding what they see.
Privacy and expectations before you share
Tell visitors why you request email, how you will use it, and where to find your privacy information. Collect only necessary details. Access verification is not automatic permission for newsletters or sales outreach; establish appropriate consent for the intended use rather than treating entry as blanket agreement.
Sentway enforces the gate on the server before delivering protected content bytes. That controls initial access, not screenshots, copying or redistribution afterwards. It does not guarantee regulatory compliance. A verified address is not a verified person, and opening a page is not proof of reading or understanding it.
When this is not the right fit
Keep native Claude sharing when it already suits your audience. Prefer a public link if reach matters more than collecting addresses, or send a downloadable file when readers need something offline. Avoid adding a sign-in hurdle just because it is available.
Claude-native model calls, app connections and storage do not automatically transfer to a standalone page. Ask Claude to explain what must be removed, replaced or separately implemented. If those features are the point of your artifact, staying in Claude may be the better choice.
A prompt you can paste
Free plan
Build a standalone browser-ready version of this [calculator/guide/quiz] suitable for publishing on Sentway. Explain features that rely on Claude's own runtime and won't port unchanged. Use create_site and save_page, then set_gate_access with mode: "email_capture" and require_email_verification: true. Run publish_site only after setting access. Give me the new Sentway URL and an incognito test checklist for me to run. Explain where I can see captured visitors on my plan and do not claim a gate entry is a form submission. Do not claim you have independently click-tested the live page.
Produces: A standalone page with verified email requested before entry, a new URL and a checklist you run yourself.
The publishing and email-gate tools are available on Free. Reading detailed visitor records requires Pro; this prompt does not request those paid readbacks.
No. You share a new Sentway URL. Your original Claude link keeps its own sharing rules and is not monitored or gated by Sentway.
Can I collect email without verification?
Yes. Plain email capture accepts the visitor-entered address. Enable verification when you need evidence of inbox control, not proof of legal identity.
Can I use the email gate on Free?
Yes. Publishing and configuring email access are available on Free. Listing captured visitor records and reading detailed per-visitor activity require Pro. Form-submission visibility is separate and limited on Free.
Does entering the gate subscribe someone to my newsletter?
No. Gate entry is not automatically a newsletter subscription or a form submission. Explain your intended use and establish appropriate consent before sending marketing.
Should I put an email form inside the page instead?
Often, yes. Let people experience value first when reach and trust matter more than collecting an address before entry. Use a form for optional responses, and a gate for an explicit access condition.