Automate Kalima with n8n

n8n reads Kalima's REST API with an API key. A ready-made workflow fetches every new AI summary once and hands it to whichever app you connect next.

Run it on n8n Cloud or on your own server. Self-hosted, the transcripts and summaries your workflow handles stay on infrastructure you control.

Start for freeDownload the workflow

Laptop with a transcript on a desk, a conveyor belt carrying summary, task and document cards to a folder, a chat window and a task list

Summaries and transcripts in your own workflows

n8n is the automation tool teams pick when they want full control: their own server, their own logic, and code where a visual step is not enough. Kalima fits into it as a plain HTTP API, so every n8n node can work with what Kalima produces.

Each feed delivers every item once. A workflow asks for what is new since its last run and never picks up a transcript that is still being recorded.

What makes transcripts awkward to automate

Polling a transcription service sounds simple until the edge cases arrive.

Transcripts that are still growing

A recording that is still running, or still being corrected, should not be sent anywhere yet. Kalima's finished feed only lists a recording once nothing has changed in it for two minutes.

Items delivered twice, or missed

Timestamps collide when several items finish in the same moment. Kalima's feeds of recordings, summaries and tasks number every item instead, and asking for what comes after that number is exact.

Data that should not leave your servers

Some teams cannot route summaries through a third-party cloud. With self-hosted n8n, the content goes from Kalima straight to your server and your own apps.

How to connect Kalima to n8n

About ten minutes with the ready-made workflow.

Create an API key in Kalima

Open Settings, choose Integrations and, under API keys, New key. Name it n8n and choose Read only if the workflow only fetches data. Copy the key, Kalima shows it once.

Paste the workflow into n8n

Choose Copy the workflow at the top of this page, open an empty workflow in n8n and press Ctrl+V (Cmd+V on a Mac). It brings a 15-minute schedule, the request to Kalima's summaries feed and a step that turns each new summary into one item with readable fields. In Kalima's Integrations settings, the same button can put a new read-only key into it for you.

Add the key as Header Auth

In the Kalima request node, create a Header Auth credential with the name Authorization and the value Bearer followed by your key.

Connect your app and activate

Replace the placeholder at the end with Slack, Notion, Google Drive or any other node, map the fields and activate the workflow.

Illustration of two colleagues at a desk: a microphone picks up their conversation, a laptop shows four remote participants, and a transcript card with speaker dots and a summary card lie in front of them

What n8n can do with Kalima

The REST API that n8n calls is the same one behind the Zapier app.

Feeds for summaries, tasks and moments

New AI summaries, the action items in them and the moments marked while recording each have their own feed, alongside the feed of finished recordings.

Uploads with languages and terms

Send an audio or video file as a new recording, with up to three spoken languages, a translation language, context and names to recognize.

Organizing from a workflow

Rename and move recordings, name speakers, create projects, request a summary, export a file or turn on a share link.

A key with only the rights it needs

Read only covers every list, feed, search and export. Add write only for workflows that upload or change recordings, and revoke a key in one click.

Workflows that work well with n8n

Starting points for the most common jobs.

What you needHow Kalima helpsOutcome

Summaries to a team channelThe ready-made workflow, then the Slack or Microsoft Teams nodeEvery new summary posted once, oldest first

Transcripts into a knowledge baseThe finished recordings feed with the transcript included, then Notion or a database nodeA searchable archive on infrastructure you choose

Transcribe files from a folderA file trigger, then a POST of the file to Kalima's recordings endpointNew audio files transcribed without anyone uploading them

Your own logic on topA Code node after the requestFilter by project, route by keyword or reformat the summary before it goes out

Before you record

Kalima runs on your own device, so nobody in the meeting sees it. That is exactly why you should announce it: tell everyone before you start and ask for their consent. If you use Kalima at work, agree on it with your data protection officer and, where there is one, your works council first.

n8n questions

Common questions about using Kalima with n8n.

n8n connects with an API key, and API keys are available on Pro, Team and Enterprise. Your plan also sets how many keys you can have at once.

Not as a separate package. n8n's own HTTP Request node does the job, and the ready-made workflow sets it up for you, so there is nothing extra to install on your server.

The workflow remembers where it stopped only while it runs as an active workflow; a manual test always starts fresh. It then returns just the newest summary, so you can see the fields and map them.

Every 15 minutes is a good start and is what the ready-made workflow uses. Each run is one request to Kalima, and the number of requests an API key may make depends on your plan.

Yes. With self-hosted n8n, what Kalima sends goes to your server and from there only to the apps you connect. Transcription itself still runs in Kalima.

Related integrations

Automate Kalima with Zapier Automate Kalima with Make Save transcripts and summaries in Notion

Connect Kalima to your n8n

Start for free, then create an API key on the Pro plan or higher and import the workflow.

Start for free Talk to sales