Some organisations already have source systems that send data to URLs with paths they chose themselves, for example:
https://hie.example.org/central-server
These URLs are configured in many source systems, often managed by different teams or partners. In OpenFn, a channel’s URL currently includes an auto-generated ID:
https://app.openfn.org/channels/bb77a9a5-7e39-484e-adae-af4c48cc3f92
To route this traffic through an OpenFn Channel, every source system would need a completely new URL. That requires a lot of coordination across systems and teams.
Request: Let users set a custom name for a channel, used in the URL instead of the generated ID. Pointing existing systems at OpenFn would then only require changing the domain:
-
Ideal:
https://openfn-instance.org/central-server -
Also acceptable:
https://openfn-instance.org/channels/central-server
Keeping the /channels/ prefix is fine if it is needed. The important part is replacing the ID with a name the user chooses.
Path forwarding would work the same as it does now. For example, /channels/central-server/patients would forward to {destination-url}/patients.
Things to consider:
-
On shared instances like app.openfn.org, names would need to be unique so two organisations cannot claim the same one.
-
The generated ID could stay as the default, with the custom name as an optional setting.
See image attached for a suggested UI.
