AttachmentStorage Object

Details on how to upload files to the 4me attachment storage facility.

Various rich text fields in 4me can hold attachments. They may contain inline image or video files, and some of them can have attachments listed externally, in which case in the 4me UI these are displayed at the bottom of the text represented with a paperclip in front of each attachment.

Adding attachments and inline image or video files to rich text fields is a three-step process:

  1. Get access to the 4me storage facility (this type provides the necessary details)
  2. Upload the files
  3. Use the keys obtained from the uploads as AttachmentInput.key arguments.

Query to retrieve the required data:

query {
  attachmentStorage {

An upload POST (to uploadUri) must use 'multipart/form-data' encoding according to RFC 2388. The upload must start with a field named Content-Type whose value is the correct content type of the file being uploaded. Subsequently all providerParameters must be supplied and finally a field named file containing the actual (binary) file content must be present.

When the provider is s3 the response to the upload will be XML, the Key element holds the value required to be used in AttachmentInput arguments. It will look something like:

<?xml version="1.0"?>

When the provider is local the response to the upload will be JSON, the key property holds the value required to be used in AttachmentInput arguments. It will look something like:

  "key": "attachments/5/.../helloworld.txt"


The fields in this section list which values can be retrieved when querying AttachmentStorage records.

allowedExtensions ([String!]!)

The permitted file extensions for uploads.

provider (String!)

Type of storage facility in use. One of:

  • local: On-premise environment storage.
  • s3: Cloud environment storage.
providerParameters (JSON!)

The mandatory fields and their values that should be added to an upload POST to the uploadUri.

sizeLimit (Int!)

The maximum size (in bytes) for uploads.

uploadUri (String!)

The URI that attachments should be uploaded to.