# OpenText Content Management

> File, find, version and download records in OpenText Content Management (Content Server), set their categories, holds and RM classifications, and start and complete its workflows.

App · 25 actions. Web page: https://docs.lodol.com/docs/integrations/opentext

## Actions

### Add version

Add a new version to a document, such as a corrected or signed copy. The earlier versions are kept.

**Inputs**

- Document ID (`node_id`, text, required): The document's id, a whole number, from a search, a folder listing, a trigger or an earlier step.
- File (`file`, text, required): The file: upload one, pick a file from an earlier step, or paste a public https link to one.
- Version note (`description`, text): What changed in this version.
- Major version (`major_version`, true/false): For a document that keeps major and minor versions, add this one as a major version.

**Outputs**

- `node` (object): The document now
- `node_id` (number): The document
- `version` (object): The new version

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48213,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2105,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 2,
    "volume_id": -2000
  },
  "node_id": 48213,
  "version": {
    "created_at": "2026-10-29T09:12:00Z",
    "description": "Corrected attendance",
    "file_name": "Council minutes 2026-10-20.pdf",
    "file_size": 49002,
    "mime_type": "application/pdf",
    "owner_id": 1000,
    "version_number": 2
  }
}
```

### Apply category

Add a category to a document or folder, with values for its attributes.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Category (`category_id`, text, required): The category to apply.
- Attribute values (`attributes`, object): Values for the category's attributes, one per attribute. Attributes left empty take the category's defaults.

**Outputs**

- `category` (object): The category now
- `changed` (list): The attributes this step set
- `node_id` (number): The item

**Example output**

```json
{
  "category": {
    "attributes": [
      {
        "key": "9830_2",
        "name": "Meeting date",
        "type": "Date",
        "value": "2026-10-20T00:00:00"
      },
      {
        "key": "9830_3",
        "name": "Body",
        "type": "String",
        "value": "City Council"
      }
    ],
    "id": 9830,
    "name": "Meeting record",
    "values": {
      "Body": "City Council",
      "Meeting date": "2026-10-20T00:00:00"
    }
  },
  "changed": [
    "9830_2",
    "9830_3"
  ],
  "node_id": 48213
}
```

### Apply hold

Put a document or folder on a hold, so it can't be changed or destroyed while the hold is in force.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Hold (`hold_id`, text, required): The hold. Pick one, or give its id from an earlier step.

**Outputs**

- `applied` (true/false): Always true once applied
- `hold_id` (number): The hold
- `node_id` (number): The item

**Example output**

```json
{
  "applied": true,
  "hold_id": 3301,
  "node_id": 48213
}
```

### Apply RM classification

Classify a document or folder for records management, which sets its retention schedule, with a record date if you like.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- RM classification (`classification_id`, text, required): The RM classification. Pick one, or give its id.
- Record date (`record_date`, date): The record date. Leave empty for Content Server's default.
- Official record (`official`, true/false): Mark it as an official record.
- Subject (`subject`, text): The record's subject.

**Outputs**

- `classification` (object): Its primary RM classification now
- `classifications` (list): Every RM classification on it
- `classified` (true/false): True when it has an RM classification
- `count` (number): How many
- `node_id` (number): The item

**Example output**

```json
{
  "classification": {
    "classification_id": 7712,
    "essential": "VITAL",
    "file_number": "CLK-100-01",
    "is_primary": true,
    "name": "Minutes - Council",
    "official": true,
    "originator": "City Clerk",
    "record_date": "2026-10-20",
    "records_officer": "Records Officer",
    "rsi": "PERM-01",
    "status": "ACTIVE",
    "status_date": "2026-10-28",
    "subject": "Regular meeting"
  },
  "classifications": [
    {
      "classification_id": 7712,
      "essential": "VITAL",
      "file_number": "CLK-100-01",
      "is_primary": true,
      "name": "Minutes - Council",
      "official": true,
      "originator": "City Clerk",
      "record_date": "2026-10-20",
      "records_officer": "Records Officer",
      "rsi": "PERM-01",
      "status": "ACTIVE",
      "status_date": "2026-10-28",
      "subject": "Regular meeting"
    }
  ],
  "classified": true,
  "count": 1,
  "node_id": 48213
}
```

### Complete assignment

Finish a workflow step with one of its choices, such as Approve, and a comment. The workflow moves on in Content Server.

**Inputs**

- Workflow ID (`process_id`, text, required): The assignment's 'process_id', from 'List my assignments' or the trigger.
- Sub-workflow ID (`subprocess_id`, text, required): The assignment's 'subprocess_id', from 'List my assignments' or the trigger.
- Step ID (`task_id`, text, required): The assignment's 'task_id', from 'List my assignments' or the trigger.
- Choice (`decision`, text, required): The choice as it appears on the step, such as Approve or Send On. 'Get assignment' lists them.
- Comment (`comment`, text): A comment to add to the step.

**Outputs**

- `decision` (text): The choice made
- `decision_key` (text): Content Server's key for it
- `done` (true/false): Always true once done
- `process_id` (number): The workflow
- `subprocess_id` (number): The sub-workflow
- `task_id` (number): The step

**Example output**

```json
{
  "decision": "Approve",
  "decision_key": "1",
  "done": true,
  "process_id": 63018,
  "subprocess_id": 63018,
  "task_id": 2
}
```

### Copy item

Copy a document or folder into another folder.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- To folder (`parent_id`, text, required): The folder to copy it into. Pick one, or give its id.
- New name (`name`, text): A name for the copy. Defaults to the original's name.

**Outputs**

- `copied_from` (number): The original's id
- `node` (object): The copy
- `node_id` (number): The copy's id

**Example output**

```json
{
  "copied_from": 48213,
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48250,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2105,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 1,
    "volume_id": -2000
  },
  "node_id": 48250
}
```

### Create folder

Create a folder inside another folder.

**Inputs**

- Folder (`parent_id`, text, required): The folder to add it to. Pick one, or give its id from an earlier step.
- Name (`name`, text, required): The new folder's name. It can't contain a colon (:).
- Description (`description`, text): A description to show with it in Content Server.

**Outputs**

- `node` (object): The new folder
- `node_id` (number): The new folder's id

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "",
    "id": 2105,
    "is_container": true,
    "is_document": false,
    "item_count": 12,
    "mime_type": "",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes",
    "parent_id": 2000,
    "reserved": false,
    "size": 0,
    "type": 0,
    "type_name": "Folder",
    "version_number": 0,
    "volume_id": -2000
  },
  "node_id": 2105
}
```

### Delete item

Delete a document or folder (with everything in it). Content Server keeps it in its Recycle Bin for a while, if the agency has one.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `node_id` (number): The item deleted

**Example output**

```json
{
  "deleted": true,
  "node_id": 48213
}
```

### Download document

Download a document's file, its latest version or an earlier one, for a later step to attach or send.

**Inputs**

- Document ID (`node_id`, text, required): The document's id, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Version (`version_number`, number): An earlier version's number. Leave empty for the latest. At least 1.

**Outputs**

- `content_type` (text): The file's type, such as application/pdf
- `document_ref` (text): The downloaded file, for later steps
- `filename` (text): The file's name
- `node_id` (number): The document downloaded
- `size_bytes` (number): The file's size in bytes
- `url` (text): Where to open the downloaded file
- `version_number` (number): The version downloaded, 0 for the latest

**Example output**

```json
{
  "content_type": "application/pdf",
  "document_ref": "doc_0123456789abcdef0123456789abcdef",
  "filename": "Council minutes 2026-10-20.pdf",
  "node_id": 48213,
  "size_bytes": 48213,
  "url": "/actions/core/serve-document/doc_0123456789abcdef0123456789abcdef",
  "version_number": 0
}
```

### Get assignment

Get one workflow step with its instructions and the choices it offers, such as Approve or Send On.

**Inputs**

- Workflow ID (`process_id`, text, required): The assignment's 'process_id', from 'List my assignments' or the trigger.
- Sub-workflow ID (`subprocess_id`, text, required): The assignment's 'subprocess_id', from 'List my assignments' or the trigger.
- Step ID (`task_id`, text, required): The assignment's 'task_id', from 'List my assignments' or the trigger.

**Outputs**

- `actions` (list): The standard buttons
- `comments_on` (true/false): True when the step takes a comment
- `decisions` (list): The step's own choices, such as Approve
- `instructions` (text): The step's instructions
- `must_accept` (true/false): True when the step must be accepted before it is done
- `priority` (number): The step's priority
- `process_id` (number): The workflow
- `subprocess_id` (number): The sub-workflow
- `task_id` (number): The step
- `title` (text): The workflow's title

**Example output**

```json
{
  "actions": [
    {
      "key": "SendOn",
      "label": "Send On"
    }
  ],
  "comments_on": true,
  "decisions": [
    {
      "key": "1",
      "label": "Approve"
    },
    {
      "key": "2",
      "label": "Send back"
    }
  ],
  "instructions": "Approve or send back with a comment",
  "must_accept": false,
  "priority": 50,
  "process_id": 63018,
  "subprocess_id": 63018,
  "task_id": 2,
  "title": "Minutes review 2026-10-20"
}
```

### Get categories

Get the categories on a document or folder, with each attribute's value.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.

**Outputs**

- `categories` (list): Its categories
- `count` (number): How many categories
- `node_id` (number): The item

**Example output**

```json
{
  "categories": [
    {
      "attributes": [
        {
          "key": "9830_2",
          "name": "Meeting date",
          "type": "Date",
          "value": "2026-10-20T00:00:00"
        },
        {
          "key": "9830_3",
          "name": "Body",
          "type": "String",
          "value": "City Council"
        }
      ],
      "id": 9830,
      "name": "Meeting record",
      "values": {
        "Body": "City Council",
        "Meeting date": "2026-10-20T00:00:00"
      }
    }
  ],
  "count": 1,
  "node_id": 48213
}
```

### Get holds on item

Get the holds on a document or folder, whether put on it or on a folder it is in, with who applied each and when.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.

**Outputs**

- `count` (number): How many
- `holds` (list): Its holds
- `node_id` (number): The item
- `on_hold` (true/false): True when an active hold applies

**Example output**

```json
{
  "count": 1,
  "holds": [
    {
      "active": true,
      "applied_at": "2026-10-30T10:00:00Z",
      "applied_by": "Records Officer",
      "applied_how": "Direct",
      "comment": "Preserve all minutes",
      "hold_id": 3301,
      "item_id": 48213,
      "name": "Smith v. City (2026)",
      "removable": true,
      "type": "Legal"
    }
  ],
  "node_id": 48213,
  "on_hold": true
}
```

### Get item

Get a document's or folder's details: its name, folder, type, size, latest version and when it changed.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.

**Outputs**

- `node` (object): The item

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48213,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2105,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 1,
    "volume_id": -2000
  }
}
```

### Get records details

Get a document's or folder's RM classification, with its retention schedule (RSI), status and record date.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.

**Outputs**

- `classification` (object): Its primary RM classification
- `classifications` (list): Every RM classification on it
- `classified` (true/false): True when it has an RM classification
- `count` (number): How many
- `node_id` (number): The item

**Example output**

```json
{
  "classification": {
    "classification_id": 7712,
    "essential": "VITAL",
    "file_number": "CLK-100-01",
    "is_primary": true,
    "name": "Minutes - Council",
    "official": true,
    "originator": "City Clerk",
    "record_date": "2026-10-20",
    "records_officer": "Records Officer",
    "rsi": "PERM-01",
    "status": "ACTIVE",
    "status_date": "2026-10-28",
    "subject": "Regular meeting"
  },
  "classifications": [
    {
      "classification_id": 7712,
      "essential": "VITAL",
      "file_number": "CLK-100-01",
      "is_primary": true,
      "name": "Minutes - Council",
      "official": true,
      "originator": "City Clerk",
      "record_date": "2026-10-20",
      "records_officer": "Records Officer",
      "rsi": "PERM-01",
      "status": "ACTIVE",
      "status_date": "2026-10-28",
      "subject": "Regular meeting"
    }
  ],
  "classified": true,
  "count": 1,
  "node_id": 48213
}
```

### List folder items

List the documents and folders in a folder, one page at a time, with their ids.

**Inputs**

- Folder (`folder_id`, text): The folder to list. Pick one, or give its id from an earlier step. Leave empty for your Personal Workspace.
- Show (`item_kind`, text): Everything (the default), documents only, or folders only. One of: `all` (Everything (default)), `documents` (Documents only), `folders` (Folders and other containers only).
- Name contains (`name_contains`, text): Only items whose name contains this text.
- Order (`sort`, text): By name (the default), or most recently changed or added first. One of: `asc_name` (Name, A to Z (default)), `desc_name` (Name, Z to A), `desc_modify_date` (Most recently changed first), `desc_create_date` (Most recently added first).
- How many (`count`, number): How many to return, 1 to 500. Defaults to 100. From 1 to 500.
- Page (`page`, number): Which page, for more: 1 (the default), 2 and so on. At least 1.

**Outputs**

- `count` (number): How many items this page holds
- `folder_id` (number): The folder listed
- `has_more` (true/false): True when there is another page
- `items` (list): The items
- `page` (number): This page's number
- `total` (number): How many there are in all

**Example output**

```json
{
  "count": 2,
  "folder_id": 2000,
  "has_more": false,
  "items": [
    {
      "created_at": "2026-10-28T14:05:00Z",
      "description": "",
      "id": 2105,
      "is_container": true,
      "is_document": false,
      "item_count": 12,
      "mime_type": "",
      "modified_at": "2026-10-28T14:05:00Z",
      "name": "Council minutes",
      "parent_id": 2000,
      "reserved": false,
      "size": 0,
      "type": 0,
      "type_name": "Folder",
      "version_number": 0,
      "volume_id": -2000
    },
    {
      "created_at": "2026-10-28T14:05:00Z",
      "description": "Approved minutes of the regular meeting",
      "id": 48213,
      "is_container": false,
      "is_document": true,
      "item_count": 0,
      "mime_type": "application/pdf",
      "modified_at": "2026-10-28T14:05:00Z",
      "name": "Council minutes 2026-10-20.pdf",
      "parent_id": 2105,
      "reserved": false,
      "size": 48213,
      "type": 144,
      "type_name": "Document",
      "version_number": 1,
      "volume_id": -2000
    }
  ],
  "page": 1,
  "total": 2
}
```

### List holds

List the agency's legal and records holds.

**Inputs**

- Active only (`active_only`, true/false): Only holds in force (the default). Turn off for every hold.

**Outputs**

- `count` (number): How many
- `holds` (list): The holds

**Example output**

```json
{
  "count": 1,
  "holds": [
    {
      "active": true,
      "id": 3301,
      "name": "Smith v. City (2026)"
    }
  ]
}
```

### List my assignments

List the connected user's assignments, such as workflow steps waiting on them, with when each is due.

**Inputs**

- Workflow steps only (`workflow_only`, true/false): Leave out assignments that aren't workflow steps.

**Outputs**

- `assignments` (list): The assignments
- `count` (number): How many

**Example output**

```json
{
  "assignments": [
    {
      "description": "Check the draft minutes before publishing",
      "due_date": "2026-11-04T17:00:00Z",
      "from_user_id": 1000,
      "id": 63021,
      "instructions": "Approve or send back with a comment",
      "location_id": 48213,
      "name": "Review minutes",
      "priority": "Medium",
      "process_id": 63018,
      "status": "Ok",
      "subprocess_id": 63018,
      "task_id": 2,
      "type": 153,
      "type_name": "Workflow step"
    }
  ],
  "count": 1
}
```

### List versions

List a document's versions, newest first, with their files.

**Inputs**

- Document ID (`node_id`, text, required): The document's id, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Order (`order`, text): Newest first (the default) or oldest first. One of: `desc` (Newest first (default)), `asc` (Oldest first).
- How many (`count`, number): How many to return, 1 to 500. Defaults to 100. From 1 to 500.

**Outputs**

- `count` (number): How many
- `node_id` (number): The document
- `versions` (list): Its versions

**Example output**

```json
{
  "count": 2,
  "node_id": 48213,
  "versions": [
    {
      "created_at": "2026-10-29T09:12:00Z",
      "description": "Corrected attendance",
      "file_name": "Council minutes 2026-10-20.pdf",
      "file_size": 49002,
      "mime_type": "application/pdf",
      "owner_id": 1000,
      "version_number": 2
    },
    {
      "created_at": "2026-10-28T14:05:00Z",
      "description": "",
      "file_name": "Council minutes 2026-10-20.pdf",
      "file_size": 48213,
      "mime_type": "application/pdf",
      "owner_id": 1000,
      "version_number": 1
    }
  ]
}
```

### Move item

Move a document or folder into another folder.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- To folder (`parent_id`, text, required): The folder to move it into. Pick one, or give its id.

**Outputs**

- `node` (object): The item, moved
- `node_id` (number): The item moved
- `parent_id` (number): The folder it is in now

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48213,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2106,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 1,
    "volume_id": -2000
  },
  "node_id": 48213,
  "parent_id": 2106
}
```

### Remove hold

Take a hold off a document or folder it was put on.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Hold (`hold_id`, text, required): The hold. Pick one, or give its id from an earlier step.

**Outputs**

- `hold_id` (number): The hold
- `node_id` (number): The item
- `removed` (true/false): Always true once removed

**Example output**

```json
{
  "hold_id": 3301,
  "node_id": 48213,
  "removed": true
}
```

### Rename item

Change a document's or folder's name or description.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- New name (`name`, text): The new name. It can't contain a colon (:).
- New description (`description`, text): A new description. Leave empty to keep the current one.

**Outputs**

- `node` (object): The item now
- `node_id` (number): The item renamed

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48213,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2105,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 1,
    "volume_id": -2000
  },
  "node_id": 48213
}
```

### Search

Find documents and folders by the words in their names, details or text. Returns one page; ask for the next page for more.

**Inputs**

- Words (`text`, text): The words to look for, such as council minutes.
- Match (`match`, text): All the words (the default), any of them, or the exact phrase. One of: `allwords` (All the words (default)), `anywords` (Any of the words), `exactphrase` (The exact phrase).
- Find (`item_kind`, text): Everything (the default), documents only, or folders only. One of: `all` (Everything (default)), `documents` (Documents only), `folders` (Folders only).
- Look in (`within`, text): Names, details and text (the default), the text only, or names and details only. One of: `all` (Names, details and text (default)), `content` (The documents' text only), `metadata` (Names and details only).
- Advanced query (`query`, text): A query in Content Server's search language, such as OTName:minutes, for what the words can't say. Combined with the words when both are given.
- Order (`sort`, text): Best match first (the default), newest first, or oldest first. One of: `relevance` (Best match first (default)), `desc_OTObjectDate` (Newest first), `asc_OTObjectDate` (Oldest first).
- How many (`count`, number): How many to return, 1 to 500. Defaults to 50. From 1 to 500.
- Page (`page`, number): Which page, for more: 1 (the default), 2 and so on. At least 1.

**Outputs**

- `count` (number): How many items this page holds
- `has_more` (true/false): True when there is another page
- `items` (list): The items
- `page` (number): This page's number
- `query` (text): The search Content Server ran
- `total` (number): How many there are in all

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "items": [
    {
      "created_at": "2026-10-28T14:05:00Z",
      "description": "Approved minutes of the regular meeting",
      "id": 48213,
      "is_container": false,
      "is_document": true,
      "item_count": 0,
      "mime_type": "application/pdf",
      "modified_at": "2026-10-28T14:05:00Z",
      "name": "Council minutes 2026-10-20.pdf",
      "parent_id": 2105,
      "reserved": false,
      "size": 48213,
      "type": 144,
      "type_name": "Document",
      "version_number": 1,
      "volume_id": -2000
    }
  ],
  "page": 1,
  "query": "(council and minutes) and OTSubType:144",
  "total": 1
}
```

### Start workflow

Start a Content Server workflow from its map, with documents attached. Its first steps go to the people the map names.

**Inputs**

- Workflow map (`workflow_map_id`, text, required): The workflow map to start. Pick one, or give its id.
- Documents to attach (`attachment_ids`, text): The ids of documents to attach, separated by commas, or a list from an earlier step.
- Title (`title`, text): A title for this workflow. Defaults to the map's.
- Due date (`due_date`, date): When the whole workflow is due (the end of that day).
- Comment (`comment`, text): A comment to start it with.

**Outputs**

- `attachment_ids` (list): The documents attached
- `draft_process_id` (number): The draft it was started from
- `message` (text): Content Server's message, if any
- `process_id` (number): The running workflow's id
- `started` (true/false): Always true once started
- `workflow_map_id` (number): The map it was started from

**Example output**

```json
{
  "attachment_ids": [
    48213
  ],
  "draft_process_id": 63010,
  "message": "",
  "process_id": 63018,
  "started": true,
  "workflow_map_id": 51200
}
```

### Update attribute values

Change attribute values of a category already on a document or folder. Only the attributes given change.

**Inputs**

- Item ID (`node_id`, text, required): The id of the document or folder, a whole number, from a search, a folder listing, a trigger or an earlier step.
- Category (`category_id`, text, required): The category whose values to change.
- Attribute values (`attributes`, object, required): The new values, one per attribute. Attributes left empty keep their values.

**Outputs**

- `category` (object): The category now
- `changed` (list): The attributes this step changed
- `node_id` (number): The item

**Example output**

```json
{
  "category": {
    "attributes": [
      {
        "key": "9830_2",
        "name": "Meeting date",
        "type": "Date",
        "value": "2026-10-20T00:00:00"
      },
      {
        "key": "9830_3",
        "name": "Body",
        "type": "String",
        "value": "City Council"
      }
    ],
    "id": 9830,
    "name": "Meeting record",
    "values": {
      "Body": "City Council",
      "Meeting date": "2026-10-20T00:00:00"
    }
  },
  "changed": [
    "9830_3"
  ],
  "node_id": 48213
}
```

### Upload document

Add a file to a folder as a new document, with a category's values if you like.

**Inputs**

- Folder (`parent_id`, text, required): The folder to add it to. Pick one, or give its id from an earlier step.
- File (`file`, text, required): The file: upload one, pick a file from an earlier step, or paste a public https link to one.
- Name (`name`, text): The document's name. Defaults to the file's name.
- Description (`description`, text): A description to show with it in Content Server.
- Category (`category_id`, text): A category to apply to the new document, such as a records category your office uses.
- Attribute values (`attributes`, object): Values for the category's attributes, one per attribute. Attributes left empty take the category's defaults.

**Outputs**

- `node` (object): The new document
- `node_id` (number): The new document's id

**Example output**

```json
{
  "node": {
    "created_at": "2026-10-28T14:05:00Z",
    "description": "Approved minutes of the regular meeting",
    "id": 48213,
    "is_container": false,
    "is_document": true,
    "item_count": 0,
    "mime_type": "application/pdf",
    "modified_at": "2026-10-28T14:05:00Z",
    "name": "Council minutes 2026-10-20.pdf",
    "parent_id": 2105,
    "reserved": false,
    "size": 48213,
    "type": 144,
    "type_name": "Document",
    "version_number": 1,
    "volume_id": -2000
  },
  "node_id": 48213
}
```
