Allow forwarding or reusing existing conversation attachments without manual download/upload

Hi ​@Felix Herwagen ! This is indeed an uncomfortable limitation, but there are several workarounds depending on the use case. Could you share what you’d specifically wish to achieve, for example, with moving attachments to external platforms? And which platforms did you refer to?

Hi ​@Aleksei O ,

I am sharing Intercom-Convo-Links to Linear AI:
If I give Linear an Intercom conversation, it mainly reads the conversation text, but it cannot directly use the screenshots that were attached in Intercom.
That means I have to manually add the screenshots again or describe their contents by hand, even though they already contain important context.

My main request would be for Linear AI to also receive and interpret Intercom attachments, especially screenshots, as part of the original conversation context.

​@Felix Herwagen Got it! I built a similar integration for Notion recently, and I think it could work for Linear as well. When a card in Notion with an Intercom conversation ID is created, it triggers a webhook in Make, which then downloads all Intercom attachments to Notion (and converts 24-hour Intercom image URLs to Notion attachments) and then appends them to the body of the page. 

For Linear, a Make scenario could look like something like this (I used Claude for the instructions based on my other setup, so it requires testing, of course): 

  1. Linear › Watch Issue Created (Webhook in Make)
  2. Tools › Set variable — extract the Intercom conversation ID from the issue text (regex on {{1.description}}). Output: conversationId.
  3. Intercom › Make an API Call — GET /conversations/{{2.conversationId}} → returns attachments[].
  4. Iterator — array: {{3.conversation_parts.conversation_parts[].attachments[]}}.
  5. HTTP › Get a file — URL: {{4.url}}.
  6. Linear › Execute a GraphQL Query — fileUpload:
  mutation($contentType:String!,$filename:String!,$size:Int!){
    fileUpload(contentType:$contentType,filename:$filename,size:$size){
      uploadFile{ assetUrl uploadUrl headers{ key value } }
    } 
  } 
  Variables: { "contentType":"{{4.content_type}}", "filename":"{{4.name}}", "size":{{4.filesize}} }

  7. HTTP › Make a request — PUT to {{6.data.fileUpload.uploadFile.uploadUrl}}; headers: Content-Type = {{4.content_type}} + any headers[] from step 6; body = binary {{5.data}}.
  8. Array aggregator (source = Iterator) — build markdown per file:
  
  9. Linear › Create a Comment — issue ID {{1.id}}, body = aggregated markdown from step 8.

For some reason, it appears that attachments can be added only as comments… 

Lmk, if you wanna chat about this!