What you can automate with Archer

Drag any of these 21 actions into a process – no code, no API wrangling.

Create Content Record

Create a content record. The body is Archer's Content wrapper — {'Content': {'LevelId': …, 'FieldContents': {fieldId: {...}}}} — where each field's shape depends on its type.

Delete Content Record

Delete a content record by its ID

Get Application

Get one application by its ID

Get Attachment

Download an attachment by its ID

Get Content by Reference Field

Get the content records referenced by a cross-reference field

Get Content History

Get a content record's history-log entries

Get Content Record

Get one content record by its ID

Get Field Content

Get specific fields of specific content records

Get Group

Get one group by its ID

Get User

Get one user by their ID

List Applications

List all applications in the instance

List Field Definitions (by Application)

List an application's field definitions — the source of the field IDs a write needs

List Field Definitions (by Level)

List a level's field definitions

List Groups

List all groups

List Levels

List all levels (an application's record layouts)

List Levels by Module

List the levels contained by one module

List Users

List users. Narrow with OData $filter/$select/$orderby

List Values-List Values

List the flattened values of a values list (for populating a values-list field)

Login

Re-authenticate and refresh the Archer session token

Post Attachment

Upload an attachment (base64 bytes) and get back the attachment ID to reference on a record

Update Content Record

Update a content record. The body carries Id, LevelId, FieldContents and the record's current Version — a stale Version is rejected.

How the Archer connection works

1. Authenticate

Archer uses username and password (token exchange). Save the connection once and reuse it across every process.

2. Build the process

Drop Archer steps onto the process map alongside desktop, browser, Excel and email steps.

3. Run it attended or unattended

Trigger on a schedule, an email, or a file landing in a folder. Credentials stay encrypted and every run is audited.

Because Archer has an API, Automize talks to it directly in the cloud – no bot needed on a desktop. Where a system has no API, an Automize bot drives its interface instead.

Archer Integration