Confluence actions setup

Use Confluence actions to let Glean Assistant and Agents search, create, and update content in Confluence Cloud including spaces, pages, and blog posts without leaving Glean.

With this setup, you can:

• Enable a Confluence action pack for a tenant.
• Authenticate using either a central Confluence OAuth app or a customer-managed OAuth app.
• Decide which agents and surfaces can use these actions.

Prerequisites

Before enabling Confluence actions:

• The Confluence datasource must be configured and successfully crawling content.
• You must be able to access the Glean Admin Console.
• Your Confluence admin can approve an OAuth app:
  • For central or custom OAuth, your Atlassian / Confluence admin must be able to create or approve an OAuth integration and grant the scopes shown in the Confluence Actions setup screen.

Setup instructions

Follow these steps to setup the Confluence action pack:

1. In Glean, go to Admin Console → Platform → Actions.

2. Click Add.

3. From the list in the Add pre‑set actions section, select Confluence Actions under Action templates.

4. In the Configuration tab:

   1. Add the Instance Name.
   note

   If you have multiple Confluence Cloud instances, create a separate action pack per datasource instance and name them accordingly, for example, Confluence Actions – Corp Wiki, Confluence Actions – Engineering.

   2. Select Datasource Instance to link this action to your Confluence instance.
   3. Configure authentication. Confluence actions use user OAuth so that actions run as the signed‑in user and respect their permissions. You can either use a central Glean‑managed app (recommended where available) or configure a custom OAuth app in Atlassian.

   Use the central option if:

   • Your organization is Glean‑hosted, and
   • Central apps are available for Confluence in your environment.

   Steps:

   1. Select Central under Authenticate sectionin on the Confluence Actions setup page.
   2. Click Save.

   End users are prompted to connect their Confluence account the first time they run an action, and tokens are managed centrally thereafter.

   Use the custom option if:

   • You are self‑hosted, or
   • Your security model requires a customer‑owned Atlassian OAuth app.

   Steps:

   In order to setup OAuth for Confluence actions, follow these steps:

   Step 1: Create a new OAuth app

   1. Navigate to the Atlassian Developer Console and create a new app of type: OAuth2.0 Integration.
   2. Follow the prompts to set up the app. Make a note of the app name, description, and logo.
   3. Click Save to create the OAuth app.
   4. Copy the Client ID.
   5. Copy the Client Secret.

   Step 2: Set permissions

   1. Go to the Permissions tab of your app configuration.
   2. Add Scopes. These scopes are available in the Confluence actions configuration page on the Glean admin console.

   Step 3: Update distribution settings

   1. Go to the Distribution tab of your app configuration in the Atlassian Developer Console.
   2. Click Edit.
   3. Change the Distribution Status to Sharing.
   4. Add a Privacy policy, you can use Glean privacy policy.
   5. Click Save Changes.

   Step 4: Fill the client ID and client secret

   1. Navigate to Confluence actions configuration page on the Glean admin console.
   2. Select custom under the Authenticate section.
   3. Add the Client ID and Client secret information.
   4. Click Save.
   5. Copy the Callback URL.

   Step 5: Configure the callback URL in your OAuth App

   1. Go to the Authorization tab of your app configuration on the Atlassian developer console.
   2. Paste the callback URL into the Callback URL field.
   3. Click Save your OAuth App.

5. Click Edit settings under Enable Actions section to make actions visible for all or some users within Glean Chat and Agents.