Messaging recipes for AI agents

Each recipe here lands a message where a human already looks. The agent writes the words; the credential, a bot token or a webhook URL, stays encrypted in the FlurryPORT secret store and is added server-side at delivery. Back comes a receipt with the provider's real answer.

They agree on little else. Slack reports a channel failure as 200 with ok:false in the body, so the receipt body outranks the status code. Discord's webhook URL is the whole credential and success is an empty 204. Telegram rides its bot token in the URL path. Teams retired classic webhooks and expects an Adaptive Card through a Power Automate workflow URL.

Pick the room your team reads; each recipe page's calculator shows how the install fits your plan.