You can use placeholders in your script to reference the target asset and the current user.

Asset information

Asset placeholders use the format Document.[API name].

Some of the most common placeholders for the Core fields of a target asset include:

Document.Title
Document.CaptionLong (the Description field)
Document.Copyright
Document.FileCreateDate
Document.FileEditDate
Document.FileImportDate
Document.FileSize
Document.EmbargoDate (the Embargo Date field)
Document.Identifier (the unique ID)
Document.Purpose (the Visibility Class)
Document.IIIFResourceType (the IIIF Resource Type field)
Document.Lockdown (Assets in lockdown cannot be shared, and all existing shares are revoked.)
Document.OriginalFileName
Document.WorkflowStatus
Document.DocSubType (the asset subtype)

Additional asset information placeholders you might find useful include:

Document.TitleWithFallback (the assets title or, if there is none, the asset’s original file name)
Document.Embargo (a boolean value indicating whether the asset is under embargo)
Document.Keywords (the asset’s tags)
Document.RecordID (the asset’s Record ID)
Document.EditDate (the Last Modified date)

User information

Some of the most common placeholders for user information are listed below. These placeholders pull information from the account of the user who triggered the automation.

For example, when a user clicks a button or saves an asset to trigger an automation, the Sender.CoreField.First_Name placeholder pulls in the value of the First name field in the user’s contact record.

Sender.CoreField.First_Name
Sender.CoreField.Last_Name
Sender.CoreField.OrganisationName
Sender.CoreField.Contact_type (the type of account, such as Staff, Source, etc.)
Sender.CoreField.Department
Sender.CoreField.DisplayName
Sender.CoreField.Identifier
Sender.CoreField.LoginID
Sender.CoreField.MustResetPassword
Sender.CoreField.CreateDate
Sender.CoreField.EditDate
Sender.CoreField.EditLocation
Sender.RecordID (the encrypted ID of the user’s account)