Creates a generic form page from an ordered list of fields. Each field becomes the component the form builder makes for its type, so the page edits normally in the dashboard afterwards.

The form must include an email or phone_number field with required: true; that is how a submission is matched to a person. Submissions can then be imported with POST /user_actions using the page id; the answer keys are the field names.

Page names are unique per website (case insensitive). A duplicate name returns 409 with existing_page_id. Without url_slug the slug comes from the name. website_id is required when the scope can use more than one website; each page in GET /pages carries its website_id.

A custom property field is { property, label, required }, where property is the internal_name from GET /custom_user_properties. Its answer saves onto the person. Its type comes from the property, and its options always follow the property. To use a new property, create it first with POST /custom_user_properties.

The API key writes for the admin who created it. That admin must have the pages.manage permission in the page's scope. The Zapier key cannot create pages.