# ClickUp events - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/clickup_trigger

Language: en

Start a workflow from provider webhook events.

## Usage and specifics

Choose the account, workspace or project and operation. Task and resource identifiers must belong to the authorized account. For a trigger, configure its mode and events, then publish the workflow. A simulated payload does not prove remote event delivery.

Technical type : `clickup_trigger`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Project management webhook secret](/docs/credentials) (`integration` / `project_webhook`). Dedicated secret for webhook signing or authentication

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `rateLimitEnabled` | `boolean` | - | - |
| `rateLimitMax` | `number` | - | -; > 0 |
| `rateLimitWindowMs` | `number` | - | -; > 0 |
| `allowedIps` | `array` | - | -; max 256 |
| `blockedIps` | `array` | - | -; max 256 |
| `credentialId` | `string` | `""` | - |
| `events` | `array` | `[]` | - |
| `resourceId` | `string` | `""` | - |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `events`<br>Events | An empty selection accepts all events. Register the webhook in the provider with the same event selection. |
| `testPayload`<br>Test payload (JSON) | Normalized event: provider, event, resourceId and payload. Leave empty to use an example. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "events": [],
  "resourceId": "",
  "testPayload": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)