> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/servicenow-app/automation-start-manual/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# automation-start-manual

> Starts an automation given the name of the automation and the trigger, with optional form data.

## Purpose

This automation **starts an automation** given the name of the automation and the trigger, as well as optional form data if desired.

This action makes multiple calls into Itential to get the correct information to start the automation. This includes getting the proper automation and trigger in order to determine the data required to start the automation.

### automation-start-manual

APIs used:

```
/operations-manager/automations
```

```
/operations-manager/triggers
```

```
/operations-manager/triggers/manual/:id/run
```

### Input

| Inputs                | Data Type         | Sample Input                                                  | Description                                                                                                                              |
| --------------------- | ----------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| instance\_name        | Dropdown (String) | SE Lab Prod 2023.1                                            | The Itential Platform instance name                                                                                                      |
| automation\_name      | String            | test\_snow\_actions                                           | Name of the automation                                                                                                                   |
| trigger\_name         | String            | test\_form\_trigger                                           | Name of the manual trigger                                                                                                               |
| form\_data (optional) | JSON              | `{ "formData":{ "OS-Type":"cisco-ios", "severity":"HIGH" } }` | Form data as per the schema being used by the trigger. **Note:** Refer the sample input to structure the JSON object in the same format. |
| token (optional)      | string            | 9f0999c2-7054-4820-8eeb-c3052d30acaa                          | Authentication token or empty if an API key is used                                                                                      |

### Output

| Output               | Data Type | Sample Output                    | Description                                                   |
| -------------------- | --------- | -------------------------------- | ------------------------------------------------------------- |
| automation\_response | JSON      | Sample output as mentioned below | Returns a JSON object with the start status of the automation |
| job\_id              | String    | 4278c701b83943b08a98\*\*\*       | The Job ID of the automation that was started                 |

#### Sample 1 - Output

```json
{
    "taskId": "workflow_start",
    "owner": "Pronghorn",
    "iterations": [],
    "transitions": {
        "success": [
            {
                "task": "6e4c",
                "type": "standard"
            },
            {
                "task": "30e5",
                "type": "standard"
            }
        ]
    }
}
```

#### Sample 2 - Output

```json
{
    "taskId": "workflow_end",
    "owner": "Pronghorn",
    "iterations": [],
    "transitions": {},
    "endTasks": {
        "incomplete": [
            "30e5"
        ],
        "complete": [],
        "error": []
    }
}
```

#### Sample 3 - Output

```json
{
    "taskId": "ec30",
    "owner": "Pronghorn",
    "iterations": [],
    "transitions": {
        "success": [
            {
                "task": "workflow_end",
                "type": "standard"
            }
        ]
    }
}
```

#### Sample 4 - Output

```json
{
    "taskId": "6e4c",
    "owner": "Pronghorn",
    "iterations": [],
    "transitions": {
        "success": [
            {
                "task": "ec30",
                "type": "standard"
            }
        ]
    }
}
```

#### Sample 5 - Output

```json
{
    "taskId": "30e5",
    "owner": "Pronghorn",
    "iterations": [],
    "transitions": {},
    "status": "running",
    "variables": {
        "time": "10",
        "endtime": "20",
        "_id": "8d887c9ad8a54569b3a44849",
        "initiator": "snow-token"
    },
    "metrics": {
        "start_time": 1690904550118,
        "user": "63fc02eed99e7739b84b660e",
        "progress": 0
    }
}
```

### Error Output

| Error Output   | Data Type | Sample Output                                                                                           | Description   |
| -------------- | --------- | ------------------------------------------------------------------------------------------------------- | ------------- |
| error\_message | String    | Method failed: (/operations-manager/automations) with code: 401 - Invalid username/password combination | Error message |

> Starts an automation given the name of the automation and the trigger, with optional form data.