By the end of this tutorial, you’ll know how to connect Claap to lemlist, create an AI Column powered by the lemlist Agent, and generate highly contextual outreach based on your past call recordings and transcripts.
This workflow helps you turn meeting context into scalable personalization. Instead of manually opening calls, searching transcripts, and copying details into emails, you can let the agent find the right recording, extract the relevant insight, and write a personalized output for every lead in your campaign.
Why this matters
Claap often contains the most valuable sales context: pain points, objections, competitor mentions, decision criteria, and next steps. Using the Claap tool inside AI Columns lets you reuse that context automatically, so your follow-ups feel personal, accurate, and grounded in real conversations.
What this feature is
AI Columns in lemlist generate content directly in your campaign’s leads table. When you use the lemlist Agent provider, the column can also use tools to research before writing. One of those tools is Claap, which lets the agent search your Claap workspace for recordings, transcripts, contacts, and deal context related to a lead or company.
Who this is for
AEs and SDRs running follow-up or warm-account sequences
Customer success teams sending post-meeting or QBR follow-ups
Growth and RevOps teams scaling personalized messaging across many leads
Benefits
Use your own conversations as personalization data: outputs are grounded in what was actually said on calls.
Write hyper-relevant follow-ups: the agent finds the right recording and turns transcript insights into messaging.
Scale 1:1 quality across campaigns: one AI Column can personalize hundreds of leads at once.
Reuse deal context: tailor messaging using deal stage, competitors, objections, and next steps mentioned in calls.
Prerequisites
You should already have access to a lemlist workspace where you can manage team integrations.
You should already have a Claap workspace on a paid plan or active free trial.
You should already know that only Admins and Owners in Claap can generate an API key.
You should have leads imported into a campaign before generating an AI Column.
Core lesson
Phase 1: Prepare your Claap access
Generate a Claap API key.
In Claap, open your workspace name → Settings → API & Webhooks → API, then click Create API key.
Give it a descriptive name such as lemlist-agent-prod, create the key, and copy it immediately.
Why this step matters: lemlist uses this key to search your Claap workspace for recordings, transcripts, contacts, and deals. The full key is only shown once, so store it in a secure password manager as soon as it appears.
Expected outcome: you have a Claap key starting with cla_ ready to paste into lemlist.
Important: Free Claap plans do not support API access. If lemlist rejects your key with a 401 or authorization error, check that your Claap workspace is on a paid plan or active trial.
Phase 2: Connect Claap to your lemlist team
Open team settings and go to Integrations.
In lemlist, click your profile avatar in the bottom-left corner, then select Settings.
Why this step matters: Claap is connected at the team level, so once it’s set up here, it becomes available inside AI Columns for your workspace.
Select the Claap integration.
In Team settings, open Integrations, find Claap, and click Connect.
Why this step matters: this is where you authorize lemlist to use your Claap workspace as a research tool for agentic AI Columns.
Paste your API key and confirm the connection.
Paste your cla_... API key into the Claap API key field, click Add API key to lemlist, then confirm the success message by clicking I understand.
Why this step matters: once validated, Claap becomes an available tool inside AI Columns that use the lemlist Agent provider.
Expected outcome: Claap is connected and ready to be selected in AI Column configuration.
Phase 3: Create an AI Column in your campaign
Open the campaign leads table and create a new AI Column.
Go to your campaign, open the Lead list, click the + button above the table, and choose Create AI column.
Why this step matters: AI Columns are created directly in the leads table, so each lead gets its own generated output as a cell value.
Create the column from scratch.
In the AI Column Templates window, click Create from scratch.
Why this step matters: starting from scratch gives you full control over the tool, provider, and prompt so you can design a Claap-specific workflow.
Name your AI Column clearly.
Enter a descriptive variable name such as claap_followup, last_call_summary, or pain_points_from_call, then click Save.
Why this step matters: a clear column name makes it easier to reuse the output later in emails with variables like
{{claap_followup}}.Expected outcome: a new empty AI Column is created in your leads table.
Phase 4: Configure the Claap-powered prompt
Enable the Claap tool in the AI Column side panel.
In the right-side configuration panel, select the Claap recordings tool.
Why this step matters: without enabling Claap, the AI Column behaves like a standard LLM generation and won’t search your recordings or transcripts.
Choose the agent, write your prompt, and launch generation.
Set the AI Provider to lemlist agent Max or lemlist Agent Lite, write a prompt using lead variables like{{firstName}},{{lastName}},{{companyName}}, and{{email}}, then click Generate AI column.
Why this step matters: the variables tell the agent how to match the right person or company in Claap, and the provider determines whether tools are available.
Use Agent Lite for faster extraction and Agent Max for more reasoning across multiple recordings.
Expected outcome: generation starts in batch, and values appear progressively in the leads table for each lead.
Tip: Adding {{email}} to your prompt usually improves matching accuracy because it gives the agent a unique identifier to search in Claap.
Best practices for prompt writing
Use at least one strong identifier:
{{email}}, full name, or company name.Be specific about what the agent should look for, such as the latest recording, open deal, or recordings from the last 60 days.
Ask for a structured output when you need consistency, such as bullets, short summaries, or a fixed number of sentences.
If needed, add AI Context Center context so the agent can better judge what matters for your positioning and ICP.
Practical applications
Example 1: Personalized follow-up after a discovery call
Create an AI Column named discovery_followup.
Select lemlist Agent Max and enable Claap.
Use a prompt like: Search Claap for the most recent recording involving
{{firstName}}{{lastName}}at{{companyName}}(email:{{email}}). From the transcript, extract the main pain point, one specific phrase they used, and the next step we agreed on. Then write a 3-sentence follow-up email opener.Insert
{{discovery_followup}}directly into your campaign email.
Example 2: Account-level pitch based on deal context
Create an AI Column named account_pitch.
Use lemlist Agent Max with the Claap tool.
Prompt the agent to find the open deal for
{{companyName}}, inspect the latest recording, and identify the competitor mentioned and any budget objection.Generate a short pitch that acknowledges the competitor and reframes the objection.
Example 3: Reactivation for lost deals
Filter leads where the deal status is lost.
Create an AI Column named reactivation_hook.
Ask the agent to find the reason the deal was lost in Claap recordings and write a one-sentence reactivation opener.
Use the generated variable in your win-back sequence.
Example 4: Chain AI Columns together
Create Column A, such as call_summary, using lemlist Agent + Claap.
Ask it to summarize pain points, tools mentioned, decision-makers, objections, and next steps.
Create Column B, such as email_intro, using a standard AI prompt that references
{{call_summary}}.lemlist will run the dependency in order, so the summary is generated before the email intro.
Example 5: Inspect sources for quality control
Click a lead in the table to open its details panel.
Review the AI Column cell and the attached source recordings.
Open the source in Claap to verify quotes or context.
Regenerate only that lead if needed.
Plans, availability, and billing
Availability: available on all lemlist plans and on the Claap side when API access is supported.
Billing: each generation with the Claap tool costs 1 lemlist credit per lead per run.
Provider limitation: the Claap tool only works with the lemlist Agent provider.
Not supported: you cannot use Claap with OpenAI, Anthropic, Gemini, or Perplexity providers, and you cannot bring your own API key to the lemlist Agent provider.
Troubleshooting and pitfalls
Issue: My API key is not accepted
Root cause: this usually happens because the Claap workspace is on a free plan, the key was copied incorrectly, or the key was deleted in Claap.
Confirm the Claap workspace is on a paid plan or active trial.
Regenerate the key in Claap and copy it again carefully.
Make sure the key still exists in the Claap API page.
Issue: I enabled lemlist Agent, but it doesn’t use Claap
Root cause: the provider is correct, but the Claap tool was not activated in the AI Column panel.
Open the AI Column settings.
Verify the provider is lemlist Agent.
Turn on the Claap recordings tool explicitly.
Issue: The agent can’t find any recording for a lead
Root cause: the prompt does not include enough identifying data, the contact doesn’t exist in Claap, or there are no accessible recordings tied to that contact, company, or deal.
Add
{{email}}to the prompt if it is available.Check that lead fields like first name, last name, company, and email are populated.
Confirm the relevant recording exists in the Claap workspace and is visible under the API key’s permissions.
Issue: Generation stays on “Running”
Root cause: Claap-powered generations can take longer because the agent may search and read several transcripts before writing the result.
Wait a little longer than you would for a classic AI Column.
If it stays stuck for more than about 3 minutes, cancel and relaunch.
Check that the Claap connection is still valid in team settings.
Issue: I want the agent to search only certain recordings
Root cause: the prompt is too broad, so the agent has to decide across a larger set of calls.
Specify a timeframe, such as last 60 days.
Reference a deal, tag, or meeting type like discovery.
Ask for the latest recording attached to the open deal for
{{companyName}}.
Issue: I deleted the Claap key by mistake
Root cause: lemlist can no longer authenticate with Claap for future generations.
Create a new API key in Claap.
Update the connection in lemlist team settings.
Existing values already generated in the table remain unchanged.