Developers Modules

Developers

Modules

Frontpage CLI module commands: list, docs, request-setup, enable, disable, archive, and config, plus form destinations, Google reviews, Stripe, and Square ordering.

Grammar

frontpage modules <key>                 # that key's CLI usage (exit 2)
frontpage modules <key> <action> [flags]
frontpage modules list|docs|request-setup|enable|disable|archive|config …

Key-first and verb-first both work: frontpage modules google_reviews enable is the same as frontpage modules enable google_reviews. Bare frontpage modules <key> prints that key's actions, not the markup how-to. frontpage modules docs <key> stays the agent markup guide.

JSON: add --json. Usage still exits 2. Secrets are never returned (masks only). See also Content & settings.

Generic actions

Articles uses section commands for its lifecycle; see Articles below.

Action What it does
docs Print markup / agent how-to for the key
request-setup Ask the owner to finish setup in the editor when the module needs it. Articles needs no setup; this request makes no changes.
enable / disable / archive Turn the module on, off, or archive it
config --config '{…}' Patch whitelisted JSON. Do not write placeId this way.

Keys

Jump to a key for its extra actions. Other keys stay generic-only until a later phase.

Key CLI today Not in this CLI yet
callbar Generic + get / set --phone --sms --call None
forms Generic + get / set --instance / destinations Do not target default. Token write is admin.
booking Native Booking actions and calendar connections None
signups Generic + get / set --notify-email Confirmations are available on every plan within the site’s monthly Email sends allowance.
articles modules docs articles; content lives on frontpage articles … Use section commands to turn Articles sections off or on; no setup needed.
printify Generic docs / request-setup. Connect is in Modules: paste a personal access token. No CLI connect. Do not paste the token into chat or a site file.
google_reviews Generic + connect / resolve / status / list-reviews / hide / show / set-stars / set-sort / set-weight / reset-weights / write-review-url / refresh / disconnect Autocomplete (hub only). Do not write placeId via config.

If an action is listed as “not in this CLI yet,” use Modules or the editor. Not frontpage prompt as a substitute. Ask-widget scores: frontpage inbox google_reviews.

Catalog/cart live in Store; Stripe, Pay now and invoices live in Payments (frontpage payments connect).

Examples

frontpage modules google_reviews
frontpage modules google_reviews connect --place-id ChIJ…
frontpage modules google_reviews list-reviews --stars 4,5
frontpage modules google_reviews docs
frontpage modules google_reviews enable
frontpage modules google_reviews request-setup --reason "You asked for Google reviews. Pick your listing so we show the right ones"

frontpage modules callbar get
frontpage modules callbar set --phone +1… --sms no
frontpage modules callbar set --call no --sms yes
frontpage modules forms get
frontpage modules forms set --instance lead-gen --notify-email hi@example.com
frontpage modules forms destinations
frontpage modules forms connect-destination privyr --token "https://www.privyr.com/api/v1/incoming-leads/…"
frontpage modules forms attach-destination --instance lead-gen --provider privyr

frontpage modules ordering connect --no-open
frontpage modules ordering status
frontpage payments connect --no-open

frontpage modules docs forms
frontpage modules enable forms
frontpage modules config callbar --config '{"phone":"+1…"}'
frontpage payments connect --no-open
frontpage articles list

Articles

Articles needs no setup. Creating a section makes it active. Draft articles stay unpublished. Use the existing section commands to create a section, turn it off, or turn it back on:

frontpage articles create-section --label "Blog" --route blog
frontpage articles archive-section --section blog
frontpage articles restore-section --section blog

Use create-article or content get|set for content. Generic modules enable|disable|archive articles does not control sections. Frontpage manages article routing. Use the Articles commands to create sections and edit content; do not read or edit the managed routing file. See Articles content commands.

GET connection summary

GET /api/v1/sites/:slug/modules/:key may include connection: { kind, ready, display } when the module has an external prerequisite (Stripe, Square, or a Google listing). Display is masks and public listing fields only. No tokens, no Stripe account ids, no review bodies.

callbar

Typed get / set write the same whitelist as frontpage modules config callbar --config '{…}' (phone, sms, call, label). sms and call are each yes or no. Text-only is --call no --sms yes. Call-only is --sms no. Turning both off is coerced to Call only so the bar never goes blank.

frontpage modules callbar
frontpage modules callbar get [--site <slug>] [--json]
frontpage modules callbar set --phone +1… [--sms yes|no] [--call yes|no] [--label "Call"]
CLI What it does
get Print phone, call, sms, label. Human lines, not a JSON dump. Add --json for agents.
set --phone +1… [--sms yes|no] [--call yes|no] [--label "Call"] POST action=set. Same sanitizeConfigPatch as the hub.

Generic docs, enable / disable / archive, and config --config still work.

This CLI will not invent a second call bar (markup is data-fp-callbar in files or the editor agent) or accept unknown leftover flags (exit 2).

frontpage modules callbar get
frontpage modules callbar set --phone +14085551234 --sms no
frontpage modules callbar set --call no --sms yes
frontpage modules callbar set --label "Call us"
frontpage modules config callbar --config '{"phone":"+14085551234"}'

forms

Use Forms when visitors send information for the business to review or reply to. Examples include contact and quote requests, callback requests, project briefs, partnership inquiries, feedback, applications, and event RSVPs that collect responses.

Manage each form by its slug. get without --instance lists all forms. Pass --instance with the form's slug when you use set. You can also send a copy of submissions to a CRM you connect.

frontpage modules forms
frontpage modules docs forms
frontpage modules forms get [--instance <slug>]
frontpage modules forms set --instance <slug> [--notify-email <address>] [--confirm yes|no] [--confirm-template <id>]
frontpage modules forms destinations [--instance <slug>]
frontpage modules forms connect-destination <privyr|hubspot|pipedrive> --token "…" [--lead-source "…"]
frontpage modules forms attach-destination --instance <slug> --provider <id>
frontpage modules forms detach-destination --instance <slug> --provider <id>
frontpage modules forms remove-destination <id> --yes
frontpage modules forms request-destination-setup <id> --reason "…"

Bare frontpage modules forms prints this key's CLI usage (exit 2). frontpage modules docs forms stays the markup / agent how-to. JSON: add --json. Secrets are never returned (last4 masks only).

Instances

CLI API What it does
get GET …/modules/forms List instances (id, status, notifyEmail) plus destination masks. With --instance, print that form.
set --instance <slug> [--notify-email <address>] [--confirm yes|no] [--confirm-template <id>] POST action=set Sets the owner notification inbox or the visitor confirmation for one form.

--notify-email sets the owner's inbox for new submissions. A visitor confirmation goes to the email the visitor entered. Confirmations are available on every plan, including Free, and use the site's monthly email allowance. Delivery checks and duplicate protection still apply.

frontpage modules forms get
frontpage modules forms get --instance lead-gen
frontpage modules forms set --instance lead-gen --notify-email hi@example.com
frontpage modules config forms --instance lead-gen --config '{"notifyEmail":"hi@example.com"}'

Visitor confirmations

Choose off, a simple confirmation from Frontpage, or a saved email template. Use an empty --confirm-template value to clear the saved template. After clearing it, --confirm yes sends a simple confirmation and --confirm no turns confirmations off. Saved templates can use {{first_name}}, {{last_name}}, and other tokens that match named form fields.

# Off
frontpage modules forms set --instance lead-gen --confirm no --confirm-template ""
# Simple confirmation
frontpage modules forms set --instance lead-gen --confirm yes --confirm-template ""
# Saved email template
frontpage modules forms set --instance lead-gen --confirm no --confirm-template <id>

Destinations (CRM copies)

Two layers. Connect a CRM once per site (store the secret). Then attach each form that should also send a copy. Connecting does not attach every form. Frontpage still stores the lead and still emails notifyEmail. Removing a destination never deletes the Leads inbox.

v1 providers: privyr, hubspot, pipedrive. One secret per (site, provider). A second call to connect-destination replaces it. Write needs an admin API key. request-destination-setup is editor. It only lights the amber bar in the Frontpage editor so the owner can paste there. frontpage modules request-setup forms stays a no-op (forms are auto-active).

What to paste

Privyr is a URL. HubSpot and Pipedrive are tokens. The CLI flag is still --token for all three. For Privyr the value is the Incoming Webhook URL, not a separate key. Do not invent an OAuth dance or a retired API key. Do not put any of this in markup.

Provider What to copy Where it is
privyr The full Privyr Webhook URL Privyr web: Automations → Lead Sources → search Webhooks → open Incoming Webhook → copy the box labeled Privyr Webhook URL (starts with https://www.privyr.com/api/v1/incoming-leads/). There is no Authentication Token on that page. The URL is the secret. Do not use Outgoing Webhooks (Lead Automations). Do not paste a URL from any other host. Official: webhooks help.
hubspot Bearer token (service key or private-app access token) with crm.objects.contacts.write You need Super admin or Developer tools access in HubSpot. Navigate to Development → Keys → Service keys → Create service key. Add new scope. Search for crm.objects.contacts.write and turn only that on. Create the key → Show → copy it. Or: Development → Legacy apps → Create legacy app → Private → Scopes → Add new scope → crm.objects.contacts.write → create the app → Auth → Show token. Do not use the retired hapikey. Official: service keys, legacy private apps.
pipedrive Personal API token Profile (top right) → Company settings → Personal preferences → API. Token is per user per company. If you do not see API, a company admin must enable use API on that user’s permission set: Settings → Manage users → Permission sets. Official: find the API token, enabling API.

CLI verbs

CLI API Role What it does
destinations [--instance <slug>] GET …/modules/forms → destinations Editor Connected providers (last4 only) and per-form attach state, including last send error. Human output prints (no destinations) when none are connected. Token never printed.
connect-destination <id> --token "…" [--lead-source "…"] POST action=destination_connect Admin Store the secret. For Privyr, --token is the Incoming Webhook URL. Second call replaces it. Optional --lead-source labels the copy in Privyr (HubSpot / Pipedrive ignore it). Default lead source is {subdomain} website. {form label}.
attach-destination --instance <slug> --provider <id> POST action=destination_attach Admin This form also sends a copy. Connect first (409 if the secret is missing). Cannot attach default, booking, or signup.
detach-destination --instance <slug> --provider <id> POST action=destination_detach Admin Stop the copy for that form only. Token stays. Other attached forms keep sending.
remove-destination <id> --yes POST action=destination_remove Admin Delete the secret and every form copy for that provider. disconnect-destination is the same verb. No --yes → exit 2 with the confirm sentence. Leads stay in Frontpage.
request-destination-setup <id> --reason "…" POST action=destination_request_setup Editor Lights the amber bar in the Frontpage editor so the owner can paste. Does not change form status. Does not store a secret. request-setup forms stays a no-op.

GET /api/v1/sites/:slug/modules/forms includes destinations: { providers, byInstance }. Providers list every catalog CRM (connected or not) with last4, optional leadSource, and a pending request if the amber bar is waiting. byInstance is per-form attach rows: enabled, lastOkAt, lastFailedAt, lastError. No tokens, no request bodies.

What Frontpage sends

After the lead is stored and the owner email is queued, Frontpage POSTs each enabled attachment. A CRM failure never drops the Frontpage lead. Retries are inside that send (4 attempts, 1s / 2s / 4s backoff, 5s per attempt). 400 / 401 / 403 fail immediately. 429 and 5xx retry. Last error (≤240 chars, no token, no PII) shows on that form, on the Destinations card, and on frontpage modules forms destinations. The next 2xx clears it. Frontpage does not email the owner for a CRM failure.

Provider Send Mapped fields
Privyr POST the owner’s allowlisted https://www.privyr.com/api/v1/incoming-leads/{a}/{b} (no X-TOKEN header) name (required; fallback Website visitor), source, email / phone when present, remaining fields as other_fields.
HubSpot POST https://api.hubapi.com/crm/v3/objects/contacts with Authorization: Bearer Contact properties only: email, firstname, lastname, phone, company, website, address when present. Arbitrary extra keys are not posted (HubSpot 400s unknown properties).
Pipedrive POST https://api.pipedrive.com/api/v2/persons with x-api-token (not a query string) name (fallback Website visitor), primary emails / phones when present. Custom field hashes are not posted in v1.

Use first_name and last_name for names and phone for a phone number. CRM copies apply to active Forms that you attach to the destination.

This CLI will not:

  • Invent form markup, a honeypot, or an action= / webhook URL in HTML.
  • Accept an arbitrary webhook host (SSRF). Privyr is the exception: only https://www.privyr.com/api/v1/incoming-leads/{id}/{id}. HubSpot and Pipedrive send URLs stay code constants.
  • Print or log the secret. GET bodies, --json, and audit payloads stay masks only.
  • Set a comma-separated notify list (one address per form).
  • Target default, booking, or signup for a destination.
  • Use request-setup forms as a stand-in for a CRM secret.
  • Attach every form when you connect. Attach is a second, explicit step.
frontpage modules forms destinations
frontpage modules forms connect-destination privyr --token "https://www.privyr.com/api/v1/incoming-leads/…"
frontpage modules forms connect-destination hubspot --token "…"
frontpage modules forms connect-destination pipedrive --token "…" --lead-source "Acme website"
frontpage modules forms attach-destination --instance lead-gen --provider privyr
frontpage modules forms detach-destination --instance lead-gen --provider privyr
frontpage modules forms remove-destination privyr --yes
frontpage modules forms request-destination-setup hubspot --reason "You asked to send leads to HubSpot"

frontpage modules docs forms

Human connect text: Connected privyr ••••7k2p. Attach: lead-gen will also send a copy to privyr. Remove: Removed privyr. Leads still land in Frontpage.

Markup reminder

<form data-fp-form="lead-gen" data-fp-success="Thanks. We'll reply within one business day.">
  <label>First name <input type="text" name="first_name" autocomplete="given-name" required /></label>
  <label>Last name (optional) <input type="text" name="last_name" autocomplete="family-name" /></label>
  <label>Email <input type="email" name="email" autocomplete="email" required /></label>
  <label>Phone <input type="tel" name="phone" autocomplete="tel" /></label>
  <label>Message <textarea name="message" rows="4"></textarea></label>
  <button type="submit">Send</button>
</form>

data-fp-form binds the form to Frontpage, which handles submission and adds the spam trap. Give every field a name and include email or phone. Mark fields required based on what the business needs. Leave action, method, onsubmit, and custom submission JavaScript out of the form. Use Booking when visitors choose an available time or stay, Mailing list when they subscribe to updates, and Payments when they need to pay. For the full reference, run frontpage modules docs forms.

booking

Booking and CLI access are included on every plan, including Free. Bookings supports Google Calendar, Outlook Calendar and iCal links. Customer lookup uses customers_list and customer_get through the shared Booking actions. These return visible contact choices only, without People history, notes or marketing controls. CLI equivalents are frontpage modules booking customers list --search TEXT and customers get --id UUID.

On sites with Bookings enabled, manage appointments, arrival-and-departure stays, customer questions, members, spaces, calendar blocks and reservations through the same Booking actions as the workspace. Start with status and the current module docs.

frontpage modules docs booking --site <slug>
frontpage modules booking status --site <slug>
frontpage modules booking types list --site <slug>
frontpage modules booking resources list --site <slug>
frontpage modules booking connections list --site <slug>

The native endpoint is POST /api/v1/sites/:slug/booking with a named action. Use complete values, the current expectedRevision for updates, and one stable requestKey per write. After a timeout, retry the same input and key. Changed input starts a new operation. The workspace, CLI and internal agent use this shared contract; existing site-role and plan rules still apply. See the CLI package's BOOKING.md and current module docs for all actions and input schemas.

AreaActions
Website presentationpresentation_get, presentation_save for the same-site customer management page
Setupstatus, settings_get, settings_save, appointment_hours_get, appointment_hours_save, activation_save
Types and spacestypes_list, type_save, resources_list, resource_save, members_list; restricted member catalogs use type_catalog and resource_catalog
Calendarcalendar, availability, block_save, block_remove
Reservationsbookings_list, booking_get, booking_create, booking_reschedule, booking_accept, booking_decline, booking_cancel, booking_withdraw
Connectionsconnect_request opens the human setup flow. Owned accounts, calendar selections, refresh and disconnect use the named connection actions in the module docs.

status.businessReady means a valid saved business time zone and notification email; configured only means a settings record exists. settings_save requires a valid nonempty notifyEmail. Read and preserve the other settings and activation state. Use a confirmed IANA time zone rather than the CLI or server's zone. appointment_hours_get returns hasSavedHours for an explicit personal schedule, including a saved empty schedule. The first appointment_hours_save needs a nonempty valid schedule and completed business settings; later saves may close all hours. Each caller acts as their own joined member. Keep current revisions and exact retry keys. Google and iCal setup are optional. connect_request creates the existing human handoff in the editor status bar and workspace overview. Skipping a connection creates no task. The workspace Admin’s initial Finish setup invokes the existing activation operation after required business settings and personal hours are saved. Individual saves, personal onboarding and calendar reconnects preserve activation, including a deliberate pause. Tools still activate only when requested. Setup does not publish source. API keys, CLI and MCP retain their site grants and actual roles; the audited platform-admin workspace override does not expand them.

Lists return nextCursor; retain filters when paging. Calendar queries accept up to 31 days of ISO instants, with member and space filters. Appointments use times; stays use local arrival and departure dates plus the type's check-in and checkout times. Each type sets its own extra questions and confirmation policy. Name and email are required. Pending requests hold availability until accepted, declined or expired. Opening an email link opens the booking; it does not accept it. Customer changes use the verified management flow.

Activity and approval count

bookings_list returns one summary per booking in descending lastActivityAt order, with a stable booking-ID tie-break. lastActivityAt is an ISO instant; lastActivityAction is the latest native lifecycle action. Creation, decisions, cancellation, rescheduling, date-change actions and expiry move that booking. Reads, management-link recovery and delivery or sync retries do not. Retain the same site/search/status while passing nextCursor unchanged as query.before.

Editors and Admins receive reviewCount from status: the site-wide count of unexpired new booking requests awaiting approval. It excludes date-change requests and delivery/calendar problems and does not depend on list filters or pagination. The workspace Activity badge says N to review and hides zero. API start/end values remain exact ISO instants; the workspace uses the booking's business time zone and shows the date once for a same-day range.

Appointment start times

Set startIntervalMinutes in the complete type_save value or the JSON file for frontpage modules booking types save. Use null for Automatic, which matches the current appointment length, or 5, 10, 15, 20, 30, 45 or 60 for a fixed interval. Omit it on an update to keep the saved setting. New types default to Automatic.

For example, durationMinutes: 60 with startIntervalMinutes: 30 allows hour-long appointments to start on the hour or half hour. Starts align to the business's local clock. Buffers and conflicts remove times without shifting the grid. New bookings and rescheduling use the type's current rule. Stays are unchanged. Read availability and use an exact returned time; off-grid requests return slot_unavailable.

Connect calendars

Workspace Connect opens Google sign-in directly and returns to its starting step. The shared editor then chooses the provider calendar and Person or Room, space or location. Person targets the connecting member; shared spaces require Admin access. provider_calendar_save accepts an optional label, which defaults to the provider-calendar name. Editing the saved calendarId uses the same operation and current revision. It replaces imported busy times and queues removal of Frontpage-owned events from the prior calendar before adding them to the selected one, without booking emails or Activity changes. An active delivery can return calendar_busy; retry the same input/key after it ends. iCal connection_save also accepts ownership with its label and resource IDs.

The saved calendar has one Disconnect calendar action. Removing its final provider selection clears the unused local grant; other selections keep access. The account-disconnect operation remains available for explicit whole-account removal and unfinished connection cleanup.

Calendar consent and private iCal links stay in the human Connections flow. Never put credentials, OAuth codes or private export URLs in prompts, CLI files or agent tools. Members must have joined the site and connect their own calendars. Admins can connect shared calendars to spaces. Connection requests appear in the editor status bar and workspace overview until the responsible member finishes setup.

Read status.providerSetup.google and status.providerSetup.outlook before offering new provider setup. Only available connections appear in the workspace; unavailable setup calls return provider_unavailable. Native Booking and iCal imports work independently of Google and Microsoft approval. Existing connections remain manageable.

Google Calendar and Outlook Calendar import busy times. If you grant write access, choose a calendar where Frontpage will create confirmed booking events. Some Microsoft 365 organizations require admin approval. Pending requests stay in Frontpage. Other members and visitors do not receive private event details. Only the connecting human can open their provider event details.

iCal links import busy times for appointments and stays under either confirmation policy. The booking type alone chooses instant confirmation or manual acceptance of customer requests. An import never sends bookings back and cannot guarantee real-time conflict prevention across platforms. A saved .ics file is a snapshot; automatic sync needs its live export URL.

Successful calendar checks target 15 minutes, through the five-minute dispatcher, plus provider delays and retry backoff. Refresh permits two attempts per calendar per rolling 15 minutes; failures count and the same retry identity does not spend another attempt. Recent last-good data stays usable during refresh or temporary failure, for at most 30 minutes. Missing, revoked, stale or uncovered data keeps dependent bookings unavailable. Connection summaries return safe health status and feedback. Normal disconnect stops checking that source and preserves native bookings and manual blocks.

Build the website form

Configure and publish a booking type first. Use the shared runtime and these containers; style them with the site's own CSS, fonts and layout. The runtime fills types, dates, availability, per-type questions, review and email verification from saved configuration. Keep the required hooks and show pending, confirmed and error states accurately. Do not invent availability or use the retired data-fp-form="booking" collector.

<section data-fp-booking>
  <div data-fp-booking-types></div>
  <div data-fp-booking-dates></div>
  <div data-fp-booking-availability></div>
  <div data-fp-booking-fields></div>
  <div data-fp-booking-review></div>
  <p data-fp-booking-status role="status" aria-live="polite"></p>
  <button data-fp-booking-submit type="button">Review booking</button>
</section>
<script defer src="https://app.frontpage.host/booking/runtime.js"></script>

The optional data-fp-booking-type-id on the root fixes one published type. Customer management links require mailbox proof. Calendar credentials and private event details never enter public markup.

Booking form appearance

Booking provides custom dropdowns and default field styling in the soft fp-defaults CSS layer, like Store. Your site CSS and component or utility layers override the appearance. Match the site's fonts, colors, fields and spacing. Use an authored root class with Astro <style is:global> or :global(...) for runtime-created controls; they do not carry the page's scope attribute.

Field hooks include .fp-booking-field, .fp-booking-label, .fp-booking-control-slot, .fp-booking-control, .fp-booking-help, .fp-booking-error and .fp-booking-address. Dropdown parts use .fp-booking-select, -field, -trigger, -value, -caret, -menu, -list and -option, with .is-active, .is-selected and accessible state attributes. Keep hidden backing values and disabled steps intact; do not show native selects or add a second dropdown implementation.

Optional tokens include --fp-booking-control-bg and --fp-booking-control-fg, --fp-booking-selected-bg and --fp-booking-selected-fg, --fp-booking-border, --fp-booking-radius, --fp-booking-focus and --fp-booking-control-height. Ordinary CSS may override every visual default.

To change field wrapper markup, place one optional <template data-fp-booking-field-template> inside the Booking root, outside its filled containers. Its single outer element must contain a <label data-fp-booking-label> and a data-fp-booking-control-slot. Optional data-fp-booking-label-text, data-fp-booking-help and data-fp-booking-error bindings let you keep label decoration and place help or errors. The runtime supplies real controls, accessible IDs, values and validation. You control the wrapper, layout and styling; Booking keeps availability, verification and reservation behavior.

Inspect every field type, dropdown, selected and focus states, disabled controls, loading, empty, errors, review, email verification and success. Test desktop, mobile and two independent forms on one page. A successful build does not verify the design.

Visual availability and custom pickers

Appointments show available dates and time buttons. Stays use check-in and checkout directly, without an extra Stay dropdown. The default starts at the first available date. Availability dots, the selected-time checkmark and full stay-range highlights help visitors see what is available and what they chose. These are editable starting points, not fixed designs.

Style .fp-booking-picker, .fp-bp-day-face, .fp-bp-time-face, .fp-bp-available-dot, .fp-bp-selected-mark and the .is-selected/.is-range states. Optional variables include --fp-booking-available-color, paired --fp-booking-date-selected-bg/--fp-booking-date-selected-fg, paired selected-time colors, and --fp-booking-range-bg. Use real site tokens with valid fallbacks. Keep keyboard focus separate from selection, and keep .is-pending separate from .is-unavailable. A loading or failed read must not look like a fully booked calendar.

To replace the whole picker, use data-fp-booking-picker="custom" on the root and author its date/availability containers. After frontpage:booking-ready, call FrontpageBooking.getPicker(root). Its subscribe(render) returns an unsubscribe function. Use showMonth, nextAvailable, choose, selectArrival, selectDeparture, selectTime, selectResource, selectType and refresh rather than inventing slots or scraping hidden values. The current module docs describe their signatures and safe state fields. Snapshots contain availability and selection, not customer details, codes, signed receipts or private calendar events. The runtime keeps verification, submission and exact retries.

Style review, verification and results

Completion opens one shared dialog: review, required email verification, then the result. It is centered on desktop and full screen on mobile, with one scrolling body. Close or Back retains the selected booking and answers; returning to code entry does not send another email. No availability is held until verified submission.

The default shell uses .fp-booking-dialog, .fp-booking-dialog-header, .fp-booking-completion-steps, .fp-booking-summary and the panel hooks below. Set data-fp-booking-dialog-label to the business name if wanted. Root variables --fp-booking-dialog-width, --fp-booking-dialog-radius, --fp-booking-dialog-shadow, --fp-booking-dialog-backdrop and --fp-booking-summary-bg customize soft defaults. Ordinary global site CSS can replace every visual rule.

To replace the whole shell, put <template data-fp-booking-dialog-template> inside the Booking root, outside filled containers. Give it one outer <dialog>, a data-fp-booking-dialog-content container and a button data-fp-booking-dialog-close. Panel, detail and field templates still control its contents. The runtime moves the original review, status and submit controls into the shell while open, so avoid direct-child-only selectors. Native dialog supplies focus containment and an inert background. Set data-fp-booking-completion="inline" for an authored inline layout. These options change presentation, not verification, reservation rules or retry identity.

The form continues through a review summary, six-digit email check and pending or confirmed result. Shared panels use .fp-booking-panel, .fp-booking-details, .fp-booking-actions, .fp-booking-action, .fp-booking-notice and .fp-booking-code. The current screen appears in data-fp-booking-panel-state. Defaults stay in fp-defaults; normal site CSS can replace every visual choice.

For different panel markup, put <template data-fp-booking-panel-template> inside the root, outside filled containers. Its single outer element contains data-fp-booking-panel-title, data-fp-booking-panel-content and data-fp-booking-panel-actions; data-fp-booking-panel-description is optional. A data-fp-booking-detail-template controls rows through data-fp-booking-detail-label and data-fp-booking-detail-value. Field templates also apply to code and recovery inputs. The runtime fills safe text and binds the real controls; incomplete templates use the functional default.

Brand the customer management page

Build a normal same-site page with data-fp-booking-manage, data-fp-booking-manage-body, data-fp-booking-status and the same runtime script. Style its outer page and shared panels together. Add noindex and no-referrer metadata. An optional data-fp-booking-manage-picker-template replaces the date-change picker using the same safe controller.

Publish that page first. Read presentation_get, then use the returned presentation revision and a stable request key for presentation_save with managementPath. CLI equivalents are frontpage modules booking presentation-get and presentation-set --file management.json --revision REVISION --request-key KEY. Only admins can change the same-site path. An empty path restores the built-in page. Private link proof stays in the fragment and current history entry for reload, never in a query, public markup or custom picker state.

Booking events can send a customer receipt and a separate business notification. When both use the same inbox, both arrive there; business subjects say Business notification. Customer links manage a reservation, while business links require workspace access. Keep required email verification and recipient rules intact. Check the entire flow, including errors and recovery, on desktop and mobile.

signups

Mailing list confirmations are available on every plan, including Free. Use signups set to manage the notification address and simple confirmation. Use modules config signups to select a saved template.

frontpage modules signups
frontpage modules signups get [--site <slug>] [--json]
frontpage modules signups set [--notify-email] [--confirm yes|no]
CLI What it does
get Shows the notification address and simple confirmation setting.
set [--notify-email] [--confirm yes|no] Saves the notification address or simple confirmation setting. HTTP 402 applies when the site’s configured Email sends allowance is zero.

Generic docs, enable/disable/archive, and config --config still work.

This CLI will not send newsletters (signups is capture-only) or invent signup markup (data-fp-form="signup").

frontpage modules signups get
frontpage modules signups set --notify-email hello@example.com --confirm no

To select a saved template, use its ID.

frontpage modules config signups --site YOUR_SITE \
  --config '{"confirmTemplateId":"TEMPLATE_UUID","confirmEnabled":false}'

Use an empty confirmTemplateId to clear the saved template. Set confirmEnabled to true for the simple confirmation or false to turn confirmations off.

printify

The owner connects a Printify shop they already have, including one that already sells on Shopify or eBay. Do not create a new empty Printify shop. Do not disconnect the other sales channel. One shop connects immediately and the panel names the shop, the channel, and the product count. Several shops wait until the owner picks. Choosing another shop later adds it. It does not replace the shop already synced.

Products sync into Store. The customer pays on this site through Stripe. After the payment succeeds, Frontpage sends that order to Printify to print and ship. Sync reads Printify. It does not edit, unpublish, or delete products there. Do not insert into the shop tables and do not write src/content/products/. Nothing imports a CSV or a Printify export.

The token is pasted in Modules, not in chat. Printify shows it only once.

  1. In Printify, open the account menu and click Connections.
  2. Under API tokens, click Generate.
  3. Name the token, leave All scopes selected, and click Generate token.
  4. Copy it.
  5. In Frontpage, open Modules, then Printify, paste the token, and click Connect Printify.

If it is not connected, call request_module_setup("printify", reason) and tell the owner those steps. Do not ask them to paste the token here. frontpage modules docs printify is the agent how-to. manage_store list_items is one page of 25 after sync. Read total. Do not page the shop into the chat. The public grid is documented under Search, price, and More.

A product Printify no longer sells is archived in Store only. If Printify still sells a product that was archived in Store, the next sync brings it back. Publish in the editor publishes the website. It does not publish Printify products.

A paid line goes to the Printify shop on that product's listing. Do not tell the owner to change Printify order approval. Shipping for a cart that is entirely Printify products uses Printify standard shipping. Mixed carts add each shop's standard rate. Disconnect stops new syncs and stops new orders from going to Printify. Products already in Store stay. Nothing in Printify is deleted.

frontpage modules docs printify
frontpage modules request-setup printify --reason "Connect the Printify shop you already have"

google_reviews

Owner-supplied Place ID or Maps URL. The server resolves the listing and seeds the cache. No Autocomplete, no Places key, no Outscraper key in the CLI or v1 JSON. Hub, editor agent (manage_google_reviews), and CLI share the same curation JSON and google_review_cache.

frontpage modules google_reviews
frontpage modules google_reviews <action> [flags] [--site <slug>] [--json]

Bare frontpage modules google_reviews prints this key's CLI usage (exit 2). Not the markup how-to. frontpage modules docs google_reviews stays the agent markup guide. JSON: add --json.

CLI API What it does
connect --place-id <id> or --maps-url <url> POST action=connect Resolve → Places Details → seed (up to 100) → persist connection. Long HTTP timeout (~310s).
resolve --place-id or --maps-url POST action=resolve Places Details only. No seed, no write.
status GET …/modules/google_reviews Listing name, address, rating, cached count, write-a-review URL, curation summary. No review bodies.
list-reviews [--limit 20] [--offset 0] [--stars 4,5] [--hidden] GET …/modules/google_reviews/reviews Paginated cache. Default page 20, max 100. Includes weight and visibility.
hide --id / show --id POST hide_review / show_review Same curation store as the hub. Unknown id → 4xx, no write.
set-stars 4,5 POST set_star_filter Replace the on-site star clicker set. At least one star required.
set-sort newest|highest|lowest POST set_review_sort On-site sort after weights.
set-weight --id --weight 1-1000 POST set_review_weight 1 clears the key. Higher numbers float first.
reset-weights POST reset_review_weights Everyone back to weight 1.
write-review-url field on status Print the platform write-a-review URL. Do not guess a Maps href.
refresh POST action=refresh Same incremental + catch-up as hub “Refresh now.” Long HTTP timeout.
disconnect [--yes] POST action=disconnect Deletes the connection row, not the review cache. --yes when stdin is not a TTY.

Generic docs, request-setup, enable / disable / archive, config --config '{…}'. Do not write placeId or mapsUrl through config. That skips resolve + seed. Use connect. request-setup still puts an amber bar in the editor when the owner does not already have a Place ID or Maps URL.

This CLI will not:

  • Places Autocomplete or any Places / Outscraper key in the client.
  • Invent stars, quotes, or a Maps href.
  • Delete cached review rows (append-only).
  • Replace the editor agent for layout and copy. Markup still goes through files or frontpage prompt.
frontpage modules google_reviews
frontpage modules google_reviews connect --place-id ChIJ…
frontpage modules google_reviews connect --maps-url "https://maps.google.com/…"
frontpage modules google_reviews resolve --place-id ChIJ…
frontpage modules google_reviews status
frontpage modules google_reviews list-reviews --stars 4,5
frontpage modules google_reviews hide --id author:123
frontpage modules google_reviews show --id author:123
frontpage modules google_reviews set-stars 4,5
frontpage modules google_reviews set-sort highest
frontpage modules google_reviews set-weight --id author:123 --weight 100
frontpage modules google_reviews reset-weights
frontpage modules google_reviews write-review-url
frontpage modules google_reviews refresh
frontpage modules google_reviews disconnect --yes

frontpage modules google_reviews docs
frontpage inbox google_reviews

Human connect text: Connected Name. N reviews cached. Write-a-review: … Ask-widget scores stay on frontpage inbox google_reviews.

Markup reminder

<div data-fp-google-reviews data-fp-requires="google_reviews"></div>
<div data-fp-google-reviews data-fp-requires="google_reviews" data-layout="badge"></div>
<div data-fp-google-reviews data-fp-requires="google_reviews" data-layout="link"></div>
<div data-fp-google-ask data-fp-requires="google_reviews" data-mode="modal"></div>

Full markup how-to: frontpage modules docs google_reviews. Owner guide: Google Reviews for your website.

Booking customer names

New Booking customer payloads use firstName (required), lastName (optional) and email (required). Each name part allows 100 characters, with a 200-character combined limit. name is the combined display value. The shared customer picker uses the same fields in Booking and Payments.

Public default controls bind through data-booking-identity="firstName", data-booking-identity="lastName" and data-booking-identity="email". Field templates, labels, layout and soft styles remain fully editable. Booking-type questions keep their own required rules. Required visitor email verification and exact-payload retries are unchanged.