@taskmagic/apps-pabbly-subscription-billing

TaskMagic integration for Pabbly Subscription Billing.

Scope

"Pabbly" is five separate products behind five separate hosts. This piece covers Subscription Billing (payments.pabbly.com/api/v1) only — not Pabbly Connect, Chatflow, Email Marketing, or Email Verification. Each of those has its own API and its own credentials, and would be its own piece.

Connecting

Requires an API Key and a Secret Key from Settings → API inside Pabbly Subscription Billing. The secret is displayed once, when the key is generated.

Authentication is HTTP Basic — base64(apiKey:secretKey) — per the Subscription Billing API reference. (The API portal's landing page describes a bearer token for the Pabbly suite in general; that does not apply to this host.)

Actions

| Action | Endpoint | |---|---| | Create Customer | POST /customer | | Find Customer by Email | GET /customer/?email= | | Get Customer | GET /customer/{customer_id} | | Update Customer | PUT /customer/{customer_id} | | List Customers | GET /customers | | Create Subscription | POST /subscription/{customer_id} | | Get Subscription | GET /subscription/{subscription_id} | | Cancel Subscription | POST /subscription/{subscription_id}/cancel | | List Subscriptions | GET /subscriptions · GET /subscriptions/{customer_id} |

Notes

• Pabbly answers HTTP 200 with {"success": false, "error": "..."} for application-level failures. The shared client turns those into thrown errors carrying Pabbly's own message, so a failed create cannot look like a success to a flow.
• Cancel Subscription uses an explicit two-option dropdown rather than a checkbox: an untouched checkbox persists as false, which would silently mean "cancel immediately".
• No triggers yet — Pabbly's webhooks are registered in its UI with no documented subscribe/unsubscribe endpoint, and the list-endpoint response schema is not published, so a polling trigger cannot be keyed reliably. See the comment in src/index.ts.