None

Overview

A connector stores how RUNOS reaches a service: address and credentials. Workflows refer to it by name, so no secrets are in the workflow JSON, and a changed password is maintained in one place.

Auth type	For	Page
None	services without sign-in, or just shared values	this page
ApiKey	API keys, e.g. OpenAI, GitHub, Odoo, weather services	ApiKey
Basic	user name and password, e.g. SMTP servers, internal APIs, FTP	Basic
OAuth2	sign-in in the browser, e.g. Microsoft 365, Gmail	OAuth2

A connector of type None has no credentials. It stores only the Base URL and, under Advanced → Extra JSON, any values of your own, such as a client number or a region. Useful for public APIs and for values several workflows share.

Extra JSON is not encrypted

Only the API key, password, client secret and tokens are stored encrypted. A password therefore doesn’t belong in Extra JSON but in a connector of type Basic.

Share with other users

When several Windows users use a shared data folder, its owner can make any connector available to all users’ workflows with Share with the other users of this data folder. Without other users the box does not appear.

Create a connector

1. Open Connectors on the left and click New.
2. Choose Blank connector or a template.
3. Give it a Name without spaces, for example Weather. Workflows address the connector by this name.
4. Choose the Auth type, fill in the fields and click Save.

Test sends an authenticated request to the Base URL and shows the response. The status at the top shows Ready, Token expires soon, Token expired, Credentials missing or No authentication. Duplicate creates a copy, for example for a second mailbox.

Template	Auth type
Microsoft Outlook Mail, Outlook Contacts	OAuth2 (Microsoft Graph)
Azure Service Principal	OAuth2 client credentials
Gmail API	OAuth2 (Google)
GitHub, OpenAI, OpenWeatherMap	ApiKey
FTP Server, Internal REST API	Basic

Security

With Encrypt secrets (default) RUNOS stores API keys, passwords, client secret and tokens encrypted for the signed-in Windows user. Another user or another PC cannot read them; on a new PC you enter them again.

Caution

Deleting or renaming a connector breaks every workflow that uses it.

Structure

Under Use in a workflow RUNOS shows the placeholder and copies it on click:

{{connector.<Name>.<Field>}}

Field	Content	Auth type
BaseUrl	base URL	all
ExtraJson.<key>	own values from Extra JSON	all
ApiKey	API key	ApiKey
Username, Password	credentials	Basic
AccessToken	OAuth2 access token, renewed when needed	OAuth2

Extra JSON is a JSON object:

{ "Client": "4711", "Region": "eu" }

Example

Connector Weather, auth type None, base URL https://api.open-meteo.com/v1, Extra JSON { "Lat": "52.52", "Lon": "13.41" }:

{
  "Type": "HttpRequest",
  "Name": "GetWeather",
  "Parameters": {
    "Connector": "Weather",
    "Url": "/forecast",
    "QueryParameters": {
      "latitude": "{{connector.Weather.ExtraJson.Lat}}",
      "longitude": "{{connector.Weather.ExtraJson.Lon}}",
      "current_weather": "true"
    }
  }
}

If the location changes, you only adjust the connector; every workflow uses the new value on its next run.