Skip to content
All integrations

Automate Kalima with Make

Make's HTTP module talks to Kalima's REST API with an API key. Your scenarios get every new transcript, AI summary and action item, and can send audio files to Kalima to transcribe.

Make offers an EU region, so the content your scenarios handle can stay in Europe on its way to your other apps.

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

Kalima as a step in your Make scenarios

Make is built for scenarios with branches, filters and many steps. Kalima joins them as an HTTP request: one module fetches what is new, and the modules after it decide where it goes.

Recordings of every kind work the same way, from team meetings and customer calls to interviews and lectures.

What gets in the way without an integration

The recording is done in Kalima. Everything after it is manual.

1

Copying summaries into other tools

The overview goes to the team, the tasks to the project tool, the notes to the customer record. By hand, that is three copies after every call.

2

Reading a transcript too early

A scenario that grabs a recording while it is still running sends half a transcript. Kalima's finished feed lists a recording only once it is complete.

3

Keeping data in Europe

Teams with a European data policy need every stop on the way to be in the EU. Kalima stores your data in Germany, and Make lets you choose an EU region.

How to connect Kalima to Make

Four settings in one HTTP module.

01

Create an API key in Kalima

Open Settings, choose Integrations and, under API keys, New key. Choose Read only for scenarios that only fetch data, and copy the key right away.

02

Add the HTTP module

In your scenario, add the HTTP app's Make a request module. Enter the URL, for example the finished recordings feed, and the method GET.

03

Send the key as a header

Under Headers, add Authorization with the value Bearer followed by your key, and turn on parsing of the response so later modules can map its fields.

04

Fetch only what is new

Each feed item has a sequence number. Store the highest one in a data store and pass it as afterSequence on the next run, and each item reaches your scenario once.

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 your scenarios can do with Kalima

The full REST API, not a reduced set of modules.

Finished recordings with their content

Ask for the transcript and the AI summary in the same request as the list of new recordings.

Separate feeds for summaries and tasks

Get each AI summary when it is saved, and each action item with its owner and due date as they were said.

Uploads from any source

Send audio or video from cloud storage, email or a form to Kalima as a new recording, with spoken languages and names to recognize.

Organizing from a scenario

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

Scenarios worth building first

Each one replaces a copy-and-paste step.

Notes for the customer recordSummaries feed, then a CRM module such as HubSpotThe call summary on the right contact without opening Kalima
A transcript archiveFinished feed with the transcript, then Google Drive or SharePointA document per recording in a shared folder
Tasks from every meetingAction items feed, then Asana, Trello or monday.comOne task per agreed action, with the owner named in the meeting
Transcribe uploaded filesA watch-files module, then a multipart POST to KalimaNew recordings in Kalima as soon as the file arrives

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.

Make questions

Common questions about using Kalima with Make.

Make connects with an API key, and API keys are available on Pro, Team and Enterprise.
Not as an app of its own. The HTTP module covers the whole REST API, and the setup guide shows the exact settings.
In the region of your Make organization. Make offers an EU region; choose it if your transcripts and summaries should stay in Europe.
Store the highest sequence number you have received and pass it as afterSequence on the next run. Kalima then returns only what came after it.
Yes, with a key that has the write scope. Send the file as multipart form data to the recordings endpoint. The transcribed duration is charged to your Kalima balance.

Add Kalima to your next scenario

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