Skip to main content

Confluence Integration

Connect tl;dv to Confluence to automatically send meeting notes, transcripts, and summaries to new or existing pages in your Spaces.

Written by Suellen Lorga

The Confluence integration sends your tl;dv meeting information straight into your Confluence Spaces. You can create a new page for each meeting, or keep adding to a page you already have. Your team gets meeting notes where they already document their work, without anyone copying and pasting.

There are 2 ways to send your meeting information:

  • Automatically: Set up a workflow that runs whenever a new meeting recording matches your conditions.

  • On demand: Choose a meeting and manually trigger an existing workflow.

This guide explains how to connect Confluence, set up your workflows, and fix the most common issues.

Part 1: What tl;dv sends to Confluence

You decide what goes on the page: you build the page name and the page content yourself, mixing your own text with meeting details such as:

  • Meeting title

  • AI Notes

  • Transcript

  • Participants name and Participants email

  • Meeting date

  • Link to the meeting in tl;dv

🚨 Important: The meeting link isn’t public. Only people who already have access to the meeting in tl;dv can open it.

💡 Participants without a name in their profile are left out of Participants name but still appear in Participants email, so the two lists may not match.

💡 Action items only show up in the AI Notes if your meeting notes template creates them.

Part 2: Connect Confluence to tl;dv

You can connect your Atlassian account in two places:

  • From the integration page: In tl;dv, click Integrations in the left sidebar, then click the Confluence tile in the Marketplace tab. Under Connection, click Connect.

  • While creating a workflow: Click Connect to Confluence in the action step.

Sign in with your Atlassian account and allow access. You only need to do this once per tl;dv account.

💡 You can start building a workflow before connecting, but you won’t be able to click Continue past the action step until Confluence is connected.

🚨 tl;dv creates and edits pages using the permissions of the Atlassian account you connect. Make sure this account can create and edit pages in the Spaces you want to use.

Part 3: Create an automated Confluence workflow

Workflows send meeting information from tl;dv to Confluence automatically. You decide what gets sent, where it goes, and which meetings trigger it.

Workflow types

When you create a workflow, you choose its scope:

  • Individual workflow: applies only to meetings you record. Available on all plans.

  • Team workflow: applies to meetings recorded by your team members. Team workflows can be created by team admins on the Business plan or above.

Use an individual workflow for your own meetings, and a team workflow when you want the whole team’s meetings documented the same way.

Available Confluence actions

Action

What it does

Create a page in Confluence

Creates a new page in the Space you choose. If a page with the same name already exists in that Space, the new content is added to the end of that page instead.

Add meeting content to an existing page in Confluence

Adds the meeting content to the end of a page you choose, below a divider. Nothing already on the page is replaced.

💡 You may also see Add meeting content to an existing database in Confluence marked as coming soon. This action isn’t available yet.

Setup follows the same flow for both actions. The only differences appear in Step 5 (Configure the action).

1. Open the Confluence integration

In tl;dv, click Integrations in the left sidebar, then click the Confluence tile in the Marketplace tab.

2. Choose a workflow type

Click New workflow, select Individual workflow or Team workflow, then click Confirm.

3. Pick an action

Choose Create a page in Confluence or Add meeting content to an existing page in Confluence.

4. Set the trigger and conditions

  1. The trigger is When a new recording is ready.

  2. (Optional) Add conditions to limit when the workflow runs. Available criteria include Meeting type, Meeting title, Participants, and Email domain.

  3. Click Continue.

💡 Use conditions to send the right meetings to the right place. For example: planning meetings to your Product Space, and customer calls to your Customer Success Space.

5. Configure the action

  1. If you haven’t connected Confluence yet, click Connect to Confluence.

  2. Choose the Space from the dropdown. It lists the Spaces from your Confluence site, and you can search it.

  3. Fill in the rest depending on the action you picked.

For Create a page

  1. Fill in the Page name.

  2. Fill in Content – what should be added to the page? with your own text, meeting details, or both.

For Add meeting content to an existing page

  1. Choose the Page. The dropdown only lists pages from the Space you selected.

  2. Fill in Content – what should be added to the page? The new content is added to the end of the page, below what’s already there.

🚨 Choose your page name carefully. A fixed name like Weekly sync sends every meeting to the same page, which keeps growing over time. If you want one page per meeting, include the meeting title and meeting date in the page name. For example: {Meeting title} – {Meeting date}.

💡 Text fields accept up to 1,000 characters. If you go over, you’ll see Character limit exceeded and won’t be able to save.

6. Test the workflow

Every workflow needs a successful test before you can turn it on.

  1. Click Continue to reach the Test step.

  2. Select a past meeting and click Test workflow.

  3. When you see Test passed!, check the result in Confluence. If you want to change something, adjust the workflow and click Test again.

🚨 The test runs for real. It creates a page, or adds content to one, in Confluence. Delete it afterwards if you don’t need it.

7. Turn on the workflow

After a successful test, the Automate workflow? card appears. Switch the toggle on to run the workflow automatically on new recordings.

💡 You can also leave it off and run the workflow only when you want, using Trigger now (Part 4).

8. (Optional) Rename your workflow

Click the workflow title at the top of the page (e.g., Integration 1) and rename it to something descriptive like Product – Sprint reviews or CS – Customer calls. This makes it easier to find later and to pick from the Trigger now menu.

Part 4: Run a Confluence workflow manually

Available on the Pro plan or above.

Automatic workflows run on every meeting that matches their conditions. Trigger now lets you run a workflow on one specific meeting, whenever you want.

  1. Open the meeting in tl;dv.

  2. Click Trigger now.

  3. Pick one of your workflows from the list.

When to use it

  • Keep automation selective. Leave your workflows off and send only the meetings you choose.

  • Send an older meeting. Workflows don’t run on meetings recorded before you created them, so use Trigger now for those.

Good to know

  • Only the meeting organizer or a meeting admin can use Trigger now.

  • Only workflows that have passed their test appear in the list.

  • The workflow’s conditions still apply. If the meeting doesn’t match them, nothing happens.

  • Each manual run uses one integration credit.

Triggering twice adds the content twice

🚨 tl;dv does not check whether a workflow has already run on a meeting. If you trigger it again, the meeting content is added to the page a second time. Before re-running a workflow, delete what the previous run added in Confluence.

Part 5: Use custom prompts to write your pages

Available on the Business and Enterprise plans.

If you see the Custom prompt option in the Page name or Content field, switch it on to have tl;dv write that field for you with AI. This is useful when the full AI Notes or transcript is more than your team needs. Prompts can be up to 10,000 characters.

Example: Meeting summary for a project page


Summarize the meeting in 3 bullet points: what was discussed, what was decided, and what happens next. Include owners and dates when mentioned.

Example: Decision log


List every decision made in this meeting as a bullet point, with the person who made it. If no decisions were made, write “No decisions recorded.”

Tips for writing prompts:

  • Be specific about format. Ask for bullet points, a table, or headings.

  • Handle empty cases. Tell tl;dv what to write when a topic isn’t discussed.

  • Constrain length. Without an instruction, output can run long. Add “no more than 5 bullet points” or similar.

Troubleshooting

Why didn’t my meeting show up in Confluence?

Check that:

  • The workflow is turned on in the Automate workflow card.

  • The meeting matches the conditions you set.

  • The recording’s creator is in scope for the workflow:

    • Individual workflows only run on meetings recorded by you.

    • Team workflows only run on meetings recorded by team members. They don’t apply to team admins or billing admins, so if you’re an admin, your own meetings won’t trigger a team workflow.

  • Confluence is still connected, and the connected Atlassian account can still create and edit pages in that Space.

  • The page you picked still exists. If it was deleted or moved, the workflow fails. Edit the workflow and choose the page again.

  • The page isn’t too large. Very long pages, especially ones that receive every meeting under the same name, can hit Confluence’s size limit, and the workflow fails. Start a new page or include the meeting date in the page name.

  • On the Free plan: you haven’t used up your integration limit. Free accounts can send up to 20 meetings in total to integrations. This limit is shared with Zapier and doesn’t reset. When it runs out, workflows stop without showing an error. Paid plans have no limit.

The notes section on my Confluence page is empty

This happens when AI Notes are turned off for the meeting or your AI credits have run out. The workflow still runs, but the notes section is sent blank.

If you still need support, please reach out to us at support@tldv.io and include:

  • The link to the meeting that didn’t reach Confluence. If several meetings are affected, send a few examples.

  • The email address of the person who recorded the meeting.

  • The name of the workflow that should have run, and whether it’s an individual or team workflow.

  • A screenshot of the workflow’s setup, including its conditions and action settings.

  • The name of the Confluence Space and page you expected the content in.

Common questions

Can I send meetings I recorded before setting up the workflow?
Workflows only run on new recordings. To send an older meeting, open it and use Trigger now.

If the meeting notes change later, does the Confluence page update?
No. The content is sent once, when the recording is ready. Later changes to the notes aren’t sent to Confluence.

Will tl;dv overwrite what’s already on my page?
No. tl;dv always adds content to the end of the page and never replaces what’s already there.

How do I get one page per meeting instead of one long page?
Include the meeting title and date in the Page name. A fixed page name sends every meeting to the same page.

Can I send different meetings to different Spaces?
Yes. Create a separate workflow for each Space and use Conditions to scope it. For example, one workflow for meetings with “Planning” in the title, and another for external customer calls.

Which plans include the Confluence integration?
Individual workflows are available on all plans. Trigger now requires the Pro plan or above. Team workflows and custom prompts require the Business plan or above.

Did this answer your question?