Granola to Telegram meeting brief automation

Build an agent workflow that posts a clean meeting brief to my Telegram whenever Granola finishes a new meeting note.

Trigger: a Granola poll trigger on the new-note event so this runs the moment a fresh note is created. Don't run on edits to existing notes, only on the initial creation.

When the trigger fires, the agent should do three things:

1. Call Granola's Get Note operation with the triggered note ID to pull the full note, including the summary, attendees, calendar event metadata, and action items. The transcript is not needed for this workflow.

2. Rewrite the note as a Telegram-friendly brief with these sections, in this order: (a) a one-line header with the meeting title and date, (b) a single short paragraph titled 'What happened' that summarizes the meeting in two to three sentences, (c) a 'Decisions' bullet list capturing concrete decisions made, and (d) an 'Action items' list where each item uses the format '• [Owner] task — next step'. If a section has no content (no decisions, no action items), skip it rather than padding with filler.

3. Call Telegram's Send Message operation to post the brief to the configured destination. Default the destination to 'me' (Saved Messages) so it lands in the user's personal note-to-self chat with zero extra setup. Let the user override the destination at workflow setup to any peer they want: a chat title, an @username, a phone number from their contacts, or a chat ID.

Formatting notes: Telegram messages render plain text well, so use line breaks and simple bullets (• or -) instead of heavy markdown. Keep the whole brief under roughly 1500 characters so it reads comfortably on mobile. If the note is unusually short (a quick 1:1 with no real outcomes), still post the brief, but keep it tiny — a one-liner is fine. Don't include the raw transcript or links to internal Granola URLs in the brief.

Additional information

What does this prompt do?

Watches Granola for new meeting notes and runs the moment a fresh one is ready.
Rewrites each note as a mobile-friendly Telegram brief: a one-paragraph recap, the decisions, and owner-tagged action items.
Posts the brief to your Telegram Saved Messages by default, or any chat or group you choose.
Keeps post-meeting context flowing into the messenger you already check on your phone.

What do I need to use this?

A Granola account on the Business or Enterprise plan, with a personal API key generated in the desktop app.
A Telegram account you can sign into to authorize the workflow.
The chat where briefs should land (Saved Messages works out of the box, or pick a colleague DM, group, or channel).

How can I customize it?

Change the destination chat: stick with Saved Messages for personal review, or send to a teammate, group, or project channel.
Adjust the brief style: shorter bullets, a longer narrative, or extra sections like risks, blockers, or open questions.
Filter which meetings count: only notes with specific words in the title, only meetings longer than a threshold, or skip personal calls entirely.

Frequently asked questions

Where does the brief get posted?

By default, your Telegram Saved Messages chat, which is your personal note-to-self space. You can switch the destination to any chat, group, or channel you already have access to.

Will my whole team see it?

Only if you point the workflow at a shared group or channel. The Saved Messages default is private to you.

How fast does the brief arrive after a meeting ends?

As soon as Granola finishes generating the note, usually a minute or two after the call wraps. The workflow checks for new notes on a regular interval.

Can I tweak the brief format?

Yes. An agent writes the brief, so describe the structure you want in plain English (shorter, more bullets, extra sections) and it will adapt.

Do I need a Granola paid plan?

Yes. Personal API keys are only available on Granola Business or Enterprise plans, and on Enterprise your workspace admin has to enable personal keys first.