@pipefy/pipefy-process-coder 0.1.0 → 0.1.2

package/.agents/skills/ppc-pipefy-flow-authoring/examples/README.md

@@ -1,42 +1,42 @@
-# Reference flows
-
-Thirteen real flows from a production trade-finance integration, sanitized
-before being added here — every company name, personal name, email, CNPJ,
-phone number, and address was replaced, and every cached `sampleData` /
-object-shaped `defaultValue` (a captured real API response, not part of the
-flow's structure) was blanked to placeholder values while keeping its shape
-and field names. The scrub was a one-off script, not kept in the repo; a
-future batch needs its own token list built by hand from that batch's real
-values, not a blind re-run of this one's.
-
-**Field names inside the blanked sample data are real and informative** —
-e.g. `cnpjOuCpf`, `idCedente`, `telefoneContato` — only the *values* are
-placeholders. The business logic, node chaining, and CODE steps are
-otherwise unchanged from production.
-
-Two chains, by filename prefix:
-
-## PRD — the live, always-connected chain
-
-| File | What it demonstrates |
-| --- | --- |
-| `01-main-2-webhook-retorno-consulta.json` | `WEBHOOK` trigger → `ROUTER` with an empty branch → calling two subflows (`piece-subflows`) from different branches |
-| `01-main-2-danfe-consulta.json` | `CALLABLE_FLOW` trigger (a subflow's entry point) → `piece-date-helper` → `piece-http-oauth2` (an authenticated external call) → `piece-tables` write |
-| `01-main-4-recebimento-barramento.json` | `WEBHOOK` trigger → `LOOP_ON_ITEMS` over a batch payload → `ROUTER` *inside* the loop with an empty branch → calling a subflow per iteration. The loop-then-router-then-subflow nesting this tool's own compiler had never written before (see `research/ipaas/probe-loop-shape*.ts` and the `AGENTS.md` note on `ADD_ACTION` into a loop) |
-| `02-subflow-2-danfe-retorno.json` | `WEBHOOK` trigger receiving an async callback, `piece-tables` lookup/update, several `CODE` steps formatting Brazilian currency/date/percent values for a Pipefy card update |
-| `02-subflow-4-criacao-operacao.json` | `CALLABLE_FLOW` subflow, `piece-pipefy` `createCard` + `updateCard`, calling a further subflow |
-| `03-subflow-4-criacao-titulo.json` | The deepest one: `LOOP_ON_ITEMS` with a `ROUTER` in its body, `piece-store` for cross-step state (the same `get`/`put`/`remove_value` shape as this project's own CS-request pagination example), `piece-file-helper`, several chained `CALLABLE_FLOW` calls |
-| `04-subflow-4-criacao-cedente.json`, `04-subflow-4-criacao-sacado.json` | Near-identical pair (creditor vs. debtor side of the same process) — good for seeing how two flows built from the same template diverge |
-
-## HML — the staging/monitoring chain
-
-Same business domain, built as standalone monitoring flows rather than
-inline subflows — useful as a *second* worked example of the same node
-types without being a copy-paste of the PRD chain:
-
-| File | What it demonstrates |
-| --- | --- |
-| `hml-01-subflow-1-titulo-acompanhamento-cobranca.json` | `piece-store` state machine, `piece-date-helper`, single-purpose monitoring flow |
-| `hml-01-subflow-1-titulo-nfe-monitoramento.json` | Similar shape, different business event |
-| `hml-01-subflow-1-titulo-retorno-bancario.json` | Similar shape, a bank-return event |
-| `hml-02-subflow-2-retorno-consulta-cedente.json`, `hml-02-subflow-2-retorno-consulta-sacado.json` | `WEBHOOK` trigger + `piece-pipefy` card update, the creditor/debtor pair again |
+# Reference flows
+
+Thirteen real flows from a production trade-finance integration, sanitized
+before being added here — every company name, personal name, email, CNPJ,
+phone number, and address was replaced, and every cached `sampleData` /
+object-shaped `defaultValue` (a captured real API response, not part of the
+flow's structure) was blanked to placeholder values while keeping its shape
+and field names. The scrub was a one-off script, not kept in the repo; a
+future batch needs its own token list built by hand from that batch's real
+values, not a blind re-run of this one's.
+
+**Field names inside the blanked sample data are real and informative** —
+e.g. `cnpjOuCpf`, `idCedente`, `telefoneContato` — only the *values* are
+placeholders. The business logic, node chaining, and CODE steps are
+otherwise unchanged from production.
+
+Two chains, by filename prefix:
+
+## PRD — the live, always-connected chain
+
+| File | What it demonstrates |
+| --- | --- |
+| `01-main-2-webhook-retorno-consulta.json` | `WEBHOOK` trigger → `ROUTER` with an empty branch → calling two subflows (`piece-subflows`) from different branches |
+| `01-main-2-danfe-consulta.json` | `CALLABLE_FLOW` trigger (a subflow's entry point) → `piece-date-helper` → `piece-http-oauth2` (an authenticated external call) → `piece-tables` write |
+| `01-main-4-recebimento-barramento.json` | `WEBHOOK` trigger → `LOOP_ON_ITEMS` over a batch payload → `ROUTER` *inside* the loop with an empty branch → calling a subflow per iteration. The loop-then-router-then-subflow nesting this tool's own compiler had never written before (see `research/ipaas/probe-loop-shape*.ts` and the `AGENTS.md` note on `ADD_ACTION` into a loop) |
+| `02-subflow-2-danfe-retorno.json` | `WEBHOOK` trigger receiving an async callback, `piece-tables` lookup/update, several `CODE` steps formatting Brazilian currency/date/percent values for a Pipefy card update |
+| `02-subflow-4-criacao-operacao.json` | `CALLABLE_FLOW` subflow, `piece-pipefy` `createCard` + `updateCard`, calling a further subflow |
+| `03-subflow-4-criacao-titulo.json` | The deepest one: `LOOP_ON_ITEMS` with a `ROUTER` in its body, `piece-store` for cross-step state (the same `get`/`put`/`remove_value` shape as this project's own CS-request pagination example), `piece-file-helper`, several chained `CALLABLE_FLOW` calls |
+| `04-subflow-4-criacao-cedente.json`, `04-subflow-4-criacao-sacado.json` | Near-identical pair (creditor vs. debtor side of the same process) — good for seeing how two flows built from the same template diverge |
+
+## HML — the staging/monitoring chain
+
+Same business domain, built as standalone monitoring flows rather than
+inline subflows — useful as a *second* worked example of the same node
+types without being a copy-paste of the PRD chain:
+
+| File | What it demonstrates |
+| --- | --- |
+| `hml-01-subflow-1-titulo-acompanhamento-cobranca.json` | `piece-store` state machine, `piece-date-helper`, single-purpose monitoring flow |
+| `hml-01-subflow-1-titulo-nfe-monitoramento.json` | Similar shape, different business event |
+| `hml-01-subflow-1-titulo-retorno-bancario.json` | Similar shape, a bank-return event |
+| `hml-02-subflow-2-retorno-consulta-cedente.json`, `hml-02-subflow-2-retorno-consulta-sacado.json` | `WEBHOOK` trigger + `piece-pipefy` card update, the creditor/debtor pair again |