> 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/jotform/jotform/action-assign-form.md).

# Action: Assign Form

Jotform Operation

<p align="center"><a class="button primary" data-icon="circle-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscriptions</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

<figure><img src="https://2140328495-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXw8pnXlR8JcEKIhl693Q%2Fuploads%2Ftu86E49Dif7BiPLh2dL9%2FJotform_logo_2021.svg.png?alt=media&amp;token=e342f66b-16de-4e09-ac1f-2838ee04eac1" alt="" width="375"><figcaption></figcaption></figure>

<p align="center">The Assign Form action assigns a form to a specific user or team member.</p>

{% embed url="<https://www.youtube.com/watch?v=CyuUuaBSZzA>" %}

#### Example User Story

I want to assign a form to a specific user so that they can manage and edit it.

#### Fields

| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| formID     | String     | Yes      |
| userID     | String     | Yes      |

### Related Connections

[Jotform](/human-connections/jotform/jotform.md)

### Related Automations

Example link

### Code (Apache v2.0): Operation

```
{
  "handle": "assign-form",
  "state": "inDev",
  "meta": {
    "short": "Assign Form",
    "description": "Assign a form to a user in Jotform."
  },
  "input": [
    {
      "name": "formID",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the form to assign."
      }
    },
    {
      "name": "userID",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the user to assign the form to."
      }
    }
  ],
  "output": [
    {
      "name": "success",
      "type": "Boolean",
      "selector": ["success"],
      "meta": {
        "description": "Indicates whether the form was successfully assigned."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "POST",
        "path": "/user/forms/{{formID}}/assign",
        "headers": {
          "Content-Type": "application/json"
        },
        "bodyTemplate": {
          "value": "{\"userID\": \"{{userID}}\"}",
          "placeholders": [
            {
              "name": "formID",
              "type": "String",
              "description": "The ID of the form to assign.",
              "required": true
            },
            {
              "name": "userID",
              "type": "String",
              "description": "The ID of the user to assign the form to.",
              "required": true
            }
          ]
        }
      }
    }
  ]
}

```

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.planetcrust.com/human-connections/jotform/jotform/action-assign-form.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
