How Do You Automate AI Proposal Creation With n8n and Gamma?

TL;DR

You can automate proposal creation by logging a completed client meeting, retrieving its transcript and AI summaries, requesting human approval, and sending the generated proposal to Gamma for slide deck creation. The workflow uses Fireflies, a Google Sheet, and two separate workflow parts to support quality control and future routing, so read on for the exact process and design choices.

Transcript

All right, imagine you just ho topped off a call and now you have to send out some sort of deliverable, whether that's meeting minutes or a proposal or something like that, which is actually a big part of my job when I was still working full-time. All of that can be automated now. So, in today's video, I'm going to be going over this workflow and w... Read More

Key Insights

• AI can automate the creation of business proposals from meeting transcripts, saving time and ensuring consistency.
• The workflow involves logging meeting details in a Google Sheet, which triggers the proposal generation process.
• Gamma's API is used to transform AI-generated text into professional slide decks with customizable themes.
• The system allows for human approval before generating a slide deck, ensuring quality control.
• Fireflies is used to capture meeting details, which are then processed for AI analysis.
• The workflow is designed for scalability, with separate paths for different meeting outcomes.
• The system uses a polling mechanism to ensure AI-generated summaries are complete before proceeding.
• Custom code nodes are used to clean and structure data for further processing in the workflow.

Questions & Answers

Q: How do you automate proposal creation with AI?

Trigger the workflow when Fireflies completes a meeting transcription, then retrieve the meeting transcript and related details. Log the information in a Google Sheet, request human approval, and pass approved content to a proposal generator that calls Gamma to create the slide deck.

Q: What tools are used to automate the proposal workflow?

Fireflies captures and processes meeting information, while a webhook starts the workflow after transcription completes. A Google Sheet logs meeting details, and Gamma receives an API call to create the professional slide deck.

Q: Why is the proposal system split into two workflows?

The first workflow logs the completed meeting, while the second handles slide deck creation. Keeping them separate makes it easier to add paths based on who attended the meeting or what follow-up is needed.

Q: What meeting information is logged in the Google Sheet?

The sheet stores the meeting date, title, attendees, gist, ID, and status. The second workflow pulls these logged details when processing a new meeting.

Q: How does Fireflies trigger the workflow?

The production webhook URL is added in Fireflies under developer settings, with the transcription-complete option enabled. After Fireflies processes a finished meeting transcript, it sends webhook data that includes the meeting ID and event type.

Q: Why does the workflow make another request to Fireflies?

The initial webhook body does not include the transcript, title, or other useful meeting details. The workflow uses the meeting ID from the webhook to request the transcript, title, host email, keywords, and AI-generated material from Fireflies.

Q: Why does the workflow wait and poll Fireflies?

Fireflies may finish the transcript before its AI-generated summaries and gist are ready. The workflow waits, checks whether the AI summary and gist exist, and repeats the check when they are missing.

Q: How is proposal quality controlled before Gamma creates the slide deck?

The workflow includes a human approval step because every meeting does not require a slide deck. Only approved material is passed to the proposal generator, which then calls Gamma to produce the presentation.

Summary & Key Takeaways

• Definition: The system turns completed client meetings into proposal slide decks through transcript retrieval, approval, proposal generation, and Gamma creation.

• Number: Two workflow parts separate meeting logging from slide deck creation.

• Tool: Fireflies sends a webhook after meeting transcription is complete.

• Tool: The Fireflies webhook provides the meeting ID and event type, but not the full transcript or title.

• Tool: A follow-up Fireflies request retrieves sentences, title, host email, keywords, summaries, and other meeting data.

• Tool: A Google Sheet records the meeting date, title, attendees, gist, ID, and status.

• When: The workflow waits and polls because Fireflies summaries and gist may not be ready immediately after transcription.

• Who: A human decides whether the completed meeting needs a slide deck before proposal generation continues.

• Tool: The proposal generator sends an API call to Gamma for a ready-to-use professional slide deck.

• Compare: Separate workflows make future routing easier than embedding meeting logging inside the Gamma creation workflow.