Stay organized with collections
Save and categorize content based on your preferences.
Creates a folder in the resource hierarchy. Returns an Operation which
can be used to track the progress of the folder creation workflow. Upon
success, the Operation.response field will be populated with the
created Folder. In order to succeed, the addition of this new folder
must not violate the folder naming, height, or fanout constraints. + The
folder's display_name must be distinct from all other folders that
share its parent. + The addition of the folder must not cause the active
folder hierarchy to exceed a height of 10. Note, the full active +
deleted folder hierarchy is allowed to reach a height of 20; this
provides additional headroom when moving folders that contain deleted
folders. + The addition of the folder must not cause the total number of
folders under its parent to exceed 300. If the operation fails due to a
folder constraint violation, some errors may be returned by the
CreateFolder request, with status code FAILED_PRECONDITION and an
error description. Other folder constraint violations will be
communicated in the Operation, with the specific PreconditionFailure
returned in the details list in the Operation.error field. The caller
must have resourcemanager.folders.create permission on the identified
parent.
This method waits—the workflow execution is paused—until the operation is
complete, fails, or times out. The default timeout value is 1800 seconds (30
minutes) and can be changed to a maximum value of 31536000 seconds (one year)
for long-running operations using the connector_params field. See the
Connectors reference.
The connector uses polling to monitor the long-running operation, which might
generate additional billable steps. For more information about retries and
long-running operations, refer to Understand connectors.
The polling policy for the long-running operation can be configured. To set the
connector-specific parameters (connector_params), refer to
Invoke a connector call.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Method: googleapis.cloudresourcemanager.v3.folders.create\n\nCreates a folder in the resource hierarchy. Returns an `Operation` which\ncan be used to track the progress of the folder creation workflow. Upon\nsuccess, the `Operation.response` field will be populated with the\ncreated Folder. In order to succeed, the addition of this new folder\nmust not violate the folder naming, height, or fanout constraints. + The\nfolder's `display_name` must be distinct from all other folders that\nshare its parent. + The addition of the folder must not cause the active\nfolder hierarchy to exceed a height of 10. Note, the full active +\ndeleted folder hierarchy is allowed to reach a height of 20; this\nprovides additional headroom when moving folders that contain deleted\nfolders. + The addition of the folder must not cause the total number of\nfolders under its parent to exceed 300. If the operation fails due to a\nfolder constraint violation, some errors may be returned by the\n`CreateFolder` request, with status code `FAILED_PRECONDITION` and an\nerror description. Other folder constraint violations will be\ncommunicated in the `Operation`, with the specific `PreconditionFailure`\nreturned in the details list in the `Operation.error` field. The caller\nmust have `resourcemanager.folders.create` permission on the identified\nparent.\n\nThis method waits---the workflow execution is paused---until the operation is\ncomplete, fails, or times out. The default timeout value is `1800` seconds (30\nminutes) and can be changed to a maximum value of `31536000` seconds (one year)\nfor long-running operations using the `connector_params` field. See the\n[Connectors reference](/workflows/docs/reference/googleapis).\n\nThe connector uses polling to monitor the long-running operation, which might\ngenerate additional billable steps. For more information about retries and\nlong-running operations, refer to [Understand connectors](/workflows/docs/connectors).\n\nThe polling policy for the long-running operation can be configured. To set the\nconnector-specific parameters (`connector_params`), refer to\n[Invoke a connector call](/workflows/docs/reference/googleapis#invoke_a_connector_call).\n\nArguments\n---------\n\nRaised exceptions\n-----------------\n\nResponse\n--------\n\nIf successful, the response contains an instance of [`Operation`](https://cloud.google.com/workflows/docs/reference/googleapis/cloudresourcemanager/v3/Overview#Operation).\n\nSubworkflow snippet\n-------------------\n\nSome fields might be optional or required.\nTo identify required fields, refer to the [API documentation](https://cloud.google.com/resource-manager/reference/rest/v3/folders/create). \n\n### YAML\n\n```yaml\n- create:\n call: googleapis.cloudresourcemanager.v3.folders.create\n args:\n body:\n displayName: ...\n parent: ...\n result: createResult\n```\n\n### JSON\n\n```json\n[\n {\n \"create\": {\n \"call\": \"googleapis.cloudresourcemanager.v3.folders.create\",\n \"args\": {\n \"body\": {\n \"displayName\": \"...\",\n \"parent\": \"...\"\n }\n },\n \"result\": \"createResult\"\n }\n }\n]\n```"]]