Intercom Attachment Archive to SharePoint

Overview

This flow archives Intercom conversation attachments into governed SharePoint storage and keeps an auditable record in Dataverse. It ships Off as a FlowLibs reference implementation - going live requires only authorizing the connections and setting the environment-variable values.

When a new Intercom conversation is created, the flow reads the full conversation over the Intercom REST API, collects every attachment (from the opening message and every reply part), and for each one: downloads the file, files it into a SharePoint library foldered by year / conversation id, logs an audit row to a Dataverse ledger (with a de-dup key so the same file is never archived twice), then writes the SharePoint links back onto the conversation as an internal note and emails a summary to the operations/compliance mailbox.

Why it matters: Customer-supplied files that live only inside Intercom fall outside Microsoft 365 retention, eDiscovery and backup. Mirroring them into SharePoint brings them under governance, with a link back so agents still see them in context.

Use Case

A support / compliance team needs customer attachments retained and discoverable in SharePoint while agents continue to see a link from the Intercom conversation. The Dataverse ledger provides an immutable audit trail - who the customer was, which file, where it landed in SharePoint, the retention label applied, and a correlation id that ties the note, the email and every row together.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Intercom	shared_intercom	TrigNewConversation GetLead
SharePoint	shared_sharepointonline	CreateFile
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Office 365 Outlook	shared_office365

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Catch mid-conversation attachments

TrigNewConversation only fires on creation. To archive files added later, replace the trigger with a Recurrence poll of POST /conversations/search filtered by updated_at > watermark, then run the same per-conversation logic.

File-type filter

Add a Filter array (or Condition) on content_type / extension to skip inline images, signatures, or unwanted types.

Real retention label

SharePoint's connector has no retention op; the flow records the label as metadata. To apply a Microsoft Purview label, add an HTTP call to SharePoint REST SetComplianceTag (or Graph) after Create SharePoint File.

De-dup by content hash

The key is conversation id + file name; switch to a file hash if customers re-send identically named but different files.

DLP / sensitivity scan

Insert a scan step before Create SharePoint File to quarantine sensitive content.

Folder taxonomy

Change the CreateFile folderPath expression to folder by customer, month, or service line.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@coalesce(body('Get_Conversation_Details')?['source']?['attachments'], json('[]'))

@union(variables('varAllAttachments'), coalesce(items('Apply_to_each_Conversation_Part')?['attachments'], json('[]')))

@concat(triggerOutputs()?['body/id'], '|', coalesce(items('Apply_to_each_Attachment')?['name'], items('Apply_to_each_Attachment')?['url'], guid()))

@concat(variables('varFolderRoot'), '/', formatDateTime(utcNow(), 'yyyy'), '/', triggerOutputs()?['body/id'])

@concat('https://app.intercom.com/a/inbox/', variables('varWorkspaceId'), '/inbox/conversation/', triggerOutputs()?['body/id'])

Customize & download