Native Slack alerts with Dust

Slack isn't an optional add-on — it's native

A striking difference from Claude Code: where Claude needs a separate Slack MCP connector to set up, a Dust agent is directly usable in Slack as soon as it's published. Mention it with @Dust in any channel where the bot is installed — no extra MCP-side configuration.

To have it post proactively (without being asked), combine:

1. A Trigger scheduled on the agent.
2. A Slack Workflow that triggers the agent and posts its reply to the chosen channel.

The limitation stays the same

Even with this native integration, the Spendesk MCP has no webhooks — the agent can't be notified in real time that an invoice arrived or a threshold was crossed. The "alert" still has the frequency of the Trigger that fires it, not push instantaneity. The difference from Claude isn't on this limitation (identical), but on how simple the delivery is: no separate connector to wire up.

Three real client needs, and how to cover them

Budget overrun alerts — the Spendesk MCP doesn't expose a get_budgets tool. What is possible: an approximation via spendesk_analyze_spend, comparing a period to a reference — useful to spot drift, not a formal budget control.

Filtered approval alerts (a Procurement need) — via get_requests, a Trigger can watch for requests pending for more than N days.

Missing invoice alerts (a CFO/AP need) — by cross-referencing get_purchase_orders and get_payables, or via spendesk_get_due_invoices.

What it looks like

The prompt to copy to get started

Add a Trigger to this agent: every [frequency — e.g. Monday at 9am], post a summary of [business need — e.g. invoices overdue by more than 15 days] to the Slack channel [#channel-name], based on [MCP tool — e.g. spendesk_get_due_invoices]. Include the total amount and the 3 most critical cases.

For CFOs: prefer a weekly digest over a daily one — easier to read, less quickly ignored.

For Procurement: always filter by cost center or minimum amount to avoid noise.

What to keep in mind

• The agent works in Slack with no connector to set up — that's the main difference from Claude.
• The alert keeps the Trigger's frequency, never true push instantaneity — the Spendesk MCP stays pull-only on every platform.
• "Budget vs actual" remains an approximation as long as get_budgets doesn't exist.

To learn to assess yourself what the MCP can and can't do for a given need: Using your agent as a thinking partner.