maintainx-webhooks-events
Guides the implementation of MaintainX webhook handlers for real-time event-driven integrations.
Install
mkdir -p .claude/skills/maintainx-webhooks-events && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5502" && unzip -o skill.zip -d .claude/skills/maintainx-webhooks-events && rm skill.zipInstalls to .claude/skills/maintainx-webhooks-events
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement MaintainX webhook handling and event-driven integrations.Key capabilities
- →Register MaintainX webhooks for specific events
- →Set up an Express-based webhook receiver with signature verification
- →Route incoming webhook events to type-specific handlers
- →Implement idempotency to prevent duplicate event processing
- →Manage webhooks by listing and deleting them via API
How it works
This skill enables real-time integrations by registering webhooks with MaintainX to receive event notifications. An Express server then receives, verifies, and routes these events to specific handlers, ensuring idempotency.
Inputs & outputs
When to use maintainx-webhooks-events
- →Implement MaintainX webhooks
- →Handle real-time work order events
- →Build notification integrations
- →Verify webhook event signatures
About this skill
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_KEYenvironment variable configured
Instructions
Step 1: Register 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://your-app.example.com/webhooks/maintainx",
"events": [
"workorder.created",
"workorder.updated",
"workorder.status_changed",
"workorder.completed"
]
}'
Step 2: Webhook Receiver (Express)
// 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
// 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
// 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
# 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
# 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 not firing | URL not reachable | Ensure HTTPS, check firewall, test with ngrok |
| Duplicate events | Retries from MaintainX | Implement idempotency with event ID deduplication |
| Signature mismatch | Wrong secret or body mutation | Verify raw body is used for HMAC, check secret value |
Resources
- MaintainX API Reference
- ngrok Documentation
- Webhook Security Best Practices
Next Steps
For performance optimization, see maintainx-performance-tuning.
Examples
Slack notification on high-priority work orders:
async function sendSlackAlert(message: string) {
await fetch(process.env.SLACK_WEBHOOK_URL!, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
text: `:rotating_light: MaintainX Alert: ${message}`,
}),
});
}
Polling fallback when webhooks are unavailable:
// Poll every 60 seconds for status changes
async function pollWorkOrders(client: MaintainXClient, since: string) {
const { workOrders } = await client.getWorkOrders({
updatedAtGte: since,
limit: 50,
});
for (const wo of workOrders) {
await routeEvent('workorder.updated', wo);
}
return new Date().toISOString();
}
When not to use it
- →When the webhook URL is not reachable from the internet
- →When the raw request body is not used for HMAC signature verification
- →When the webhook secret value is incorrect
Prerequisites
Limitations
- →Invalid API key can cause 401 on webhook registration
- →Webhook not firing if URL is not reachable
- →Signature mismatch if wrong secret or body mutation occurs
How it compares
This skill provides real-time event-driven integration with MaintainX using webhooks, which is more immediate and efficient than periodic polling for changes.
Compared to similar skills
maintainx-webhooks-events side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| maintainx-webhooks-events (this skill) | 1 | 26d | Caution | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| playwright-browser-automation | 29 | 7mo | Review | Intermediate |
| workflow-orchestration-patterns | 10 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
workflow-orchestration-patterns
wshobson
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
bullmq-specialist
davila7
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.