Taiga
Manage Taiga issues and project webhooks on your own Taiga instance.
OCNORA ships 8 typed Taiga operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Taiga
- Authentication
- Bearer token
- Credential
- the Taiga auth token as {"auth_token": "…"}, or {"username": "…", "password": "…"} to log in with
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The account must be able to administer the project's webhooks — a member without that right can read issues and still fail to publish. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL the Taiga instance can reach, which for a self-hosted Taiga behind a firewall is the usual reason a registration succeeds and no delivery ever arrives.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Taiga
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 2
Read and search 3
Update 1
Delete and cancel 2
A sample Taiga workflow
- 1Eventtrigger.taiga_eventStart a run when something changes in a Taiga project — an issue, user story, task, sprint or wiki page.
- 2Get Issuetaiga.get_issueFetch one issue by its internal id.
- 3Create Issuetaiga.create_issueCreate an issue in a project.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Create IssueCreate an issue in a project.taiga.create_issue
- Create WebhookPoint a project's webhook at a URL so Taiga posts its events there.taiga.create_webhook
- Delete IssuePermanently delete an issue.taiga.delete_issue
- Delete WebhookRemove a webhook so Taiga stops posting its events.taiga.delete_webhook
- Get IssueFetch one issue by its internal id.taiga.get_issue
- List IssuesList a project's issues, with Taiga's own filters and ordering.taiga.list_issues
- List WebhooksList the webhooks configured on the instance or on one project.taiga.list_webhooks
- Update IssueChange one or more fields on an existing issue.taiga.update_issue
Taiga questions
- How does OCNORA authenticate with Taiga?
- With a stored Bearer token credential, shaped the Taiga auth token as {"auth_token": "…"}, or {"username": "…", "password": "…"} to log in with. A connection test can check it when you add it.
- What can I automate with Taiga?
- 8 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Taiga operation I need is not listed?
- Where Taiga has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Taiga?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Taiga calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Taiga workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.