Automate meeting notes and follow-ups with AI

Meeting notes fail in the gap after the call, not during it. Someone meant to send the recap, the owner of the next step was unclear, and three days later the only record is a calendar title. You can close that gap with three tools that do different jobs. Granola captures the conversation without putting a bot in the participant list, and it builds notes from what you jot plus the transcript. Fyxer lives in the inbox: it drafts the follow-up so you can edit it in the place you already send mail. Lindy is the agent you use when the follow-up has to become more than an email, and you still want an approval before anything is sent.

You do not have to run all three on every call. The setup below tells you which one to open, how to configure it, and how to pass a note from one to the next without pasting a transcript into a random chat.

The Granola link on this page includes an offer of the first month free.

Decide the job before you install anything

Split the hour after a meeting into four questions.

1. What was said, including the bits you did not type?
2. What did you mean to remember, in your own words?
3. What email has to go out, and who has to approve the wording?
4. What has to happen in another system, such as a task list or a CRM, if you use one?

Granola is built for the first and second. Fyxer is built for the third. Lindy is built for the fourth, and it can also draft mail, but the reason to add it is the hand-off beyond the inbox. If you only need a recap for yourself, stop after Granola. If the recap is an email and nothing else, Granola plus Fyxer is enough. Add Lindy when a person would otherwise copy the same three bullets into a second tool.

Tell the other people on the call what you are using when a tool joins as a visible participant. Granola's design is to record from the device instead of joining the meeting. Fyxer's meeting notes product describes a notetaker that joins the call. Those are different experiences for everyone else on the invite. Pick the one that matches the room. A customer call where a surprise bot would be unwelcome is a Granola call. An internal stand-up where everyone expects a notetaker can be a Fyxer call.

Capture the call in Granola

Install the Granola desktop app and sign in with the account you use for work. Connect the calendar Granola asks for, so the note is attached to the right meeting instead of a blank document you have to name later. The offer linked from this tutorial is the first month free. Confirm the terms on the signup screen. This page does not restate a price.

Granola's own guide to AI notes describes the loop you should actually practice:

1. Start the note when the meeting starts, from the meeting on your calendar.
2. During the call, type rough prompts, not a transcript. "Budget concern." "Wants a pilot in June." "Legal has to review." You can type nothing. Granola's point is that the words you do type steer the summary. A blank note becomes a generic recap. A few sharp bullets become a recap about those bullets.
3. When the call ends, enhance the notes. Granola describes the result as your text staying distinct from the model's additions, so you can see what you wrote and what was filled in from the transcript.
4. If a line looks wrong, ask Granola about that line and check it against the transcript excerpt it shows you. Do this for numbers, dates, and names. Those are the words a fluent summary gets wrong.

Granola says it transcribes from the device audio and does not keep the audio recording. Treat that as their description of the product, and read their current security note if the call is sensitive. Do not record a conversation you are not allowed to record. Laws and workplace rules differ. A tool that stays off the participant list does not, by itself, answer that question.

Share only when the note is right. Granola describes notes as visible to you until you copy a share link or put the note in a shared folder. Send the link to the people who were in the room, not to a wide channel, until you have a habit of reading the gray text first. Integrations they document include places like Notion, Slack, HubSpot, and Zapier. Which of those are available can depend on the plan. Check the product rather than assuming every destination is turned on.

A note worth keeping has five lines, even if the enhanced version is longer:

Decision:
Owner:
Date they named:
Open question:
Exact phrase I should not paraphrase:

Fill those from the enhanced note and delete any enhanced sentence that does not serve them. You are not required to forward the whole summary.

The catalogue record is Granola.

Open Granola

Draft the follow-up in Fyxer

Fyxer is the inbox step. Connect it to the email account you actually send from, using the providers in their setup flow. Let it see enough of your sent mail to imitate your pacing. Then turn on the meeting notes feature if you want Fyxer itself to attend, or skip that and paste a Granola summary in when you want the bot to stay out of the room.

Fyxer's meeting product describes three outputs that matter here. It summarizes the call, it pulls action points, and it drafts a follow-up. It also describes a prep email before an upcoming meeting that refers to the previous one. Use the draft as a draft. Open it, check every name, date, and commitment against the Granola note, and only then send. A follow-up that promises a date nobody agreed to is worse than a late follow-up.

If Granola already produced the note, do not make Fyxer re-interpret the whole transcript. Paste the five-line note into the draft and tell Fyxer, in the composer or in whatever instruction field it gives you, to write the email from those lines only. You get your voice, without a second model inventing a sixth commitment.

A follow-up that is safe to send has this shape:

Subject: Next step after today's call

Thanks for the time today. Here is what I am doing next:
- I will send the pilot outline by Thursday.
- I will leave the legal review with you.

The open question on my side is whether June is a hard date or a target.
I will wait for that before I book the working session.

Every bullet is something a human in the meeting would recognize. If you cannot point at the moment it was said, delete the bullet. Fyxer can produce a polished paragraph that fails this test. Polished is not the goal.

The catalogue record is Fyxer.

Open Fyxer

Hand the next system to Lindy, with approval

Use Lindy when the email is not the end of the work. A typical case: the call agreed a follow-up email, a reminder in three days, and a note on an account record. Doing that by hand is how the reminder gets lost. Doing it with an agent that sends on its own is how the wrong email gets sent. Configure the agent so it prepares, and you approve.

In Lindy, create an agent with a boring name, Meeting follow-up. Give it a trigger you can explain. The clearest trigger is manual: you paste the five-line Granola note, or you forward the Fyxer draft. A calendar trigger that runs the moment a meeting ends is convenient and also easy to fire on the wrong event. Start with the manual trigger for a week. Add the calendar trigger only after the drafts have been right.

The instructions to the agent should be short enough to audit:

You prepare a follow-up. You do not send it.

Input: a meeting note with a decision, an owner, a date, and an open question.

Do this:
1. Draft a short email in plain sentences. Do not add commitments that are not in the note.
2. List any task that has an owner and a date, as separate lines.
3. If a CRM or chat tool is connected, prepare the update. Do not submit it.

Stop and wait for approval before any send, post, or record update.
If the note has no date, ask for one. Do not invent one.

Connect Gmail or the calendar only if that connection is required for the draft you want. Connect a CRM or Slack only after the email draft has been right three times. Each connection is another place a bad note can land. Lindy's value is that it can reach those systems. Your job is to keep the approval step in front of the send.

When you approve, read the email as if you were the recipient. Then look at the task lines. A task with no owner is a wish. Send it back to the agent with the owner filled in, or drop the task.

The catalogue record is Lindy.

Open Lindy

Run the three together on one real meeting

Use the next low-stakes internal call as the dress rehearsal, not a customer negotiation.

1. Start a Granola note. Type three rough bullets during the call. Enhance it. Correct one proper noun.
2. Copy the five-line version into Fyxer and generate a draft. Delete one sentence that was not in the five lines. Send it only if the call actually needs an email. Sending to yourself is a valid test.
3. Paste the same five lines into the Lindy agent. Approve nothing on the first run. Look at what it prepared. If it added a commitment, tighten the instructions and run it again on the same note.

After that, write down which tool you will skip next time. A founder who takes all of their calls on a laptop, and who hates bots in the room, may live in Granola and only open Fyxer to send. A recruiter who lives in the inbox may let Fyxer take the notes and never open Granola. A sales team that must update a CRM may use Granola for the capture and Lindy for the record, and let Fyxer go. The mistake is running all three on every call because a tutorial listed them.

Keep a single place for the five-line note. If it exists in Granola, in your inbox, and in a CRM, and the three copies disagree, you have automated confusion. The five lines are the source. The email and the CRM update are derivatives. When they disagree, fix the derivatives.

What not to automate

Do not auto-send the first version of a follow-up. The models are good at tone and bad at whether you actually promised a date. Approval is the feature, not a temporary caution.

Do not drop a raw transcript into a group chat. Transcripts are long, they mis-hear names, and they include asides that were not for the channel. Share the five lines, or a Granola link, with the people who were there.

Do not record a call to get around someone who declined to be recorded. Turn the tool off.

Do not put medical, legal, or payment details into a prompt "so the summary is complete" unless you already know that product is allowed to hold them. A meeting note tool is not a filing cabinet you have reviewed. If you are unsure, leave those details in the system that already stores them, and keep the note to the decision and the owner.

Prices and plan limits are not stated here. Each product's signup screen is the current offer. The only offers this page is passing on are the ones tied to the links: Granola's first month free, via the Granola button. Fyxer and Lindy are linked because they are the tools in the workflow. Their IQ.net records are Fyxer and Lindy.

If the follow-up is a deck rather than an email, the next guide is Share pitch decks and docs securely with Papermark. Send a link with an expiry. Do not attach the PDF to the Fyxer draft out of habit.

Open Granola

Open Fyxer

Open Lindy