Appwrite - Event

Node catalog Triggers

On this page

Receive Appwrite events through a signed webhook.

Usage and specifics

Choose the Appwrite project, TablesDB or Databases API and resource identifiers. Key permissions restrict reads, writes and functions. For triggers, publish and configure the Appwrite webhook and events; a test payload does not verify delivery.

Technical type : appwrite_trigger. Runtime : nodulz.

Credentials and prerequisites

Appwrite - Webhook (integration / appwrite_webhook). Appwrite webhook HMAC signing key, separate from the API key.

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 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`	`["*"]`	-; min 1, max 100
`testPayload`	`string`	`""`	-

Configuration help

events Events: Comma-separated events; * accepts everything. Example: tablesdb..tables..rows..create or users..create. Subscribe to these events in Appwrite too. Filtering uses X-Appwrite-Webhook-Events.

Initial configuration

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

json

{
  "credentialId": "",
  "events": [
    "*"
  ],
  "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.