AI & researchAgentHTTP RequestOpenAI Chat ModelManual Chat TriggerMarkdown

🌐 Confluence Page AI Powered Chatbot

Configured with Agent, HTTP Request, OpenAI Chat Model, Manual Chat Trigger, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSON View files on GitHub ↗12 nodes · MIT

Workflow preview

Node categories in this workflow

Web / API
Transform
AI & models
Trigger
Data store
Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
Node	Category	Type	Operation
Confluence Page Storage View	Web / API	HTTP Request	See node parameters
HTML to Markdown	Transform	Markdown	See node parameters
gpt-4o-mini	AI & models	OpenAI Chat Model	See node parameters
When chat message received	Trigger	Manual Chat Trigger	See node parameters
Window Buffer Memory	Data store	Memory Buffer Window	See node parameters
Chat Response	Transform	Edit Fields	See node parameters
Globals	Transform	Edit Fields	See node parameters
Search By ID	Web / API	HTTP Request	See node parameters
Page Schema	Transform	Edit Fields	See node parameters
AI Agent	AI & models	Agent	See node parameters
Send Telegram Message	Messaging	Telegram	See node parameters
Split Out	Transform	Split Out	See node parameters

Setup

Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

httpHeaderAuth
openAiApi
telegramApi

Workflow notes

Confluence

https://developer.atlassian.com/cloud/confluence/basic-auth-for-rest-apis/ https://id.atlassian.com/manage-profile/security/api-tokens https://developer.atlassian.com/cloud/confluence/rest/v2/intro/#about

Supplying basic auth headers You can construct and send basic auth headers yourself, including a base64-encoded string that contains your Atlassian account email and API token.

To use basic auth headers, perform the following steps:

Generate an API Token for your Atlassian Account: https://id.atlassian.com/manage/api-tokens Build a string of the form user@example.com:your_user_api_token. You'll need to encode your authorization credentials to Base64 encoded. You can do this locally: Linux/Unix/MacOS:

Copy

echo -n user@example.com:your_user_api_token | base64

Windows 7 and later, using Microsoft Powershell:

Copy

$Text = ‘user@example.com:your_user_api_token’
$Bytes = [System.Text.Encoding]::UTF8.GetBytes($Text)
$EncodedText = [Convert]::ToBase64String($Bytes)
$EncodedText

Supply an Authorization header with content Basic followed by the encoded string. Example: Authorization: Basic eW91cl9lbWFpbEBkb21haW4uY29tOnlvdXJfdXNlcl9hcGlfdG9rZW4=

Copy

curl -D- \
   -X GET \
   -H "Authorization: Basic <your_encoded_string>" \
   -H "Content-Type: application/json" \
   "https://<your-domain.atlassian.net>/wiki/rest/api/space"

The above cURL command will not work as shown. You need to replace <your_encoded_string> and <your-domain.atlassian.net> with your authorization credentials encoded string and instance information before running it in the terminal.

Using Rest API to GET Confluence Page Body

https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-id-get

Request https://.atlassian.net/wiki/api/v2/pages/{id} Path parameters id integer

Required Query parameters

The content format types to be returned in the body field of the response. If available, the representation will be available under a response field of the same name under the body field.

Valid values: storage, atlas_doc_format, view, export_view, anonymous_export_view, styled_view, editor

🌐 Confluence Page AI Powered Chatbot

Purpose and structure

This folder contains the 🌐 Confluence Page AI Powered Chatbot workflow. Its executable nodes use agent, httpRequest, lmChatOpenAi, manualChatTrigger, markdown, memoryBufferWindow, set, splitOut, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When chat message received

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/1919_Telegram_Splitout_Automate_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

Chatbot for Confluence Pages
Confluence Search By ID

More in AI & research

"Hey Siri, Ask Agent" workflow #️⃣Nostr #damus AI Powered Reporting + Gmail + Telegram (G) - Email Classification