Choose where Tenda's alerts go
choose_alertsDestructiveIdempotent
Use this when the user wants to change which Slack and Teams channels get Tenda's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and admins can change alerts. Needs a Tenda account and workspace. Not for connecting a channel (Tenda dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | "slack" or "teams" for that app's channels. Leave out app and channel for every channel. | |
| only | No | true when what's sent here should go only here: every other channel stops getting it. An app or channel the user didn't mention otherwise keeps its alerts. | |
| send | No | Alerts to turn on in those channels: "new_tenders" (new tenders that fit the company), "changes" (changes to tenders in the pipeline), "morning_summary" (the weekday morning summary), "bid_work" (bid work nobody has yet), or "all". | |
| stop | No | Alerts to turn off in those channels: "new_tenders" (new tenders that fit the company), "changes" (changes to tenders in the pipeline), "morning_summary" (the weekday morning summary), "bid_work" (bid work nobody has yet), or "all". A channel with no alerts stays connected, so the team can still ask Tenda there. | |
| channel | No | One channel, by its name: e.g. "bids" or "#bids" in Slack, or "General" in Teams. | |
| workspace | No | The Tenda workspace to use, by name, when the user is in more than one, e.g. "Northbridge Services". |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| link | No | ||
| summary | Yes | ||
| channels | No |