Post Attachment

POST

Body

Arguments

numberrequired

stringrequired

filerequired

File content as a base64-encoded string. When the user attached a file in the chat, pass the attachment reference provided by the chat.

stringrequired

Type of record receiving the attachment. Common values: WorkTicket (set objectId to workTicketID, not the ticket number), Opportunity (set objectId to opportunityID), and Receipt (set objectId to receiptID). Use listObjectCodes for the full list of supported values; do not guess the record type.

numberrequired

boolean

Only valid for Opportunity attachments. For any other objectCode, omit this field entirely; Aspire rejects it even when false.

boolean

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Try this request

Request

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/aspire/actions/post-attachment/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "arguments": {
    "attachmentTypeId": "",
    "fileName": "",
    "fileData": "",
    "objectCode": ""
  }
}'

{
  "success": true,
  "data": [
    {
      "response": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.