Custom apps

When Pipory doesn't ship a dedicated node for a service you need, a custom app turns that service's API into a first-class palette node without waiting on a built-in integration.

Define an app

Open Custom Apps from the sidebar and create an app: a name, a base URL, and an auth type - none, an API key in a header you name, a bearer token, or basic auth. Then add endpoints: a method, a path (supporting {param} placeholders), and an optional Handlebars body template.

Import from OpenAPI

Instead of defining endpoints by hand, paste or upload an OpenAPI 3.x document. Pipory walks it and extracts a flat list of operations (method, path, summary) for you to pick from - the parser is intentionally forgiving, so a spec that's not perfectly well-formed still produces a best-effort operation list along with any warnings.

Using a custom app node

Every endpoint you define appears in the node palette under your app's name. Configuring one on the canvas looks like any other action node: fill in {param} values, optionally override the endpoint's stored body template, and the node calls out with your app's configured auth applied automatically. The result lands downstream the same way an HTTP Request node's does.

Related

• Node reference: Core Actions - the HTTP Request node a custom app node generalizes.
• Credentials - how a custom app's auth value is stored and encrypted.