Extensions
An extension is a reusable, versioned unit of functionality — most often a single external API call — that a rule invokes through the Extension action without anyone having to wire up the request by hand.
What an extension is
Each extension packages everything needed to make one call: the HTTP method and URL, query and header values, authentication, an optional request body, the inputs a caller supplies per call, and the outputs returned to the rule set. Authors declare this once; consumers simply pick the extension and provide inputs. Extensions are run from the Extension action, one of the integration actions.
Versions and version history
An extension has a stable identity plus an ordered list of versions. Publishing creates a new version while leaving earlier ones intact, so consumers are never broken by an author's later changes. The detail view lists every version, and you can open any single version to inspect its configuration before adopting it. A version you depend on keeps working even after newer versions ship.
Only published versions are available to consumers. Authors work against a draft and publish when a version is ready; the latest published version is what new consumers see first.
Browsing and selecting
Use the in-app extension browser to search and sort the catalog, then open an extension to read its description, category, and version history. Signed-in users can like, favorite, or flag an item, and opening a detail page records a view — these signals drive the popularity sort.
When you are building a rule, the extension selector lets you choose an extension and a specific version to attach to an Extension action. From that point the rule calls the extension whenever it runs.
Managed parameters
Extensions never embed secrets. Anything sensitive — an API key, OAuth client credentials — is declared as a managed parameter. When your organization adopts an extension, you map each managed parameter to one of your environment variables, so the secret stays in your environment and the same extension works across organizations.
Terms of use
Some extensions call third-party services with their own terms. Before an extension is used, the application surfaces a terms-of-use acknowledgement so the consuming organization accepts responsibility for how the underlying API is called and billed.
Want to publish an extension instead of just consuming one? See Authoring Extensions for the build-and-publish flow.