Mark deployments in monitoring
When a deployment finishes in GitLab, record it in Dotcom Monitor so alerts can be read against it.
See all Dotcom Monitor + GitLab 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.
GitLab Explore GitLab →
TriggersFires when a job, build or file conversion finishes in GitLab.
Fires when a job, build or API request fails in GitLab.
Calls an GitLab endpoint with data from an earlier step.
Creates a PDF, image or converted file with GitLab.
Checks or enriches a phone number, address or IP with GitLab.
More Dotcom Monitor + GitLab workflows
See all Dotcom Monitor + GitLab integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Mark deployments in monitoring” between Dotcom Monitor and GitLab?
Yes — describe it in the box above and Knit's Integrations Agent researches Dotcom Monitor and GitLab'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 connect developer tools to a monitoring tool?
Most incidents follow a change. Linking GitLab and Dotcom Monitor lets engineers see what was deployed around the time an alert fired, and turn an incident into tracked work.
Can an incident create an issue for the engineering team?
Yes. When an incident opens in Dotcom Monitor, you can create an issue in GitLab so the fix is tracked alongside the code.