Label should not be required for `phone` field in API

[vimtor]

Issue Summary

When creating an event type using the v2 API I get the following error:

Validation failed for phone booking field: label must be a string

The problem is that if I set a custom label I lose translation capabilities.

Evidence

I found this issue while setting up an N8N automation.

[linear]

CAL-6867

[FizaSiddique123]

Issue Summary

When creating an event type using the v2 API, the request fails with the following error:

Validation failed for phone booking field: label must be a string

The label field for the phone booking entry appears to be required, but setting a custom label removes the built-in translation capability.
So currently you cannot use the default translatable label through the API.

Steps to Reproduce

Send a request to create/update an event type using the v2 API.

Include a phone booking field without explicitly providing "label".

Execute the request (in my case through an N8N HTTP Request node).

The API returns a validation error.

Example failing snippet:

{
"bookingFields": [
{
"type": "phone",
"required": true
// No "label" provided — expecting default translatable label
}
]
}

Actual Behavior

API returns:

400 Bad Request
Validation failed for phone booking field: label must be a string

The API does not accept the field unless "label" is manually added.

Expected Behavior

"label" should be optional for phone booking fields.

If "label" is not provided, the API should fallback to the default translated label (same behavior as the UI).

This preserves multilingual compatibility.

Context

Using N8N automation to create event types via the v2 Cal.com API.

The UI allows leaving the phone field label blank and still uses the translatable default label.

The API rejects the same configuration.

Suggested Fix

Make "label" optional for type: "phone" in the v2 API schema, or

Automatically fall back to the internal default translated label when "label" is missing.

[CarinaWolli]

@JDP-Neo