Give your IT team fast answers from your knowledge base. This child workflow takes a question from a parent flow, searches Confluence, and returns a clean title, link, and short content snippet. It is ideal for chat based IT help where users want quick links and clear guidance.

The flow begins with an Execute Workflow Trigger that receives the query text from the parent. An HTTP Request node calls the Confluence search API with Basic Auth and a CQL query built from the incoming text. The response is parsed, then a Set node formats a single response field with the article title, the full URL, and a trimmed content preview. That payload is sent back to the parent to power a final reply or an AI step. This design reduces context switches, enforces a consistent answer format, and keeps links correct.

Setup is simple. You need Confluence Cloud, an API token, and access to n8n. Replace the Confluence domain, confirm the CQL query, and test with a common IT term like password reset. Teams can expect faster resolution, fewer escalations, and less manual searching. Great for topics like account access, VPN setup, device policies, and software install guides.

• Receives the user question through an Execute Workflow Trigger from the parent flow
• Calls the Confluence search API using an HTTP Request with Basic Auth
• Builds the CQL query from the incoming JSON field so the search matches the question
• Parses the JSON reply and assembles title, link, and content preview
• Formats a single response field with consistent structure for the parent to consume
• Swap to another knowledge base by changing the HTTP Request endpoint and query

• Reduce manual search time from several minutes to under one minute
• Streamline IT question handling by returning a ready to send title, link, and summary
• Improve answer accuracy by sharing the exact Confluence article link
• Handle more simultaneous requests because search runs without human steps
• Connect your chat workflow to Confluence through a single, reusable child flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Atlassian Confluence. See the Tools Required section above for links to create accounts with these services.
3. In your Atlassian account, create a Confluence API token. Go to your account settings, open the API tokens page, and generate a new token. Copy it and keep it secure.
4. In the n8n credentials manager, create a new HTTP Basic Auth credential. Use your Atlassian email as the username and paste the Confluence API token as the password. Give the credential a clear name.
5. Open the Query Confluence node. In Credential to connect with, select your new HTTP Basic Auth credential.
6. Set the URL to your Confluence Cloud domain, for example https://your-domain.atlassian.net/wiki/rest/api/search. Keep the Accept header as application/json.
7. In Query Parameters, set cql to an expression that uses the incoming query. Example: text ~ "{{ $json.query }}". Save the node.
8. Open the Return Tool Response node. Confirm the expressions map the first result fields correctly, such as title and the full link built from _links.base and the result web path.
9. Quick test option: temporarily replace the cql expression with a fixed term like text ~ "password reset" and click Execute Node on the HTTP Request to verify results. Then restore the expression.
10. End to end test: run the parent flow that calls this child. Send a sample question and confirm a single response object returns with title, link, and content snippet.
11. Troubleshoot: if you see 401, check email and token. If results are empty, try a broader CQL like text ~ "VPN". If permissions errors appear, confirm the API user can read the target spaces.