get_workflows
get_workflows
Live server: available on mcp.solvimon.com as well as on the test server.
Read-only access to workflows and what they did. A workflow is an automation rule that watches for an event and runs actions in response. For example, when an invoice becomes overdue, a workflow emails the customer or pushes data to an ERP.
Actions: list, get, search
Resource types: workflows, workflow_actions, workflow_triggers, workflow_executions (get and search only)
- A trigger only says the workflow matched an event. The execution says what happened:
SUCCEEDED,FAILED(with the reason),PENDINGorNOT_EXECUTED(its conditions didn’t hold). - Execution search needs at least one id filter, such as a customer, invoice or workflow.
- Workflow search takes
typeandstatusfilters only.
Only ACTIVE workflows and actions run. DRAFT configuration never fires.
Example prompts
- “Which reminders and emails do we send customers automatically?”
- “Did the overdue reminder go out for invoice INV-2026-10-000044?”
- “Why didn’t Acme Inc. get a low-balance email?”
- “Which workflow runs failed for Acme Inc., and why?”
Example output
Prompt: “Which reminders and emails do we send customers automatically?”
Tool call:
Response (trimmed):
Claude’s answer: None right now. Six workflows are set up (final invoice email, overdue reminder after 7 days, failed payment, upcoming payment, trial ending and low wallet balance), but all are DRAFT, so none of them fires. Activate the ones you want in Desk.