Pneumatic

@pneumatic list all active workflows currently assigned to me and show their current task status

Based on your Pneumatic account, you have 4 active workflows assigned to you: 1. **Employee Onboarding - Sarah Chen** (started 3 days ago) — currently at task "IT Equipment Setup", waiting on your approval for laptop specs. 2. **Q1 Budget Review** (started 1 week ago) — at task "Department Manager Sign-off", due in 2 days. 3. **Customer Refund Request #8472** (started today) — at task "Finance Team Review", marked urgent by the requester. 4. **Content Approval - Blog Post Draft** (started 5 days ago) — at task "Final Editorial Review", includes 3 checklist items you haven't completed yet. This is an illustrative example showing how Pneumatic returns workflow state and task assignments for the authenticated user.

This example demonstrates read-only task discovery. The MCP requires API key authentication with read permissions on workflows and tasks. Results reflect the specific user's assignments at query time — teammates with different roles will see different active work. No side effects occur from listing workflows.

@pneumatic run the "New Hire Onboarding" template for candidate Alex Martinez, set urgency to high, and populate the start date field with next Monday

Workflow started successfully. I've launched the "New Hire Onboarding" template for Alex Martinez with the following configuration: - **Workflow ID**: WF-2847 - **Urgency**: High - **Start Date**: Monday, January 13, 2025 - **First Task**: "Send Welcome Email" — now assigned to HR team member Jamie Park, due within 24 hours. The workflow includes 8 tasks spanning IT setup, manager introduction, benefits enrollment, and first-week check-ins. You'll receive notifications as each task completes and moves to the next performer. This illustrative example shows how Pneumatic confirms workflow creation and surfaces initial task assignment.

This example demonstrates workflow execution — a write operation with immediate side effects. Running a template creates a new workflow instance, assigns tasks to real team members, and triggers notifications. Ensure you have permission to start workflows from the target template and that kickoff field names match the template's configuration exactly, or the run will fail.

@pneumatic get all tasks from the "Customer Support Escalation" workflow and draft a status summary email for the account owner

I've retrieved the "Customer Support Escalation" workflow (WF-2801) and found 5 tasks: 1. **Initial Triage** (completed 2 days ago by Support Agent) 2. **Engineering Investigation** (completed yesterday, flagged "bug confirmed") 3. **Fix Implementation** (completed this morning, deployed to staging) 4. **QA Validation** (in progress, assigned to QA team, due tonight) 5. **Customer Communication** (pending, will start after QA approval) **Draft email:** *Subject: Update on Your Support Escalation (Ticket #4729)* Hi [Account Owner], Our engineering team has confirmed and resolved the issue you reported. The fix is currently in QA validation and on track for production deployment tomorrow. We'll reach out within 24 hours once testing is complete to confirm resolution. This illustrative example shows how Pneumatic task data can feed AI-generated summaries.

This example pairs Pneumatic's workflow data retrieval with AI synthesis — the MCP fetches structured task history, then the AI drafts a summary. The draft is not sent automatically; you control whether to use it. Workflow visibility depends on your Pneumatic role permissions; you can only retrieve workflows you're authorized to view.

When Pneumatic beats spreadsheets for new-hire workflows

A 6-person agency hires 2-3 contractors per quarter and runs the same 12-step onboarding sequence every time: IT setup, contract signing, tool access, intro calls. Pneumatic wins here because Run Template kicks off the workflow with kickoff field values (name, role, start date) and routes tasks to the right performer automatically. Get Task shows each owner exactly what's due without digging through Slack threads. The trade-off: if your onboarding changes every hire or you need complex branching logic, Pneumatic's template model gets rigid fast. But for repeatable sequences under 20 steps where you want task-level accountability without building custom tooling, this MCP turns a 15-minute manual kickoff into a 30-second API call.

Using Pneumatic to surface workflow blockers in standups

A 4-person product studio runs 8-10 client projects concurrently, each following a discovery-design-build-launch template. List Workflows filtered by current performer surfaces which projects are waiting on a specific teammate, and Get Workflow pulls the current task and due date for status updates. The win: standup prep drops from 10 minutes of tab-switching to a single query showing who's holding what. The limit: Pneumatic doesn't aggregate cross-workflow metrics or flag patterns like 'design reviews always run 3 days late.' If you need rollup reporting or predictive insights, you're still exporting to a BI tool. For teams under 15 people running fewer than 20 active workflows, this MCP makes daily triage faster without adding a project manager.

When Pneumatic handles tier-2 handoffs better than email

A 9-person SaaS support team escalates 40-60 tickets per month from tier-1 to engineering or sales. They template the escalation as a 4-task workflow: triage, technical review, customer reply, close-out. Run Template creates the workflow with ticket ID and urgency as kickoff fields, and Get Task shows the engineer exactly what context tier-1 captured. The advantage: no more 'who's handling this?' Slack threads, and List Tasks gives each performer a clean queue. The boundary: if escalations need dynamic routing based on product area or SLA tier, Pneumatic's static task assignment gets clunky. For straightforward handoff sequences where the path is known upfront, this MCP turns ad-hoc escalation into a trackable process without heavyweight ticketing software.