Record meetings, get transcripts, and access meeting notes automatically.
tl;dv currently provides 2 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Meeting Ready
Triggers when a meeting has finished processing and is ready
Transcript Ready
Triggers when a meeting transcript has been generated
Upload Recording
Import a meeting or recording from a URL
List Meetings
Search and list meetings
Get Meeting
Get meeting details by ID
Get Transcript
Get meeting transcript by meeting ID
Get Highlights
Get meeting highlights (notes) by meeting ID
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported tl;dv event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Meeting Ready
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported tl;dv action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Upload Recording
Combine tl;dv with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
Meeting Ready
Finishes with
Upload Recording, then preserve the outcome in Coherence
The exact authentication fields depend on tl;dv. The workflow structure stays straightforward:
Authorize the tl;dv account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with tl;dv or provide a complementary trigger or action.
tl;dv currently provides 2 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
tl;dv currently lists 2 triggers and 5 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported tl;dv triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
