How to dynamically search through custom prompt titles in Fireflies.ai
I'm working with Fireflies.ai’s integration, where the data returned is mostly standardized (e.g., {ID, DATE, Participants, etc.}). The issue arises when a custom prompt is used during a meeting to generate newly formatted transcript summaries. These summaries are stored as:
“Custom App Note 1 Title”
“Custom App Note 1 Prompt”
“Custom App Note 1 Content”
The problem comes up when multiple prompts are run during the same meeting. I end up having to comb through "Custom App Note 1" to "Custom App Note 15" to find the correct one.
Has anyone encountered this issue before? What would be the best method to dynamically search through these to find the correct prompt?
Page 1 / 1
Hey @ckareagain, welcome to the Community!
Sorry to hear you’re running into some trouble with those custom prompts. Could you share a screenshot of how the custom prompt summaries appear, in the selected test record, in the Zap’s trigger? That’ll help us see if they’re coming through as separate fields or line items, so we can determine the best way to extract the data so that the Zap can search through it. Make sure to blur or remove all personal information (names, emails, addresses etc.) from screenshots before sharing - you can use a tool like Zappy for that.
Looking forward to your reply!
Example of Data Response.
This format is the same for additional Custom Apps. These apps are run on Fireflies Dashboard on these meetings, they are sent to Zapier in the order they are run by the user. Custom App Note [#] Title, etc.
Thanks so much for sharing that screenshot showing how the custom prompts are coming through, @ckareagain.
It looks like the information is output into separate fields rather than as line items, so I’m wondering whether you could try mapping all of the potential fields in a AI by Zapier action. That way, all of the information would be in a single place for the AI action to then analyse and extract as necessary.
As the number of prompts could vary and may be over 15, you could try manually selecting the fields. To do that you could try using custom pill mapping to select the fields for prompt 16, 17, 18 etc, which might not be available to select from the current test record.
We have a guide on how to manually select fields that aren’t present in test records here:
Do you think that sort of approach could work? If you do give that a try and run into any issues just let me know!
Thank you for the Idea, I will dig into this and come back with an update.