blokboard/ Open app
Docs/Run safely

Run safely

Connections and credentials

Configure integration access without embedding credentials in the graph.

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.

Telegram bot#

  1. Open the official @BotFather in Telegram. Send /newbot, choose a display name and an available bot username, and copy the token it provides. Telegram’s bot guide explains bot creation and token management.
  2. In Blokboard, add a Telegram node. Open its connection selector and choose Add Telegram bot. Give it a Connection name and paste the token into Bot token. Blokboard verifies the token before saving.
  3. Open your new bot’s private chat in Telegram and press Start. A bot needs an accessible destination before it can send to you.
  4. To find your chat ID without putting the token in a URL, build Start → Message received → Variable. Select your bot connection on Message received, leave Only this chat empty, and run. Send a new message to the bot while the workflow is listening.
  5. Inspect Message received’s output and copy chat.id, including any minus sign. Stop this discovery workflow. Enter that ID in Chat ID on Send message, or in the example’s chatId Global.
  6. Select the same connection on Send message, enter a short message, and run once. Then import Pump launch alerts or the wallet report.

For a group, add the bot and send a command addressed to it while the discovery workflow is listening. Group privacy settings affect which messages the bot receives. For a public channel, give the bot permission to post and use its @channelusername as the destination. See Telegram’s bot FAQ.

Use one incoming-message consumer for a bot during discovery. Telegram does not allow getUpdates while a webhook is configured; a bot previously connected to another service may need that service disconnected first. Sending outgoing alerts does not require a Message received node to stay running.

Keep tokens in the saved connection, never in Globals, CSV files, scripts, or screenshots. A chat ID identifies the destination; it is not the bot token. Revoke an exposed token through BotFather and update the saved connection.

Email and SMTP#

  1. Connect Desktop and choose it as the execution runtime. Your browser can store connection settings, but SMTP delivery runs in Desktop.
  2. Add an Email node and choose Add email account from its connection selector. Enter Connection name, Email address, optional From name, SMTP host, Port, SMTP username, and SMTP password using your mail provider’s settings.
  3. Match the transport to the provider: port 465 normally uses Use direct TLS checked; port 587 normally leaves that option unchecked and upgrades with STARTTLS. Follow the provider’s actual configuration. SMTP transport settings explain this distinction.
  4. Some providers require an app password or administrator-enabled SMTP access. For Gmail accounts that support app passwords, consult Google’s instructions. This connection form uses SMTP credentials; it does not perform a Google OAuth sign-in.
  5. Save, then select the connection on Email. Set To to an address you control, add a Subject and Text body, and run Start → Email once. Inspect accepted, rejected, and messageId.
  6. For an attachment, connect Write CSV’s file output to Email’s input. The email node reads the file reference from its incoming value. The Raydium pool report demonstrates this end to end.

Authentication failures point to account credentials or provider policy. A connection timeout can indicate the host, port, firewall, or runtime. An accepted message can still land in spam; inspect the recipient mailbox before assuming delivery is complete.

Solana RPC#

Choose the intended Solana network and RPC route in runtime settings. Public wallet reports need only public addresses; transactions also need a signing wallet. The practical Pump and Raydium examples use mainnet and declare that in their prerequisites. Test mode changes chain selection; it does not simulate mainnet integrations.

For watchers, the route must support WebSocket subscriptions as well as HTTP reads. First test SOL balance against an address on the selected network, then test a watcher. An HTTP read succeeding does not prove that subscriptions are available. Keep credentials in the connection or runtime configuration, not in a shared workflow file.

Ethereum RPC#

Choose Cloud RPC and use the workflow’s Test mode switch to choose test or live data. No provider account or API key is needed for Cloud RPC. Start with Ethereum reads for the supported nodes, a downloadable example, and expected results. See Cloud RPC credits for request costs and busy-service errors.

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.