BlogTag
Web Forms
Publish a public web form from a workspace template and share /form/SLUG. Each fill is a sent envelope.
Related product pages
Guides
Publish a Web Form from a template
Turn an Inkpacket workspace template into a public /form/SLUG. The filler does not sign in. Each submission creates an envelope and counts as one monthly envelope — Free includes 1 published Web Form at 5 packets a month.
Bulk send vs Web Forms: which tool starts the envelope
Choose between an Inkpacket bulk job and a published Web Form: you already have the emails, or strangers start themselves. Both count toward the monthly envelope cap — Free allows 5 packets a month.
Web Form intake when you don’t have the emails
Use an Inkpacket Web Form when strangers should start the envelope: publish /form/SLUG from a template, collect name and email, and count each fill toward the monthly envelope cap — Free allows 5 packets a month.
Operating a Web Form share link
After you publish an Inkpacket Web Form, the work is the share link: copy /form/SLUG, keep the PIN off the same page, close the form when intake should stop, and treat each fill as one envelope toward the monthly cap.
Public form closed copy
Disable an Inkpacket Web Form and the public page says Form closed — This Web Form is no longer accepting submissions. Existing envelopes stay. That closed-copy honesty is not a void.
Web Form Free published-form cap
Free includes 1 published Inkpacket Web Form. A second publish returns HTTP 402 and names the plan limit — not ENVELOPE_LIMIT. Disable one, or stay on Free while checkout is not open. That is published-form-cap honesty.
Web Form reminders and expiry on publish
Inkpacket Web Form reminder days (0–90) and expiration (0–365) are set when you publish. Later fills inherit that pair. Envelopes already created keep the days they were born with. That is publish-cadence honesty.
When to set a Web Form access code
Set an optional PIN when you publish an Inkpacket Web Form if a public /form/SLUG would be a leak. Later fills inherit that code. Share it separately. That is web-form-pin honesty — not an envelope access code on send.
Web Form disable versus delete
Inkpacket Web Forms have Disable form and Publish again. There is no delete control. The slug stays. Existing envelopes stay. That is disable-versus-delete honesty.
Free published Web Form 402 versus envelope limit
A second Inkpacket Web Form publish on Free returns HTTP 402 and names the plan limit. A 6th send returns HTTP 402 ENVELOPE_LIMIT. That is two-402 honesty — same status, different gate.
Why a template with zero fields cannot publish
An Inkpacket Web Form starts from a workspace template. A template with zero fields cannot be published. That is zero-field-publish honesty — not a missing Settings toggle.
Why you cannot pick a Web Form slug
Inkpacket generates a Web Form slug from the title. You do not pick it. A second publish is a second URL. That is slug-generation honesty — not a hidden rename, not checkout.