Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

tl;dv

Record meetings, get transcripts, and access meeting notes automatically.

CategoryProductivity
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect tl;dv with Flows360

Record meetings, get transcripts, and access meeting notes automatically.

Use the tl;dv connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 2 triggers.

Available actions

  • Upload Recording
  • List Meetings
  • Get Meeting
  • Get Transcript
  • Get Highlights

Available triggers

  • Meeting Ready
  • Transcript Ready

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: tl;dv
  • Package: @activepieces/piece-tl-dv@0.1.7
  • Exact artifact digest: sha256:70ccfcd91904f2a72475068897d660c0a1383a46913e5e2ab35d191aeb523f36
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Upload Recording (upload_recording), Import a meeting or recording from a URL Classification: read.
  • List Meetings (list_meetings), Search and list meetings Classification: read.
  • Get Meeting (get_meeting), Get meeting details by ID Classification: read.
  • Get Transcript (get_transcript), Get meeting transcript by meeting ID Classification: read.
  • Get Highlights (get_highlights), Get meeting highlights (notes) by meeting ID Classification: read.

Trigger contracts

  • Meeting Ready, webhook.
  • Transcript Ready, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions5
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Upload Recording Yes No Import a meeting or recording from a URL
List Meetings Yes No Search and list meetings
Get Meeting Yes No Get meeting details by ID
Get Transcript Yes No Get meeting transcript by meeting ID
Get Highlights Yes No Get meeting highlights (notes) by meeting ID
Meeting Ready Yes No webhook trigger declared by the pinned package.
Transcript Ready Yes No webhook trigger declared by the pinned package.

Supported actions

Upload Recording · Read

Import a meeting or recording from a URL

upload_recording · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the meeting or recording
  • url · string · Required, Publicly accessible URL of the recording. Supported formats: .mp3, .mp4, .wav, .m4a, .mkv, .mov, .avi, .wma, .flac
  • happenedAt · string · Optional, The date and time when the meeting occurred. If not provided, the current date will be used.
  • dryRun · boolean · Optional, Test the import without persisting to the database
  • participants · array · Optional, Email addresses of meeting participants
List Meetings · Read

Search and list meetings

list_meetings · Risk: low · Retry: safe

Inputs

  • query · string · Optional, Search for meetings by name or content
  • page · number · Optional, Page number to return (default: 1)
  • limit · number · Optional, Number of results per page (default: 50)
  • from · string · Optional, Search meetings from this date
  • to · string · Optional, Search meetings up to this date
  • onlyParticipated · boolean · Optional, Only return meetings you participated in
  • meetingType · string · Optional, Filter by meeting type
Get Meeting · Read

Get meeting details by ID

get_meeting · Risk: low · Retry: safe

Inputs

  • meetingId · string · Required, Select a meeting
Get Transcript · Read

Get meeting transcript by meeting ID

get_transcript · Risk: low · Retry: safe

Inputs

  • meetingId · string · Required, Select a meeting
Get Highlights · Read

Get meeting highlights (notes) by meeting ID

get_highlights · Risk: low · Retry: safe

Inputs

  • meetingId · string · Required, Select a meeting

Triggers

Meeting Ready · Webhook

Triggers when a meeting has finished processing and is ready

Inputs

  • webhookInstructions · string
Transcript Ready · Webhook

Triggers when a meeting transcript has been generated

Inputs

  • webhookInstructions · string

Setup

Setup

  1. Add the tl;dv connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-tl-dv@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required tl;dv connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-tl-dv@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com