HTTP and Knowledge: Confluence Page Index Template

This Spojit template keeps a searchable index of your Confluence wiki by pulling space pages on a schedule and embedding them into a persistent Knowledge collection.

What It Builds

A Schedule trigger fires on a cron you set. Because Confluence does not have a native tile, the workflow uses the http connector to call the Confluence REST API and fetch the pages in a space. A Knowledge node in Embed mode then loads that content into a persistent collection, so your team can ask questions across the whole wiki using a later Knowledge Query node or any AI step.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every morning at 6am. Connect to the Confluence REST API and fetch all pages from our "Engineering" space, including their page title and body content. Embed each page into a persistent Knowledge collection called "confluence-wiki" so the whole space stays searchable through AI queries.

Connectors Used

Schedule trigger - runs the index refresh on a cron schedule in your timezone.
http - Miraxa connects to the Confluence REST API to fetch space pages and their content.
Knowledge - Embed mode loads the pages into a persistent, reusable collection.

Customize It

Swap the space key ("Engineering") for your own, change the 6am run time or cron frequency, and rename the collection. You can also narrow the fetch to pages updated since the last run, or add label filters so only tagged pages get indexed.

Tips

Confluence Cloud uses an API token plus your base URL: store these on the http connection so the prompt never carries credentials.
Re-embedding the same collection keeps it current; schedule it often enough that edits surface in search quickly.
Pair this index with a Knowledge Query node, or add a Response Schema for structured JSON answers.