Connect Gather and tl;dv to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Gather with tl;dv - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Timeline Item" from Gather.
Add your action
An action happens after the trigger—such as "Upload Recording" in tl;dv.
You’re connected!
Zapier seamlessly connects Gather and tl;dv, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- New Timeline Item
Triggers when a new item is added to a user's timeline, such as joining the space or registering for a program.
Try ItTriggerPolling - Updated User
Triggers when an existing user is updated.
Try ItTriggerPolling - Recording Added
Triggers when a new recording is created.
Try ItTriggerInstant - Recording nameRequired
- Recording file or recording download URLRequired
ActionWrite
- New User
Triggers when a new user is created.
Try ItTriggerPolling - Note tags
Try ItTriggerInstant- Transcript Added
Triggers when a new transcript is created.
Try ItTriggerInstant
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate tl;dv on the Zapier blog
Frequently Asked Questions about Gather + tl;dv integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Gather and tl;dv
How do I initiate the integration between Gather and tl;dv?
To integrate Gather with tl;dv, you'll need to set up a workflow that connects both applications through our platform. You'll start by choosing a Trigger from Gather, such as 'New Event Created', and then select an Action in tl;dv, like 'Create Recording'. This setup ensures that whenever a new event occurs in Gather, a corresponding recording is automatically created in tl;dv.
What permissions are required for the integration between Gather and tl;dv?
Our integration will require permissions to access relevant data and features in both Gather and tl;dv. Specifically, you'll need authorization to manage events in Gather and create recordings in tl;dv. When setting up the integration, you will be guided through granting these permissions.
Can I customize what information is shared between Gather and tl;dv during the integration?
Yes, during the setup of your workflow, you can define specific data fields that you'd like to transfer from Gather to your newly created recording in tl;dv. For instance, you could choose to include event title and description details from Gather into the notes section of a recording in tl;dv.
What types of events trigger actions from Gather into tl;dv?
In our current setup, you can use triggers like 'New Event Created', 'Event Updated', or 'Event Canceled' from Gather. These can initiate various actions in your connected tl;dv account, ensuring all updates are captured automatically as they're made.
Is it possible to integrate more than one action following a single trigger event between Gather and tl;dv?
Yes, when configuring your workflow between Gather and tl;dv through our platform, you can set multiple actions for a single trigger. For example, when an event is added in Gather ('New Event Created'), you can set it so that it not only creates a new recording but also sends out summaries or notifications via email within your team on tl;dv.
How often does the data sync happen once I've integrated Gather with tl;dv?
Once you've established the connection and defined triggers/actions through our service, data sync happens almost instantaneously for each defined trigger event occurring within Gather. The updates reflect immediately on your linked actions within the corresponding applications including any adjustments made on previous setups.
Are there any limitations I should be aware of when integrating processes between Gather and tl;dv?
The main limitation relates to the available triggers/actions currently offered by both platforms. Some complex workflows might not yet be supported due to these constraints but we are continuously expanding our capabilities based on user feedback and platform updates.