Create Webhook

taiga.create_webhook
ActionBusiness appsconnection required

Calls the Taiga API with the connection's credentials.

Point a project's webhook at a URL so Taiga posts its events there.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Taiga
Secret shape
the Taiga auth token as {"auth_token": "…"}, or {"username": "…", "password": "…"} to log in with
Config it needs
base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project
Id of the Taiga project. This is the numeric primary key, not the project slug.
integerYes—≥ 11
name
A display name for the webhook, shown in the project's settings.
stringYes——Mantle workflow
url
The URL Taiga posts each event payload to, such as a Mantle webhook trigger's ingress URL.
stringYes—url formathttps://example.com/hooks/taiga
key
The shared secret Taiga signs each payload with, so the receiver can verify the request really came from this instance.
stringYes—credential materialcredential

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "name": "Mantle workflow",
  "project": 1,
  "url": "https://example.com/hooks/taiga"
}

Output

One shape.

result

FieldTypeExample
id
Taiga's internal primary key for the webhook.
number—
project
Id of the project the webhook watches.
number—
name
The webhook's display name.
string—
url
The payload URL Taiga posts each event to.
string—
key
The shared secret Taiga signs each payload with.
string—
logs_counter
How many deliveries Taiga has recorded for it.
number—
{
  "id": 0,
  "key": "",
  "logs_counter": 0,
  "name": "",
  "project": 0,
  "url": ""
}

See Create Webhook run in a workflow.

In a technical demo we add the Taiga connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.