Pyrus Client Symfony Laravel Package

Product Decisions This Supports

• Workflow/approval automation in-product: Pyrus is a task-and-approval workflow platform; this client lets you create and track tasks, and now (v0.16.0, via CommentCreate) post comments onto them. That directly enables features like "route this request to an approver, capture the decision, and log the audit trail" without building a workflow engine.
• Build vs. buy for approvals: A CommentCreate addition signals the package is actively filling out the collaboration surface (create task → comment → track). If your roadmap includes human-in-the-loop review queues, escalation notes, or approval trails, this is a viable "buy/integrate" path versus building state machines and notification fan-out yourself.
• Audit-trail and internal-ops tooling: Posting structured comments programmatically means system-generated context (order IDs, customer tier, prior failures) can ride alongside the approval task — useful for back-office, finance ops, and support-escalation features.
• Roadmap signal, not a headline: This is an incremental capability, not a platform shift. Treat it as "the SDK now covers comment creation" — it unblocks a feature, but it does not by itself justify a roadmap commitment.
• Caveat on fit: The package family is a Symfony client (suare-su/pyrus_client_symfony), not a Laravel package. In a Laravel codebase you would consume it as a plain Composer dependency and wire your own service provider/binding, or look for a dedicated Laravel wrapper. Budget a small integration spike rather than assuming out-of-the-box Laravel ergonomics.

When to Consider This Package

Adopt when:

• Pyrus is already (or is being) selected as your workflow/approval backend — this is the official-style PHP path to its API.
• You need programmatic task creation plus comment append (v0.16.0 is the minimum version for that second capability).
• Your stack is Symfony, or Laravel where you are comfortable hand-wiring a third-party client into the container and config.
• You want a thin, versioned, semver-tagged dependency over hand-rolled Guzzle calls against a REST API.

Look elsewhere or pause when:

• You have no Pyrus dependency and no near-term approval/workflow requirement — adopting this pulls in an external SaaS and its auth/rate-limit model.
• You need a first-class Laravel experience: config publishing, facades, queued jobs, retry semantics, test fakes. Expect to build those yourself.
• Your reliability bar is high and you need documented retry/idempotency behavior — the release notes here are a single-line changelog, which is a maturity signal worth weighing for a payments-adjacent or customer-facing flow.
• You require a stable 1.0 API contract; the project is pre-1.0, so minor versions can change shape.

How to Pitch It (Stakeholders)

To executives: This is a small, low-cost integration that lets our product hand work off to Pyrus — the approval/workflow system — and write results and notes back automatically. The newest release (v0.16.0) adds the ability to post comments to tasks, which is what turns "we created a task" into "we have a traceable decision record." Recommendation: approve a timeboxed spike, not a full build-out.

To engineering: suare-su/pyrus_client_symfony v0.16.0 adds CommentCreate — we can now attach system-generated commentary to a Pyrus task, closing the loop on approval flows. It is a Symfony client, so in Laravel we own the wiring: a service-provider binding, config for credentials, and a thin adapter interface so we can swap it out. It is pre-1.0 and the changelog is terse, so pin the version, wrap it behind our own interface, and add contract tests against a mocked HTTP layer.

To product/design: New capability unlocked — annotate approval tasks with context (order, customer, prior actions) at creation and at each decision point. This makes the "why was this approved?" question answerable inside the tool users already work in, rather than in a separate audit log.