# Claap + Lutril: setup guide

> Lutril connects to Claap with a workspace API key. It reads your Claap users with their role, their licence and their state, and it time boxes access from both ends: a grant invites somebody or reinstates an account Lutril suspended earlier, and the deadline suspends it again. A grant on somebody who already has a working account raises only their role, and Lutril writes the previous role back when the access ends. Nothing is ever deleted, so every grant can be undone.

Source: https://www.lutril.com/fr/integrations/claap
Category: Communication
Auth: api_key
Last verified: 2026-11-09

---

## Setup

1. [object Object]
2. [object Object]
3. Copy the key as soon as it appears. It starts with cla_ and Claap shows it once, so it cannot be read again afterwards.
4. Leave Full access off. It only widens the key to private recordings, which Lutril never reads, and only a workspace Owner can turn it on.
5. In Lutril, connect Claap and paste the key. Lutril sends it as the X-Claap-Key header, and the key is encrypted at rest.
6. [object Object]
7. A grant only ever raises a role. Anyone who already holds the role they asked for, or a higher one, is left exactly as they were, so a deadline can never take away access that Lutril did not grant.
8. Reinstating an account takes two calls, and Lutril makes both. Claap resets a member's role to Member whenever an account's state changes, so Lutril reactivates the account and then applies the role the grant is for. Without the second step somebody would come back able to sign in but without the access they asked for.
9. Guests are listed as guests rather than as members, so a review of who belongs to the workspace does not quietly include people outside your company. A guest cannot be given a time boxed role, because Claap's API cannot set the guest role back again afterwards. Those grants are refused with an explanation rather than made permanently.

## Access requested

- The key is workspace scoped rather than scope based. It must be created by an Admin or an Owner, because the API and Webhooks settings are only available to those two roles.
- Full access is not required. Lutril reads and manages users and invitations, and never reads recordings, transcripts or deals.

## References

- [Claap documentation](https://docs.claap.io/api-reference/authentication)
- [Claap console](https://app.claap.io/settings/api)
- [Claap API authentication](https://docs.claap.io/api-reference/authentication)
- [List users endpoint](https://docs.claap.io/api-reference/endpoint/list_users)
- [Update user endpoint](https://docs.claap.io/api-reference/endpoint/patch_user)
- [Invite users endpoint](https://docs.claap.io/api-reference/endpoint/post_invite)
- [Using Claap's API](https://help.claap.io/en/articles/11833785-using-claap-s-api)