Google Chat - event

Node catalog Triggers

On this page

Start on an authenticated Google Chat notification.

Usage and specifics

Use an action credential or a separate webhook credential according to the node. To receive events, publish and configure the HTTPS URL, events and permissions in the service. The test payload is a normalized event and does not validate connectivity. Output preserves the provider payload.

Technical type : google_chat_trigger. Runtime : nodulz.

Credentials and prerequisites

Google Chat - webhook (integration / google_chat_webhook). HTTPS audience and exact sender service account email shown in Google Chat API > Configuration. The Google OIDC token is verified.

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`	`[]`	-
`channelId`	`string`	`""`	-
`sender`	`string`	`""`	-
`ignoreBots`	`boolean`	`true`	-
`testPayload`	`string`	`""`	-

Configuration help

events Events: Leave empty to receive all supported events. Configure event subscriptions in the service too.
testPayload Test event (JSON): Optional. Normalized event with provider, event, eventId, channelId, sender, text, bot and payload. Empty: local example without calling the service.

Initial configuration

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

json

{
  "credentialId": "",
  "events": [],
  "channelId": "",
  "sender": "",
  "ignoreBots": true,
  "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.