Send a Telegram message for each new Krisp transcript

Each time Krisp creates a meeting transcript, this workflow sends a Telegram text message built from it to the chat you choose, so you can see what was said without opening Krisp.

Krisp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.1k sites Free to import

The Send a Telegram message for each new Krisp transcript workflow on the FlowMattic canvas, with 2 steps across Krisp, Telegram — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Krisp records and transcribes your calls, but the transcript waits in Krisp until you go and look. If you spend more time in Telegram than in your meeting tools, a message there is a quicker way to know a call has been written up. This workflow sends one for every new transcript.

The Krisp trigger fires when a meeting transcript is created. FlowMattic receives the transcript data and makes it available to map. The Telegram step then sends a text message through your bot to the chat you set, with the content you build from the Krisp fields, such as the meeting title and the transcript text.

Long meetings produce long transcripts, so decide whether you want the full text in Telegram or only the meeting details. Telegram's Send a Text Message action supports markup, which helps you format the message. You can check every Krisp-to-Telegram run, with the data it carried, in Task History.

Founder reviewing sales calls on the move

After each call recorded with Krisp, the founder gets the transcript in a private Telegram chat and reads it between meetings.

Team group for client meetings

Send the message to a Telegram group so colleagues who missed a client call can catch up on what was discussed.

Personal archive of calls

Use a Telegram chat as a searchable log of meeting transcripts, separate from your work inbox.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Krisp Transcript Created
Fires when Krisp creates a transcript for one of your meetings. The transcript and meeting details are passed to the Telegram step.
Step 2Action
Telegram Send a Text Message
Sends a text message from your Telegram bot to the chat you choose. Map Krisp's meeting details and transcript into the message, using markup for formatting if you like.

What you need

FlowMatticCore
Krisp AccountAccount
Telegram AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

If transcripts are too long for comfortable reading, send only the meeting title and time, or build a second workflow on Krisp's Notes Generated trigger to send the shorter notes instead.
Add a Filter after the trigger that continues only for meetings whose title contains a client or project name, so only those transcripts reach Telegram.
Record a short test meeting in Krisp after import so FlowMattic captures the transcript fields before you build the message.

Questions about this workflow

Do I need a Telegram bot for this Krisp workflow?

Yes. FlowMattic's Telegram actions send messages through a bot you connect. Add the bot to the chat or group where you want the transcripts.

Does the message include the whole Krisp transcript?

It includes whatever you map. You can place the full transcript in the message or send only the meeting details.

Can I get Krisp's meeting notes instead of the transcript?

Yes, by switching to a different Krisp event: FlowMattic offers Notes Generated and Outline Generated alongside Transcript Created. Swap the trigger, or build a second workflow, to send those.

Is every Krisp meeting sent to Telegram?

Every meeting that gets a new transcript starts a run, as nothing in the template narrows it down. Add a Filter to limit it.