Add Config Field
addConfigFieldAdd a Policy question to this automation. Its key is custom_ plus the label in snake_case, with _2, _3 and so on appended when the key is taken, and it is placed at the end of its section. A module template reinstall never changes a field added here.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"automation_id": "<automation_id>",
"label": "<label>",
"question": "<question>",
"type": "<type>"
},
"name": "addConfigField"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | Code for the field, unique within the automation; derived from the label when left out | |
| type | Yes | Value type; compound and sourcePointer are template-only | |
| label | Yes | Short name for the field, shown as its row heading | |
| roles | No | Keys of the process roles whose holders answer this question; empty means anyone | |
| columns | No | Required for table, refused otherwise | |
| example | No | An example answer to the question; left out or null for none | |
| options | No | Required for select and multiSelect, refused otherwise | |
| section | No | Section to add the field to, or null for none | |
| bindings | No | How the value reaches the automation (context, tool) | |
| guidance | No | What to fill in for the question, in plain sentences; left out or null for none | |
| question | Yes | The setup question asked for this field | |
| fill_mode | No | How the field is filled (interview, setup) | interview |
| automation_id | Yes | The automation's unique identifier |