pipefy-process-intelligence

Process Intelligence

Read the MCP reference or CLI reference for the surface you are using. Load only the relevant reference.

Analyze existing pipes for improvement opportunities and implement them progressively. Investigate immediately. Diagnose with data. Improve progressively.

---

When to use

The user asks to analyze or improve an existing process:

• "Analyze my pipe"
• "How can I improve this process?"
• "Is this pipe optimized?"
• "Where are the bottlenecks?"

Not for: designing a new process from scratch → use pipefy-process-design. Justifying a change with numbers, without implementing it → use pipefy-process-impact.

---

Prerequisites

• Pipe ID or name is known (or searchable via search_pipes).
• Read access to the pipe's cards and phase data.

---

Steps — investigation (Round 1)

1. Get pipe structure:

   Operation: get_pipe pipe_id=<id>

   Capture: phases, field count per phase, automation count.

2. Sample recent cards (last 30–50):

   Operation: get_cards pipe_id=<id> first=50 include_fields=true

   Look for: cards piling up in early phases, phases with 0 cards, fields left empty. get_cards selects no creation, update, or phase timestamps; the timed card read under the diagnosis framework does.

3. Check automations:

   Operation: get_automations pipe_id=<id>

   Look for: phases with no automations (manual handoffs), repeated manual steps.

4. Check AI configuration:

   Operation: get_ai_agents repo_uuid=<PIPE_UUID>

   For each active agent (disabledAt is null), read its behaviors to see which phases it already acts on:

   Operation: get_ai_agent uuid=<AGENT_UUID>

   Look for: no AI agents despite manual categorization or triage patterns, and hops an active behavior already covers (do not report those as manual).

---

Diagnosis framework

Time-based signals need dates that get_pipe and get_cards do not return. Per-card signals (stuck in a phase for more than 7 days, no update in weeks) come from a timed card read: one execute_graphql query on the pipe's cards selecting updated_at, current_phase_age, and phases_history (firstTimeIn, lastTimeOut, duration in seconds per phase); the document is in the reference. It is a read with no confirmation, 25 cards per page (up to 50), so say how many cards the numbers come from.