Microsoft Teams · Trigger

Node catalog Triggers

On this page

Messages, cards and events received by a Teams bot.

Usage and specifics

Use a Teams bot credential and activity or conversation parameters. The trigger receives Bot Framework activities at its published URL. Replies reuse the incoming activity context.

Technical type : teams_trigger. Runtime : nodulz.

Credentials and prerequisites

Microsoft Teams bot (integration / teams_bot). Single-tenant Azure Bot: encrypted tenant, client ID and secret

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
`credentialId`	`string`	-	-
`events`	`array`	`["message"]`	-; min 1
`teamIds`	`array`	`[]`	-
`channelIds`	`array`	`[]`	-
`conversationIds`	`array`	`[]`	-
`userIds`	`array`	`[]`	-
`requireMention`	`boolean`	`false`	-
`ignoreBots`	`boolean`	`true`	-
`textContains`	`string`	`""`	-
`commandPrefix`	`string`	`""`	-
`invokeNames`	`array`	`[]`	-
`invokeResponse`	`string`	`""`	-
`testPayload`	`string`	`""`	-

Initial configuration

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

json

{
  "events": [
    "message"
  ],
  "teamIds": [],
  "channelIds": [],
  "conversationIds": [],
  "userIds": [],
  "requireMention": false,
  "ignoreBots": true,
  "textContains": "",
  "commandPrefix": "",
  "invokeNames": [],
  "invokeResponse": "",
  "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.