SaaS

ElevenLabs

Connect your ElevenLabs workspace to Ploy to automatically discover everyone in the workspace, the seat type each person holds, whether they are locked, and the groups they belong to — along with what each group unlocks in the product. This keeps your ElevenLabs access picture up to date in Ploy, and lets Ploy invite, lock, remove and re-seat workspace members and manage group membership when you ask it to.

Before you begin

  • Ploy connects using an ElevenLabs API key. One key belongs to one workspace, so there is nothing else to configure — no tenant ID and no workspace selector.

  • The key must be created by an account with the workspace admin seat type. Reading the workspace member directory is an admin-only operation in ElevenLabs, and that is the first thing Ploy does.

  • If your ElevenLabs key creation screen lets you choose permissions for the key, include the workspace member and workspace group permissions so Ploy can read the directory and, if you use them, perform the member and group changes described below.

  • Ploy only calls ElevenLabs' workspace administration endpoints — the member directory, groups, and invitations. It does not touch your voices, projects or audio content.

Create an ElevenLabs API key

  1. Log in to ElevenLabs as a user with the workspace admin seat type.

  2. Open your profile menu and choose API Keys.

  3. Create a new key. If the key has configurable permissions, grant it access to workspace members and workspace groups.

  4. Copy the key and keep it to hand for the next section.

Connect ElevenLabs to Ploy

  1. In Ploy, click Integrations in the left sidebar.

  2. Click Add new integration and search for ElevenLabs.

  3. The setup page shows an ElevenLabs API reference link if you want to read more about creating a key.

  4. In Enter your ElevenLabs API key, paste the key you just created.

  5. Save the connection. Ploy verifies the key by reading your workspace member list — the same call its regular sync makes — so a key that connects successfully is a key that can sync.

What data syncs

  • Workspace members: everyone in the workspace, with their email, name and seat type, feeding identities and who has access to ElevenLabs.

  • Seat types and ownership: each member's seat (workspace admin, workspace member or workspace lite member) appears as their access level, and the workspace owner is flagged separately.

  • Locked members: ElevenLabs' locked state is picked up directly, so a locked member shows as blocked in Ploy on the very next sync.

  • Groups: your workspace groups and who belongs to each one. ElevenLabs automatically creates a hidden personal group for every member; Ploy filters those out so only real groups appear.

  • Group permissions: the product permissions each group carries (text to speech, dubbing, conversational AI and so on), shown on the group so you can see exactly what membership unlocks.

Data syncs roughly every hour. One thing that cannot sync: ElevenLabs' API has no way to list pending invitations, so someone you have invited appears in Ploy once they accept and join the workspace.

What Ploy can do in ElevenLabs

With the connection in place, Ploy can also make changes in your workspace — for example from onboarding and offboarding flows or access requests:

  • Invite a user: sends an ElevenLabs workspace invitation to an email address, optionally with a seat type and groups. If no seat type is given, ElevenLabs applies its own default.

  • Lock and unlock a member: suspends a member's access using ElevenLabs' own locked state, and restores it later. Locking keeps the seat.

  • Change a member's seat type: switches a member between workspace admin, workspace member and workspace lite member.

  • Remove a member: permanently removes someone from the workspace and releases their seat. Unlike locking, this is not reversible.

  • Revoke a pending invitation: withdraws an invitation that has not been accepted yet.

  • Grant and remove group membership: adds someone to or removes them from an ElevenLabs group, from the group's page in Ploy or via an access request.

Before locking, re-seating or removing anyone, Ploy looks the person up in the live workspace directory first, so a change can only ever apply to the member it was aimed at.

Troubleshooting

"ElevenLabs rejected that API key. Create a new one and paste it again."

The key is invalid or has been revoked. Create a fresh API key in ElevenLabs and connect again in Ploy.

"That API key reached ElevenLabs but is not allowed to read workspace members."

The key works, but the account it belongs to does not have the workspace admin seat type — reading the member directory is an admin-only operation. Create the key from an account with the workspace admin seat type and try again.

"We could not reach ElevenLabs with that API key. Check the key and try again."

Something went wrong verifying the connection. Check the key was pasted completely, and try again in a moment.

A group I expect to see is missing

Ploy deliberately hides ElevenLabs' auto-created personal groups (one per member, named after their email address), because they are not real access containers. If a genuine shared group is missing, wait for the next hourly sync.

Was this helpful?
Was this helpful?