When Fin closes a conversation and generates an AI summary note, that summary is not stored in any accessible conversation attribute. As a result, it cannot be passed into workflows or data connectors natively, even though the summary is visibly present on the conversation record.
The current workaround requires building a custom service that calls GET /conversations/{id}, parses the conversation_parts array, filters for note type entries, and then maps the content back into a custom attribute via a data connector. This is a significant implementation lift for what should be straightforward automation.
The intent seems clear: the AI summary exists, it has value, and customers want to route it to other tools like Slack, CRMs, or internal systems as part of a post-close workflow. Right now there is no supported way to do that without custom engineering.
Request: Expose the Fin AI summary note as a native, referenceable conversation attribute so it can be used directly in workflow steps and data connectors without requiring a custom API integration.
