Skip to main content

Settings

The Settings tab contains project configuration options.

Custom domain​

Custom domains are a Pro feature, included on Pro and Pro+. On Free, the project stays on its *.micropage.sh address.

The Settings tab shows:

  • Type: CNAME
  • Target: cname.micropage.sh
  • Example record: www.example.com CNAME cname.micropage.sh

Add this record at your DNS provider. SSL is provisioned automatically. Subdomains only — apex domains such as example.com are not supported; redirect the apex to www at your DNS provider.

See Custom Domains for full setup instructions.

Sending domain​

Available on paid plans. Settings → Sending Domain lets you send newsletters from an address on your own domain, such as [email protected], instead of [email protected].

Enter a domain — an apex such as example.com or a subdomain such as mail.example.com — and the screen shows the DNS records to add at your provider, with a Copy all records button and a per-record table. Verification runs in the background and the status updates on its own; you don't need to keep the page open.

This is not the same setting as Custom Domain above: a sending domain covers email, a custom domain covers your website.

See Sending Domain for the full setup, statuses, and troubleshooting.

Deploy tokens (Pro+)​

Under Settings → Deploy tokens you can create per-project deploy tokens for CI (for example GitHub Actions). A token lets CI (micropage projects deploy) or the MCP server upload assets, create builds and publish this project without an interactive login. Treat it like a password: while the token is pinned to one project in the CLI and MCP, it currently carries your account's access, so store it only in CI secrets and revoke it if it may have leaked.

  • Tokens are shown once when created; store them in your CI secrets.
  • You can set an optional expiry; leave it empty for a token that does not expire.
  • Revoke a token anytime if it may have leaked.

Use the project UUID, the token, and run micropage projects deploy in CI—see CI/CD and the GitHub Actions walkthrough.

Forms​

Settings → Forms lists every form found in your saved markup, with the page it appears on and a Newsletter toggle. The list is available on all plans; webhook notifications inside this section are Pro+.

Newsletter​

The Newsletter toggle governs subscriber capture for a form. With it on, each submission to that form creates a persistent subscriber record, listed under Newsletter → Subscribers, instead of only a one-off entry in Form Submissions. Capture is available on all plans, including Free.

Markup does not control this. newsletter: true|false in a form block only selects the confirmation wording shown after a submission — it never starts or stops subscriber capture. See Newsletter for the full split.

A newsletter form also carries sender details, edited under Newsletter → Sender settings:

  • Sender name — the display name recipients see in their inbox.
  • Sender address — the local part of the sending address, the hello in [email protected]. Read-only until a sending domain is verified; until then the sender is [email protected].
  • Reply-to address — where replies to the newsletter are delivered.
  • Postal address — printed at the bottom of every newsletter email, as anti-spam law requires.

Webhook notifications​

Enter an https:// URL to receive a POST request for each new form submission.

To add a webhook URL:

  1. Open Settings → Forms.
  2. Click Add webhook URL.
  3. Enter your endpoint URL (must start with https://).
  4. Click Save webhook URL.

Once saved, every new submission triggers a POST to that URL. The request body is JSON:

{
  "id": "uuid",
  "project_id": 123,
  "form_name": "Contact",
  "page_url": "/",
  "form_index": 0,
  "payload": { "name": "Jane", "email": "[email protected]" },
  "submitted_at": "2026-04-02T12:00:00Z"
}

The request also includes an X-Micropage-Submission-Id header with the submission UUID, which you can use to verify the source or deduplicate retries.

To change or remove the URL, use the Change URL or Remove webhook buttons in the same section.

Deleting a project​

The Settings tab includes a Delete Project option.

Deleting a project:

  • removes all builds
  • removes all uploaded files
  • removes all form submissions
  • is permanent and cannot be undone

You will be asked to confirm by typing the project name before deletion proceeds.