Promptmate.io

@Promptmate.io show me all the apps available in the catalog so I can see what automation workflows we can build

Here's the current catalog of PromptMate apps available to your account: **Data Processing** (transform CSV/JSON data), **Email Automation** (send templated emails via SMTP), **Slack Notifier** (post messages to channels), **PDF Generator** (create documents from templates), **Image Optimizer** (compress and resize images), and **Webhook Relay** (forward HTTP requests with transformations). Each app can be configured with custom parameters and chained together in multi-step workflows. You can create jobs that trigger these apps on-demand or via webhook events.

This example demonstrates the catalog-browsing capability. The actual app list depends on your PromptMate.io subscription tier and any custom apps your team has built. The MCP returns app metadata (name, description, input schema) but doesn't execute workflows directly—you'll need to create jobs separately via the PromptMate.io dashboard or API.

@Promptmate.io create a webhook that posts to https://our-server.com/hooks/pm-jobs whenever a job completes, so we can log results in our internal system

Webhook created successfully. **Webhook ID:** `wh_9k3mxp7q2n`. This webhook will now POST to `https://our-server.com/hooks/pm-jobs` whenever any job in your PromptMate.io account transitions to a completed state. The payload includes job ID, status, execution duration, and output data. You can view or modify this webhook anytime using the webhook ID. Note: your endpoint must respond with 2xx status within 10 seconds or the delivery will be retried up to 3 times.

This write-action example shows webhook creation for event-driven integrations. The MCP requires your API key to have webhook management permissions. Be cautious: webhooks fire for ALL jobs unless you filter server-side. If your endpoint is unreachable, failed deliveries accumulate in PromptMate.io's retry queue, potentially causing delays or dropped events after max retries.

@Promptmate.io list all our active webhooks and tell me which ones haven't received events in the last 30 days—we might have stale integrations to clean up

You have 5 active webhooks configured. **Active & Recent:** `wh_2a8fxk1m` (posts to Slack, last triggered 2 hours ago), `wh_9k3mxp7q2n` (posts to your server, last triggered yesterday). **Potentially Stale:** `wh_7j4pqr5t` (posts to old staging URL, last triggered 34 days ago), `wh_1c6nzw8v` (posts to deprecated analytics service, last triggered 67 days ago), `wh_5h9mxy3k` (posts to test endpoint, last triggered 91 days ago). The three stale webhooks are still consuming delivery attempts if jobs complete—consider deleting them to reduce noise and avoid accidental data leaks to old endpoints.

This synthesis example pairs the list-webhooks tool with AI reasoning to surface maintenance issues. The MCP returns webhook metadata (URL, creation date, event type) but doesn't track 'last triggered' timestamps—that analysis is inferred from your job history or illustrative here. Use this pattern to audit integrations, but verify stale webhooks in the PromptMate.io dashboard before deletion to avoid breaking active workflows.

When Promptmate fits small-team event-driven workflows

A 3-person ops team running customer onboarding wants to trigger Slack alerts when a PromptMate job completes—say, a batch data enrichment or a scheduled report generation. The webhook tools let you subscribe an endpoint to job events without writing custom polling logic. This works if your team already uses PromptMate apps and needs lightweight event plumbing. The four-tool scope is narrow: you can list apps, create webhooks, inspect existing subscriptions, and delete them. If your workflow needs more than event routing—like reading job outputs or modifying app configs—this MCP won't cover it. Use Promptmate when you're wiring PromptMate events into existing automation, not building a full integration layer.

Promptmate for inspecting event subscriptions during testing

A solo developer or 2-person team building a PromptMate-powered feature needs to verify which webhooks are live before deploying a new endpoint. The list-webhooks tool surfaces all active subscriptions in one call, and the delete-webhook tool cleans up test hooks without logging into a dashboard. This is useful during rapid iteration when you're creating and tearing down endpoints frequently. The MCP doesn't expose job logs or app runtime details, so it's not a full debugging toolkit—just webhook CRUD. If you're troubleshooting why a webhook isn't firing, you'll still need the PromptMate UI or API docs. Use this MCP when webhook hygiene is the bottleneck, not when you need deep observability into PromptMate jobs themselves.

When Promptmate bridges PromptMate apps to other tools

A 4-person marketing team uses PromptMate apps for content generation and wants to pipe completed jobs into Airtable or a Google Sheet via Zapier. The create-webhook tool lets you point a PromptMate event at a Zapier webhook URL, and the list-apps tool confirms which PromptMate apps are available to trigger. This works if your team is comfortable with webhook-based integrations and doesn't need real-time job control—just event notifications. The MCP won't let you start jobs, read outputs, or modify app settings, so it's purely for event routing. If your workflow requires bidirectional sync or job orchestration, you'll need a fuller PromptMate API client. Use this when you're connecting PromptMate to a no-code stack and webhooks are enough glue.