Flag key accounts during an outage
When Dotcom Monitor raises a critical alert, tag the related accounts in Pipedrive so the team can prioritize outreach.
See all Dotcom Monitor + Pipedrive integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Dotcom Monitor Explore Dotcom Monitor →
TriggersFires when a monitor or check in Dotcom Monitor raises an alert.
Fires when an incident is opened or updated in Dotcom Monitor.
Fires when a monitored site, service or alarm in Dotcom Monitor changes state.
Opens a new incident or alert in Dotcom Monitor.
Acknowledges an open incident in Dotcom Monitor.
Resolves an incident in Dotcom Monitor.
Pipedrive Explore Pipedrive →
TriggersFires when a new contact or lead is added to Pipedrive.
Fires when a field on a contact changes in Pipedrive.
Fires when a deal, case or record moves to a new stage in Pipedrive.
Fires when a deal is marked won in Pipedrive.
Creates or updates a contact in Pipedrive.
Creates a new deal in Pipedrive.
Moves a deal or record to a new stage in Pipedrive.
Logs a call, email, or note against a record in Pipedrive.
More Dotcom Monitor + Pipedrive workflows
See all Dotcom Monitor + Pipedrive integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Flag key accounts during an outage” between Dotcom Monitor and Pipedrive?
Yes — describe it in the box above and Knit's Integrations Agent researches Dotcom Monitor and Pipedrive's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why link incident alerts to a CRM?
When Dotcom Monitor opens an incident, the accounts affected by it matter to sales and success teams. Recording it in Pipedrive gives them the context without watching an on-call tool.
Can I notify account owners about incidents?
Yes. When an incident opens or is resolved in Dotcom Monitor, you can create a task or note in Pipedrive for the owner of each affected account.