Hi, dear community. From yestarday evening I’m experiencing “Unknown runtime error” in Fireflies.ai
Very weird. Anyone else?
1 Like
Hello @kaidano 
Thank you for bringing this to the Community.
This issue has been reported to the Dev team and is being checked. Once I have further updates on this, I’ll let you know!
Meanwhile, we suggest you use the “Execute a Graphql query” module for your use case.
You can also submit a ticket to get further assistance. 
Thank you for your patience and understanding.
Hey, same error for me and three customers since yesterday.
It doesn’t work with “Execute a GraphQL query” either.
Please handle this quickly, Make.com — I already sent a ticket to support.
Hey Misha, any updates on this?
Hello @Jon_B
Unfortunately, not at the moment. I will let you know of an update as soon as possible. 
Not fixed yet … @Misha , please keep us informed, clients loose their info
Hey guys, I’m also experiencing the fireflies error, but I’ve found a workaround during the HTTP request
To get a transcript
HTTP Module Method POST
URL : `https://api.fireflies.ai/graphql`
Headers : Authorization
Value : Bearer YOUR_API_KEY
Headers: Content-Type
Value : application/json
Then the JSON Body
{
"query": "query Transcript($transcriptId: String!) { transcript(id: $transcriptId) { id title transcript_url audio_url sentences { raw_text speaker_name } summary { keywords action_items } }}",
"variables": {
"transcriptId": "**MAP YOUR MEETING ID**"
}
}
PS
I hope this makes sense and helps 
3 Likes
I need to get all transcripts from the day. I managed it like this for now:
3 Module is an HTTP + Request Content:
{
“query”: “query GetFullTranscript($transcriptId: String!) {\n transcript(id: $transcriptId) {\n id\n title\n dateString\n privacy\n duration\n calendar_id\n cal_id\n calendar_type\n transcript_url\n audio_url\n video_url\n meeting_link\n date\n host_email\n organizer_email\n user {\n user_id\n email\n name\n num_transcripts\n recent_meeting\n minutes_consumed\n is_admin\n integrations\n }\n meeting_info {\n fred_joined\n silent_meeting\n summary_status\n }\n speakers {\n id\n name\n }\n meeting_attendees {\n displayName\n email\n phoneNumber\n name\n location\n }\n fireflies_users\n participants\n sentences {\n index\n speaker_name\n speaker_id\n text\n raw_text\n start_time\n end_time\n ai_filters {\n task\n pricing\n metric\n question\n date_and_time\n text_cleanup\n sentiment\n }\n }\n summary {\n keywords\n action_items\n outline\n shorthand_bullet\n overview\n bullet_gist\n gist\n short_summary\n short_overview\n meeting_type\n topics_discussed\n transcript_chapters\n }\n apps_preview {\n outputs {\n transcript_id\n user_id\n app_id\n created_at\n title\n prompt\n response\n }\n }\n }\n}”,
“variables”: {
“transcriptId”: “ITERATOR ID TRANSCRIPT”
}
}
1 Like
Thank you for this.
It was more annoying to remap everything in the iterator and everything else in the chain I had. I originally had a chain with a router that goes to 6 different paths. I had to delete all of them because the Fireflies module broke. But at least this works!
If anyone uses timestamps like I do, here is the request that you need. It is pretty simple to figure out once you look at the API docs from Fireflies.
{
"query": "query Transcript($transcriptId: String!) { transcript(id: $transcriptId) { id title transcript_url audio_url sentences { text index raw_text start_time end_time speaker_id speaker_name } summary { keywords action_items } }}",
"variables": {
"transcriptId": "**MAP YOUR MEETING ID**"
}
}
1 Like
Hi there!
I’m trying to connect my Fireflies to the scenario in using Fireflies API, but there is an error with my user ID (“Failed to load data”).
I’ve connected to Fireflies’ support and they noticed that the issue is coming from Make.com’s end.
I want to know is this problem serious and when they’re going to fix it?
And maybe there’s a way to get around this error.
Maybe someone has encountered this?
1 Like
Welcome to the Make community!
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. Make support has access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing potentially sensitive information about your account, scenario variables, and output bundles might not be advisable as it is a public forum.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free Make account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues. P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
— @samliew
Hello Makers
Thank you to everyone who came by and shared a workaround! We really appreciate your support.
Our Dev team is aware of the issue and confirmed that they know what’s going on and are working on the fix.
I’ll keep you posted.
3 Likes
Hello @JBJ
Happy to share that the fix is on its way. 
Thank you for your patience!
4 Likes
@Misha, duly noted. Thank you for the prompt reply.
Excited to see this!
Any Eta on this one?
Hello @here
I’m thrilled to share that the fix was released! If you need further assistance, please open a ticket.
Thank you for your support and patience!
2 Likes