Source Field Exposed in Magic Skills Data
J
Janine Bezuidenhout
The partner is requesting that the "source" field be surfaced and made available within the Magic Skills execution environment so it can be used as part of skill logic. Currently, message data returned within Skills only includes fields such as author, type, internal, text, created, and author_email. The source field is not present in the API response, which prevents skills from detecting the ticket/message source (e.g., source="chat") and acting on it. The skill logic itself is correct in principle, but cannot function as intended without this field being exposed.
Autopilot
Merged in a post:
Allow Supermagic to read the source field
D
Danielle Vickstrom
I'm trying to create a skill that is looking for only thread voice attendant calls so that it can do QA on the voice transcription and ticket notes as a whole after the ticket is closed. However the Super Magic agent is telling me that it does not have access to see the ticket source. This causes the Supermagic to have to look at an excess amount of tickets and read them before determining whether there's a voice AI transcription on them.