BusyBot

Reference · Credentials

Taiga API credentials

Used by 2 BusyBot nodes.

Type taigaApi 4 fields

The Taiga credential authenticates with your Taiga account username and password, plus a switch for cloud or self-hosted. Because it uses a real account login, prefer a dedicated automation user over your own.

Fields

FieldTypeRequiredNotes
Username
username		 string Yes Your Taiga account username
Password
password		 password Yes Your Taiga account password
Environment
environment		 string No "cloud" or "selfHosted"
URL
url		 string No Self-hosted Taiga instance URL.

Getting your credentials

  1. Use the username and password of a Taiga account with access to the relevant projects.
  2. Set Environment to cloud for Taiga’s hosted service, or selfHosted for your own installation.
  3. For a self-hosted instance, set URL to its base URL. Cloud installations do not need it.

Create a dedicated Taiga user for automation rather than reusing a personal login — it keeps activity attributable and lets you revoke access without changing your own password.

Permissions and scopes

The credential acts as that Taiga user, with exactly the project memberships and role permissions it holds. A user with no membership on a project cannot see it through the API either.

Troubleshooting

  • 401 Unauthorized — wrong username or password, or the account is on a different instance than the URL points at.
  • Connection refused on self-hosted — the URL is wrong, or the instance is unreachable from the workflow environment.
  • 404 on a project — the account is not a member of it.

Frequently asked questions

Why does it want a password rather than a token?

Taiga authenticates this integration with account credentials. Use a dedicated automation account so activity stays attributable and access can be revoked without touching your own login.

What do I set for self-hosted Taiga?

Environment to `selfHosted` and URL to your instance's base URL. The cloud service needs neither.

Why can the workflow not see a project?

The account behind the credential is not a member of it. Project membership and role permissions apply exactly as they do in the interface.

Nodes that use Taiga API

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

Last updated . Spotted something wrong? Tell us.