> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.moveworks.com/_mcp/server.

# Forms Integration - ManageEngine

# Overview

ManageEngine forms and request templates are incredibly powerful when combined with Moveworks’ Smart Forms. You can use them together to:

* Enable powerful automations, by leveraging [ManageEngine ServiceDesk Automation](https://www.manageengine.com/products/service-desk/automation/).
* Trigger custom approval workflows.
* Structure inputs from your employees.

# Permission Required

Moveworks will use the existing service account created in ManageEngine for fetching the forms from your instance.

# Form Ingestion

Forms are referred to as `request_templates` under the Service Catalog in ManageEngine. Moveworks will ingest all request templates that are available in the Service Catalog.

### Form Finding

To fetch all the request templates, we use the following API:
`GET https://{manageengine_url}/api/v3/request_templates`

To fetch additional details about a single request template, we use the following API:
`GET https://{manageengine_url}/api/v3/request_templates/{request_template_id}`

### Form Filling

To create a request using the form fields of a request template, we use the following API:
`POST https://{manageengine_url}/api/v3/requests` , with the following body:

```json
Body: x-www-form-urlencoded
input_data: {
              "request": {
                "template": {
                  "id": "{template_id}"
                },
                "requester": {
                  "id": "{requester_id}"
                }
                "request_template_task_ids": [],
                "subcategory": null,
                "item": null,
                "subject": "{subject_string}",
                "description": "{description_string}",
                "email_ids_to_notify": [],
                "created_time": {created_time},
                "due_by_time": {due_by_time},
                "attachments": []
              }
            }
```

## Architecture

![](https://files.readme.io/ff91934-Untitled_-_2023-10-26T153600.798.png)

# Supported Field Types

| Integration  | External Field Types | Moveworks Type   |
| ------------ | -------------------- | ---------------- |
| ManageEngine | string               | Text: Multi-line |
| ManageEngine | html                 | HTML             |
| ManageEngine | lookup               | Dropdown: Single |
| ManageEngine | boolean              | BINARY           |
| ManageEngine | int                  | Text: Numerical  |
| ManageEngine | long                 | Text: Numerical  |
| ManageEngine | double               | Text: Numerical  |
| ManageEngine | datetime             | Datetime         |
| ManageEngine | udf                  | Unsupported      |
| ManageEngine | unknown              | Unsupported      |
| ManageEngine | group                | Unsupported      |

# FAQ

### Q: Does Moveworks support request templates that contain mandatory attachments?

**A**: No, not at the moment.

### Q: Does Moveworks support request templates with no fields present in them other than the `requester` field?

**A**: No, not at the moment.

### Q: Does Moveworks support request templates with fields that are present in the template but containing no metadata?

**A**: No, not at the moment.

### Q: We are changing the menu templates and moveworks may need to look up and present options to end users a different way once we update the templates. What issues would happen if our organization changes the template menus in Manage Engine.

**A:** Request templates are forms from Manage Engine, with Moveworks form ingestion any changes will be automatically ingested