Connections and credentials

Connections store the credentials an integration needs. A node’s connection parameter selects a saved connection; the graph keeps its reference rather than copying the credentials into each node.

Set up a connection#

Open the node’s Parameters and choose an existing connection or add one of the required kind. Telegram, HTTP, and Email use different connection settings. Complete the fields for the integration you are using, then select that connection on the node.

Before a workflow runs, Blokboard checks required connections. An unselected, missing, or disabled connection needs attention. Open the node named in the message and choose an available connection.

Match the runtime#

Choose a runtime that supports the integration. Email requires Desktop. HTTP in the browser can be blocked by browser network rules. See choose a runtime when a correctly configured connection still cannot reach its service.

Import your own bindings#

Portable workflows do not carry another person’s credentials or device connection bindings. After importing, choose your own connections for the nodes that require them. Read the example or article’s prerequisites to understand which service access is expected.

Keep public files free of private values#

Credential fields are only one place private data can exist. A literal HTTP header, request body, URL query, code block, or Global can contain a token or private value entered manually.

Review every such value before exporting or publishing. Replace private literals with configuration that the reader supplies. A public workflow file can be downloaded without signing in.

Wallet signing has its own access boundary. Continue with wallets and transaction safety.