Skip to main content
Pro plan. Tavus works through a connection, HTTP steps and listeners (Wait for webhook, Call & wait), which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
You train a replica of yourself once in Tavus. A Call & wait step then asks Tavus for a video with the contact’s name and this contact’s callback URL; Tavus calls back with a hosted link and the next LinkedIn message shares it.
How it connects: Tavus’s API with your key in the x-api-key header. See Tavus’s Create video docs. The request and callback below follow Tavus’s docs.

Before you start

  • Tavus plan: API plans include a number of video minutes (Tavus’s pricing).
  • A replica: trained in Tavus; copy its replica_id.
  • An API key: from Tavus’s developer portal.

1. Connect Tavus

In Kerux, open Integrations > Connections, click Connect on Custom API (under Developers):
  • How it signs in: API key in a header, Header name x-api-key, paste the key.
  • Base URL: https://tavusapi.com
Click Save, then Test connection.

2. Request the video and wait

After Invitation accepted, add a Call & wait step named tavus, pick the connection. Its request:
Tavus’s callback (from its docs, trimmed):
Add a Condition on {{steps.tavus.payload.status}} equal to ready, then a LinkedIn message with {{steps.tavus.payload.hosted_url}}. Errors and timeouts go to a plain text message.

Test with one contact

In the Builder, click Test to open Test on one contact. The journey shows the request and the callback when it arrives.

Common errors

The key is wrong. Create a new one in Tavus’s developer portal.
The replica id is wrong or the replica isn’t finished training.
Tavus couldn’t generate the video. The Condition sends the contact to the text message; check the video in Tavus.
Related: Webhook steps, HeyGen, Vidyard.