> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/human-connections/docusign/docusign/action-create-workspace.md).
# Action: Create Workspace
The Create Workspace action sets up a new shared folder in DocuSign for organizing and collaborating on documents.
{% embed url="" %}
#### Example User Story
I want to create a dedicated DocuSign workspace for each new project, so my team can securely store and manage all related contracts in one place.
#### Fields
| Field Name | Field Type | Required |
| ----------- | ---------- | -------- |
| name | String | Yes |
| description | String | No |
| billable | Boolean | No |
### Related Connections
[Docusign](/human-connections/docusign/docusign.md)
### Related Automations
Example link
### Code (Apache v2.0): Operation
```
{
"handle": "create-workspace",
"state": "inDev",
"meta": {
"short": "Create Workspace",
"description": "Creates a new workspace in Docusign."
},
"input": [
{
"name": "name",
"type": "String",
"required": true,
"meta": {
"description": "The name of the workspace."
}
},
{
"name": "description",
"type": "String",
"required": false,
"meta": {
"description": "The description of the workspace."
}
},
{
"name": "billable",
"type": "Boolean",
"required": false,
"meta": {
"description": "Whether the workspace is billable."
}
}
],
"output": [
{
"name": "workspaceId",
"type": "String",
"selector": ["workspaceId"],
"meta": {
"description": "The ID of the created workspace."
}
},
{
"name": "name",
"type": "String",
"selector": ["name"],
"meta": {
"description": "The name of the created workspace."
}
},
{
"name": "description",
"type": "String",
"selector": ["description"],
"meta": {
"description": "The description of the created workspace."
}
},
{
"name": "billable",
"type": "Boolean",
"selector": ["billable"],
"meta": {
"description": "Whether the created workspace is billable."
}
}
],
"steps": [
{
"type": "http",
"http": {
"method": "POST",
"path": "/v2.1/workspaces",
"headers": {
"Content-Type": "application/json"
},
"bodyTemplate": {
"value": "{\"name\": \"{{name}}\", \"description\": \"{{description}}\", \"billable\": {{billable}}}",
"placeholders": [
{
"name": "name",
"type": "String",
"description": "The name of the workspace.",
"required": true
},
{
"name": "description",
"type": "String",
"description": "The description of the workspace.",
"required": false
},
{
"name": "billable",
"type": "Boolean",
"description": "Whether the workspace is billable.",
"required": false
}
]
}
}
}
]
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.planetcrust.com/human-connections/docusign/docusign/action-create-workspace.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.