Choose a form or calendar on a page

In the website editor, use Change form or Change calendar on an embedded resource. Choose another resource from the same site in the picker. Each placement is saved independently as a new draft revision; publish separately to make it live. Draft resources can be selected, but must be activated before publishing. Archived resources are excluded. This change does not require AI credits.

Reusable contact fields

Create a field from the Contact field selector without leaving your form/calendar editor, or open your project’s Contact fields page, or choose a project in CRM → Contact fields, to create, rename, archive and restore project fields. Creating a field preserves your unsaved setup and selects the mapping; save the resource separately.

Workspace-wide agents can call list_project_contact_fields and manage_project_contact_fields for a project. Site-bound agents retain list_contact_fields and manage_contact_fields for their permitted child. Then map questions with field:<UUID>. Question and field types must match; use the field’s choices for choice questions. Calendars accept optional questions and collect name/email automatically. Forms need a question mapped to Email to attach custom values to a contact. Contact values appear on contact details and CSV exports.

Read private values with get_contact_fields (contacts.read); update them with save_contact_fields (contacts.write), where null clears a value and CRM plan eligibility applies. Field management requires contacts.write and workspace owner/admin or explicit project admin access. Existing field IDs remain valid aliases for their project copies during migration. Archived fields preserve existing mappings/values; types and choices remain fixed. Refresh cached MCP tools to discover these operations.

Managed conversion resources

Website generation can add managed enquiry forms and booking calendars. Resource bindings in the built revision identify the forms and calendars it embeds. Configure availability, delivery settings and resource status in the website dashboard or through list_resources, create_resource, save_resource and the webhook tools.

Review before going live

A revision with an inactive or missing embedded resource cannot be published. Review and activate the resources in Dashboard → Forms / Calendars, then retry publishing. The public agent API currently supports website operations; it does not expose form answers, booking attendee data, or resource administration.