Basic · URL source
Anything with an address, rendered as what it actually is
With the URL source whatever your build publishes, your API returns or your repository serves over HTTP shows on the Confluence page as the diagram, table, document or spec it actually is. You learn one source and every macro in the pack takes it - all thirty-one of them.
You learn one source and it works for every macro
Some sources suit some formats: typed text is no way to deliver a spreadsheet, and a Miro board has nothing to fetch from a bucket. A URL is the exception - every macro takes one. Learn it once and it works for the CSV, the PlantUML diagram, the PDF and the OpenAPI spec alike, which makes it your natural default for anything a pipeline already publishes.
Your credentials never sit in the page
Protected endpoints take basic auth, a token or a bearer token - and what gets stored is a sealed, server-encrypted credential, not the password someone typed. Better still, an admin registers a named credential once - "Internal API", say - and page authors simply pick it from a list: they publish from the endpoint without ever being told the secret, and nobody pastes a token into a wiki page that is about to be shared with the whole company.
Your key opens one door, not all of them
A named credential can be pinned to the hosts it belongs to - a list of allowed URL prefixes - so the token minted for your internal API is usable against that API and nothing else. Whoever grants it decides where it reaches, which is the difference between handing out a key and handing out a key to one door. Even a credential typed into a single macro is sealed to your site and to the origin it was entered for. Custom headers ride along for the APIs that want something of their own.
You reach the servers only your readers can see
Some things are not reachable from the internet on purpose: the dashboard on the office network, the service behind the VPN. Tick "fetch directly from the browser" and the request comes from the reader's own machine instead of our backend - someone already inside the network - and the content never passes through us at all. The server has to allow cross-origin requests, and the direct route is for endpoints that need no credential.
URL is one of 13 places Macro Pack reads from
One app, one licence, one connection your admin sets up - and 12 more places a page can pull content from, whether that is a page attachment, a Git repository, an S3 bucket or your database.
See every source compared