Maintainx Webhooks EventsSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: maintainx-webhooks-events description: 'Implement MaintainX webhook handling and event-driven integrations. Use when setting up webhooks, handling MaintainX events, or building real-time integrations with MaintainX. Trigger with phrases like "maintainx webhook", "maintainx events", "maintainx notifications", "maintainx real-time", "maintainx triggers". ' allowed-tools: Read, Write, Edit, Bash(curl:*), Bash(npm:*) version: 1.11.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - maintainx - webhooks compatibility: Designed for Claude Code --- # MaintainX Webhooks & Events ## Overview Build real-time integrations with MaintainX using webhooks for work order updates, asset changes, and maintenance notifications. MaintainX fires webhook events when key resources change. ## Prerequisites - MaintainX account with API access - HTTPS endpoint accessible from the internet (ngrok for local dev) - `MAINTAINX_API_KEY` environment variable configured ## Instructions ### Step 1: Register a Webhook ```bash curl -X POST https://api.getmaintainx.com/v1/webhooks \ -H "Authorization: Bearer $MAINTAINX_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://your-app.example.com/webhooks/maintainx", "events": [ "workorder.created", "workorder.updated", "workorder.status_changed", "workorder.completed" ] }' ``` ### Step 2: Webhook Receiver (Express) ```typescript // src/webhook-server.ts import express from 'express'; import crypto from 'node:crypto'; const app = express(); app.use(express.json({ limit: '1mb' })); // Signature verification middleware function verifySignature(secret: string) { return (req: express.Request, res: express.Response, next: express.NextFunction) => { const signature = req.headers['x-maintainx-signature'] as string; if (!signature) { return res.status(401).json({ error: 'Missing signature header' }); } const expected = crypto .createHmac('sha256', secret) .update(JSON.stringify(req.body)) .digest('hex'); if (!crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))) { return res.status(401).json({ error: 'Invalid signature' }); } next(); }; } const WEBHOOK_SECRET = process.env.MAINTAINX_WEBHOOK_SECRET!; app.post( '/webhooks/maintainx', verifySignature(WEBHOOK_SECRET), async (req, res) => { const { event, data, timestamp } = req.body; console.log(`[${timestamp}] Event: ${event}, Resource ID: ${data.id}`); // Idempotency check const eventId = req.headers['x-maintainx-event-id'] as string; if (await isProcessed(eventId)) { return res.status(200).json({ status: 'already_processed' }); } try { await routeEvent(event, data); await markProcessed(eventId); res.status(200).json({ status: 'ok' }); } catch (err) { console.error('Webhook handler error:', err); res.status(500).json({ error: 'Processing failed' }); } }, ); app.listen(3000, () => console.log('Webhook server listening on :3000')); ``` ### Step 3: Event Router ```typescript // src/event-handlers.ts type EventHandler = (data: any) => Promise<void>; const handlers: Record<string, EventHandler> = { 'workorder.created': async (data) => { console.log(`New work order: #${data.id} "${data.title}"`); // Notify Slack, create ticket, etc. if (data.priority === 'HIGH') { await sendSlackAlert(`High priority WO created: ${data.title}`); } }, 'workorder.status_changed': async (data) => { console.log(`WO #${data.id}: ${data.previousStatus} → ${data.status}`); if (data.status === 'COMPLETED') { await syncCompletionToERP(data); } }, 'workorder.completed': async (data) => { console.log(`WO #${data.id} completed at ${data.completedAt}`); await generateCompletionReport(data); }, 'workorder.updated': async (data) => { await syncWorkOrderToDataWarehouse(data); }, }; export async function routeEvent(event: string, data: any) { const handler = handlers[event]; if (handler) { await handler(data); } else { console.warn(`Unhandled event type: ${event}`); } } ``` ### Step 4: Idempotency Store ```typescript // src/idempotency.ts // Use Redis in production; Map for dev/testing const processed = new Map<string, boolean>(); export async function isProcessed(eventId: string): Promise<boolean> { return processed.has(eventId); } export async function markProcessed(eventId: string): Promise<void> { processed.set(eventId, true); // In production: await redis.setex(`event:${eventId}`, 86400, '1'); } ``` ### Step 5: Local Development with ngrok ```bash # Start your webhook server npm run dev # In another terminal, expose it with ngrok ngrok http 3000 # Copy the https URL (e.g., https://abc123.ngrok-free.app) # Register the ngrok URL as a webhook curl -X POST https://api.getmaintainx.com/v1/webhooks \ -H "Authorization: Bearer $MAINTAINX_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://abc123.ngrok-free.app/webhooks/maintainx", "events": ["workorder.created", "workorder.status_changed"] }' ``` ### Step 6: List and Manage Webhooks ```bash # List all registered webhooks curl -s https://api.getmaintainx.com/v1/webhooks \ -H "Authorization: Bearer $MAINTAINX_API_KEY" | jq . # Delete a webhook (replace ID) curl -X DELETE https://api.getmaintainx.com/v1/webhooks/456 \ -H "Authorization: Bearer $MAINTAINX_API_KEY" ``` ## Output - Webhook endpoint with HMAC signature verification - Event router dispatching to type-specific handlers - Idempotency guard preventing duplicate processing - Local dev setup with ngrok for testing webhooks - Webhook registration and management via REST API ## Error Handling | Issue | Cause | Solution | |-------|-------|----------| | 401 on webhook registration | Invalid API key | Verify `MAINTAINX_API_KEY` | | Webhook n
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__maintainx-webhooks-events.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Maintainx Webhooks Events skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Maintainx Webhooks Events safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Maintainx Webhooks Events access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Maintainx Webhooks Events work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.