Overview
This node interacts with the Fireflies API to fetch transcript details based on a provided Transcript ID. It is useful for workflows that need to retrieve and process meeting transcripts or audio transcription data stored in Fireflies. For example, you can use this node to automatically pull transcript metadata such as title, date, duration, and URL for further analysis, reporting, or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Transcript ID | The unique identifier of the transcript you want to fetch from the Fireflies service. |
| Credentials | An API key credential required to authenticate requests to the Fireflies API. |
Output
The node outputs JSON data containing a transcript object with the following fields:
title: The title of the transcript.id: The unique identifier of the transcript.date: The date associated with the transcript.duration: The length/duration of the transcript.transcript_url: A URL linking to the full transcript.
If an error occurs and the node is configured to continue on failure, the output will include an error field describing the issue alongside the original input data.
Dependencies
- Requires an active Fireflies API key credential for authentication.
- Makes HTTP POST requests to a GraphQL endpoint (in the provided code, it points to
http://127.0.0.1:3001/graphql, which should be replaced with the actual Fireflies API endpoint in production). - Uses the Axios library for HTTP requests.
Troubleshooting
- Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect or non-existent Transcript ID will result in empty or null transcript data.
- Network errors if the API endpoint is unreachable or misconfigured.
- Error messages:
- If the node throws an error related to authorization, verify that the API key credential is correctly set up.
- If the transcript is not found, check that the Transcript ID is correct.
- For network-related errors, ensure the API endpoint URL is accessible and correct.