Krisp.ai Integration

About Krisp Integration

The Krisp.ai integration enables automatic capture and organization of meeting data within Jasper. When team members have Krisp installed for their meetings, the following data is sent to Jasper and shown in the Meetings page of the Jasper desktop app:

Captured Meeting Data

Data Type	Description
Transcripts	Full meeting transcription with speaker identification
Action Items	AI-extracted tasks with assignee and due date suggestions
Key Points	Important discussion points and decisions
Outlines	Structured meeting summary

Setting Up the Integration

Step 1: Ask Us to Turn Krisp On

There is no settings screen for Krisp. Talk to us and we will switch it on for your organisation.

Step 2: Get Your Webhook URL

Each organization has a unique webhook URL in the format:

https://heyjasper.ai/webhooks/krisp/{your-org-uuid}

We will give you your organisation's URL when we switch Krisp on. Copy it for the next step.

Step 3: Configure Krisp

1. Log into your Krisp dashboard
2. Navigate to Settings → Integrations → Webhooks
3. Add a new webhook endpoint with your Jasper URL
4. Select the events you want to receive (see supported events below)
5. Save the configuration

Supported Webhook Events

The integration listens for the following Krisp webhook events:

Event	Description
transcript_created	New meeting transcript available
action_items_generated	AI-extracted action items ready
key_points_generated	Key discussion points extracted
outline_generated	Meeting outline/summary created
meeting_completed	Meeting has ended
summary_generated	AI summary generated

Viewing Meeting Data

Meetings appear in the Meetings page of the Jasper desktop app, next to your own recorded calls, and through the API below. There is no meetings page in the web app.

When a transcript arrives, Jasper sends it, with its action items and key points, to Anthropic's Claude for analysis automatically.

Troubleshooting

Webhooks Not Received

1. Ask us to confirm Krisp is switched on for your organisation
2. Check that the webhook URL is correctly configured in Krisp
3. Ensure the organization identifier matches your Jasper URL
4. Check Settings → Webhook Logs for recent entries

Meeting Data Missing

1. Check webhook logs for the meeting's events
2. Verify the processing status shows 'completed'
3. Look for error messages in failed logs
4. Contact support if the issue persists

Action Items Not Extracted

• Ensure the action_items_generated event is enabled in Krisp
• Check that the meeting had enough conversation to extract action items
• Verify the transcript was successfully processed

Security Considerations

• Keep the URL private: the webhook URL contains your organisation's ID, and that is the only secret. Jasper does not check a signature on Krisp webhooks unless your organisation has a webhook secret set (ask support); Jasper then requires it as a bearer token or an X-Webhook-Secret header.
• Async Processing: Processing happens asynchronously to prevent timeout issues

API Access

Access your own meeting data programmatically via the Jasper API. Each endpoint returns only the meetings you recorded or attended (Krisp heard your Jasper email address in them), whatever your role or token scope. The Jasper desktop app lists them under Meetings:

Endpoint	Description
GET /api/v1/krisp/meetings	List the meetings you recorded or attended, newest first
GET /api/v1/krisp/meetings/{id}	Get meeting details
GET /api/v1/krisp/meetings/{id}/transcript	Get full transcript
GET /api/v1/krisp/meetings/{id}/action-items	Get action items for meeting
PATCH /api/v1/krisp/action-items/{id}	Update action item status