DocsIntegrationsOverview

Integrations

An integration holds the token, password or address a workflow needs to reach another service. Set it up once in a workspace, test it, and pick it from any node.

Set one up

  1. In the console, open Integrations from the left rail and choose Add integration.
  2. Pick the service and give it a name you'll recognise in a node, like Family chat.
  3. Paste the token or sign-in. Secrets are encrypted at rest and never shown again, only replaced.
  4. Press Test. WBSKT sends a test message or makes a test call and tells you what came back.
  5. Pick the integration in any Email, Telegram, Discord, ntfy or Call a URL node.
Who can do thisViewing integrations needs integrations.read. Adding, changing or deleting one needs integrations.manage.

How secrets are kept

  • Tokens, passwords and webhook URLs are encrypted (AES-256-GCM) the moment you save them, tied to the workspace and to that one integration, so they can't be moved or read back.
  • The console only ever shows the last four characters, to tell which one is saved. To change a secret, replace it.
  • Each step fetches the integration fresh, so a replaced secret takes effect on the next step.
  • Error messages in the run history have secret values scrubbed out.
  • A credential for an HTTP API, or an ntfy or mail server, is only ever sent to the address it was saved with.

Deleting an integration

An integration that a published workflow uses can't be deleted. The console lists the workflows that use it so you can change them first.

Errors you might see

CodeStatusMeans
INTEGRATION_NAME_TAKEN409Another integration in this workspace has that name.
INTEGRATION_TYPE_INVALID400The service isn't one WBSKT supports.
INTEGRATION_NOT_FOUND404No integration with that reference in this workspace.
INTEGRATIONS_UNAVAILABLE503Integrations are briefly unavailable. Retry after the time in Retry-After.

Every code is on the Error codes page.