# Pipefy Building

> Thin router for Pipefy build and configure asks: map user intent to the correct domain skill (pipes, automations, AI agents, iPaaS, portals, etc.). Use when the user wants to create, build, configure, or integrate something in Pipefy and you need to know which skill to open. Do not use this skill as a delivery playbook — if the user already has a building skill or a detailed build prompt, follow that for how to build; use this skill only for which Pipefy domain skill to read.

- Skill: `pipefy/pipefy-building` (Agent Skill)
- Install (CLI): `npx skillmds@latest add pipefy/pipefy-building`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pipefy/pipefy-building/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: pipefy (https://skillmd.com/u/pipefy)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pipefy/pipefy-building

---


# Pipefy Building (router)

Maps **what the user wants** to **which domain skill to read**. It does not teach create/update workflows — open the linked skill for that.

If the user already has a building skill or a detailed build prompt/spec, use that for *how to build*; use this skill for *which Pipefy skill to load*.

---

## When the user wants X → read skill Y

| User intent (examples) | Read |
|------------------------|------|
| Design / architecture / "help me structure this process" | [pipefy-process-design](../../process-design/pipefy-process-design/SKILL.md) (consulting only) |
| Pipes, phases, fields, labels, cards, field conditions | [pipefy-pipes-and-cards](../../pipes-and-cards/pipefy-pipes-and-cards/SKILL.md) |
| Traditional or AI automations (if/then, prompt-driven rules) | [pipefy-automations](../../automations/pipefy-automations/SKILL.md) |
| Conversational AI agents and behaviors | [pipefy-ai-agents](../../ai-agents/pipefy-ai-agents/SKILL.md) |
| External integration / integrate with Slack, Gmail, Sheets, or another app | [pipefy-ipaas](../../ipaas/pipefy-ipaas/SKILL.md) |
| Portals, pages, elements, sub-portals | [pipefy-portal-setup](../../portal-setup/pipefy-portal-setup/SKILL.md) |
| Members, email templates, inbox email, webhooks | [pipefy-members-email-webhooks](../../members-email-webhooks/pipefy-members-email-webhooks/SKILL.md) |
| Database tables and records | [pipefy-database-tables](../../database-tables/pipefy-database-tables/SKILL.md) |
| Pipe/card relations | [pipefy-relations](../../relations/pipefy-relations/SKILL.md) |
| Reports and exports | [pipefy-reports](../../reports/pipefy-reports/SKILL.md) |
| Logs, usage, credits, job exports | [pipefy-observability](../../observability/pipefy-observability/SKILL.md) |
| First-time toolkit setup | [pipefy-toolkit-setup](../../onboarding/pipefy-toolkit-setup/SKILL.md) |

**Do not re-teach domain workflows here — open the linked skill.**

---

## Product limits live in domain skills

Hard stops and quirks (phase connections UI-only, email template create/edit UI-only, incompatible automation event×action pairs, no automation action applies a label, verify-after-write, AI consent) are documented in the domain skills above; follow those contracts after routing.

## See also

- [pipefy-process-design](../../process-design/pipefy-process-design/SKILL.md) — consulting when the ask is design, not build.
- [skills/README.md](../../README.md) — full catalog.