MCP server
send_slack_test_message
Posts a sample lead message (marked [Test Notification]) to a Slack channel so you can see how it looks.
Send a Slack test message · Changes data · Acts outside your account
Posts a sample lead message (marked [Test Notification]) to a Slack channel so you can see how it looks. It is a real Slack message. Without channelName it uses the channel of the first active Slack automation. Answers { success, channel } plus unknownFields when the template uses merge fields that don't exist; when Slack refuses (channel not found, app not invited to it, archived) it answers 400 with the reason and slackError.
| Connection | Account URL, team member URL or OAuth |
|---|
Parameters
| Parameter | Type | Required | Accepts | Description |
|---|---|---|---|---|
websiteId | string | Yes | any | Website ID from list_websites. |
channelName | string | No | any | Channel name from list_slack_channels, e.g. leads. Optional: defaults to the channel of the first active Slack automation. |
template | string | No | any | Optional template to try instead of the saved one. |
Tool definition
What your assistant receives from tools/list:
{
"name": "send_slack_test_message",
"title": "Send a Slack test message",
"annotations": {
"title": "Send a Slack test message",
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false,
"openWorldHint": true
},
"inputSchema": {
"type": "object",
"properties": {
"websiteId": {
"type": "string",
"description": "Website ID from list_websites."
},
"channelName": {
"type": "string",
"description": "Channel name from list_slack_channels, e.g. leads. Optional: defaults to the channel of the first active Slack automation."
},
"template": {
"type": "string",
"description": "Optional template to try instead of the saved one."
}
},
"required": [
"websiteId"
]
}
}