Search all guides

Reference · Credentials

Connect Discourse to BusyBot

Used by 1 BusyBot node.

Type discourseApi 3 fields

Fields

FieldTypeRequiredNotes
URL
url
string Yes Base URL of your Discourse instance (e.g., https://forum.example.com).
API Key
apiKey
password Yes Discourse API key. Generate from Admin > API Keys.
Username
username
string Yes Username associated with the API key.

Setting up Discourse API

  1. In Discourse API, create the credential this connection needs — the values listed in the table above. These are issued from your own Discourse API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Discourse API.
  3. Paste each value into the matching field and save.
  4. Add the Discourse node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Discourse credentials?

One node: Discourse. Create the credential once and select it in that node.

What does a Discourse credential need?

3 fields: URL, API Key, Username. Required: URL, API Key, Username. The values come from your own Discourse account.

How are Discourse secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use Discourse API

One credential works across every node below — create it once and reuse it.