Claude workflow
Protect revenue at risk with Claude
Go through the accounts flagged at risk and plan one save action, with an owner and a date, for each.
What does this workflow do?
Claude reads the revenue at risk entries by exposed amount, then each company's recent activity and email to say what the risk really is. It proposes one concrete save action per account with an owner and a date, and creates the tasks after you confirm.
The prompt
Copy it into a chat with Lumenbase turned on. Fields in square brackets are yours to fill in.
Use the Lumenbase connector. 1. Call fetch_revenue_at_risk, sorted by exposed revenue. 2. For each account, read the company and its recent activities and email (fetch_companies, fetch_activities, fetch_mail_conversations) and say what the risk really is. 3. Propose one concrete save action per account with an owner and a date. 4. Create the tasks with create_task after I confirm.
Run it as /protect_revenue_at_risk in Claude.
Tools it calls
In the order the prompt uses them.
- List revenue at risk · Read
Fetch Revenue at Risk (RAR) entries: exposed revenue and likelihood by company for forecast and churn tracking.
What to check before you approve
- The stated reason for the risk matches what you know.
- Each save action has a named owner who can do it.
- Dates are close enough to matter.
Make it recurring
This job comes back every week. Ask Claude to turn it into a Routine and it runs in Lumenbase on its own schedule, as a draft you review and switch on.
Common questions
Sources and scope
The prompt and its tool list come from the Lumenbase MCP workflow catalog, the same list the connector serves.
Claude is a trademark of Anthropic. ChatGPT is a trademark of OpenAI. Cursor is a trademark of Anysphere. Lumenbase is not affiliated with, sponsored by or endorsed by these companies.
