Create a task for each incident
When an incident is opened in PagerDuty, create a task in LimbleCMMS and assign it to the owning team.
See all LimbleCMMS + PagerDuty 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.
LimbleCMMS Explore LimbleCMMS →
TriggersFires when a new task, job or item is created in LimbleCMMS.
Fires when a task in LimbleCMMS is marked complete.
Fires when a task's due date in LimbleCMMS is coming up.
Fires when a task, job or project changes status in LimbleCMMS.
Creates a new task, job or item in LimbleCMMS.
Updates a task's status or assignee in LimbleCMMS.
Posts a comment on a task in LimbleCMMS.
Assigns a task in LimbleCMMS to a team member.
PagerDuty Explore PagerDuty →
TriggersFires when a monitor or check in PagerDuty raises an alert.
Fires when an incident is opened or updated in PagerDuty.
Fires when a monitored site, service or alarm in PagerDuty changes state.
Opens a new incident or alert in PagerDuty.
Acknowledges an open incident in PagerDuty.
Resolves an incident in PagerDuty.
More LimbleCMMS + PagerDuty workflows
See all LimbleCMMS + PagerDuty integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create a task for each incident” between LimbleCMMS and PagerDuty?
Yes — describe it in the box above and Knit's Integrations Agent researches LimbleCMMS and PagerDuty'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 send incidents to a project management tool?
The alert is handled in PagerDuty, but the follow-up work lives in LimbleCMMS. Creating tasks automatically keeps that work visible and assigned.
Can I track action items from each incident?
Yes. When an incident is resolved in PagerDuty, create a task in LimbleCMMS for the review and any follow-up actions.