Automate CMDash with Zapier
Trigger workflows off CMDash risk, posture, compliance and integration events, or create and update CMDash risks from any of the 6,000+ apps Zapier connects to — no code, no webhook plumbing of your own.
Run the app privately
The CMDash Zapier app (9 triggers, one per outbound webhook event, and 3 actions against the public API) is built and tested. It runs privately: ask your CMDash contact for an invite to it on the Zapier CLI, or use the public API and outbound webhooks directly.
Recipes
Post new risks to a Slack channel
The moment a risk is registered in CMDash — by hand or by an integration sync — post it to a Slack channel so the team sees it without opening the dashboard.
Trigger: CMDash — New Risk Created · Action: Slack — Send Channel Message
- Trigger: CMDash — New Risk Created.
- Connect your CMDash account with an API key that has the webhooks:read/webhooks:write scopes.
- Action: Slack — Send Channel Message.
- Map the risk’s title, category and score into the Slack message text.
- Turn the Zap on — CMDash subscribes a webhook for risk.created automatically.
Page on-call when an integration sync fails
A failed sync (an expired credential, a rate limit, a vendor outage) should page someone, not sit unnoticed until the next dashboard visit.
Trigger: CMDash — Integration Sync Failed · Action: Slack — Send Direct Message
- Trigger: CMDash — Integration Sync Failed.
- Action: Slack — Send Direct Message (or swap in PagerDuty/Opsgenie’s own Zapier action).
- Map the integration provider and failure reason into the message.
- Turn the Zap on.
Turn a spreadsheet row into a CMDash risk
Keep a shared risk-intake spreadsheet (a security questionnaire response, an audit finding log) and have every new row become a tracked CMDash risk automatically.
Trigger: Google Sheets — New Spreadsheet Row · Action: CMDash — Create Risk
- Trigger: Google Sheets — New Spreadsheet Row.
- Action: CMDash — Create Risk.
- Map the row’s columns to Title, Category, Likelihood and Impact.
- Turn the Zap on — no CMDash webhook is created for this direction; Zapier polls the sheet.
Prefer n8n?
The same trigger and actions are also available as an n8n community node (n8n-nodes-cmdash) for teams running n8n instead of, or alongside, Zapier.
Building your own automation
Every event a Zapier trigger can fire on is documented in the outbound webhooks reference, including delivery guarantees, signature verification and replay. Every action a Zapier create can run is part of the same public API your own scripts can call directly.