--- title: "ProAbono Integration" description: "ProAbono is a French subscription-billing platform with a Live API and a BackOffice API. Agents create customers and subscriptions, meter feature usage, manage offers and billing addresses, suspend or invalidate accounts, and react to billing events in real time." url: https://flowrunner.ai/integrations/proabono date_modified: 2026-09-04T14:51:36-07:00 --- # ProAbono [Payments](https://flowrunner.ai/integrations/category/finance-accounting) ProAbono is a French subscription-billing platform with a Live API and a BackOffice API. Agents create customers and subscriptions, meter feature usage, manage offers and billing addresses, suspend or invalidate accounts, and react to billing events in real time. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 51 actions · Basic auth · available [ProAbono website](https://www.proabono.com/) · [Platform Documentation](https://docs.proabono.com/) · Capability data verified 2026-08-25 1. The nightly reconciliation runs against your own user directory 2. Agent counts active seats and enabled modules per account in the product database 3. List Customer Usages reads what ProAbono currently records for each of those accounts 4. Quote Usage Update prices each difference before anything is written 5. Update Multiple Usages sets the seat counts and module switches to the counted truth 6. Accounts whose next charge moves beyond a threshold are summarized for the controller 7. The controller approves the increases that cross the threshold before the next invoice picks them up ## What This Integration Enables ProAbono models a subscription business around features rather than around price lists, and that choice shapes the whole API. Every feature is typed as on-off, a limitation, or a consumption meter, and the operation that reads a customer's usage is the same operation your product should gate access on. Asking which offer someone bought and mapping that to permissions yourself is the thing ProAbono is designed to make unnecessary, and there is a direct query that answers which customers currently hold a given feature. Two more properties matter for agents. Almost every money-moving operation has a matching quote that prices it without recording anything, so a flow can show the real prorated figure before a person decides. And the hosted portal links ProAbono returns authenticate by themselves, meaning anyone holding one reaches that customer's billing view, which is why revoking them is a first-class operation. FlowRunner agents meter, quote, upgrade, and reconcile continuously. The operations that end a relationship or erase a person stop and ask, because [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) is the default rather than a step someone remembered to add. ### Without FlowRunner **Entitlement inferred rather than read**: Who may use a module is worked out by listing plans and reasoning about which ones include it **Seat drift between systems**: A missed usage call is lost, so the invoice quietly bills against last month's headcount **Offboarding treated as one action**: Pausing an account, freeing a reference, and erasing personal data are handled as if they were interchangeable ### With FlowRunner **Entitlement read directly**: One call answers who may use a feature, another answers what a customer is entitled to against what they have consumed **Seats reconciled to your own count**: Setting the quantity outright is idempotent, so a missed run corrects itself on the next one **Offboarding as three separate decisions**: Pause, free the reference, and erase are distinct operations with distinct consequences, chosen on purpose ## Use Case Scenarios ### Seats that match the product, not last month's guess Your own user directory is the truth about how many seats an account is using. Each night the agent counts them, reads List Customer Usages for the same accounts, and where the numbers disagree calls Set Usage Quantity rather than Increment Usage, because setting the truth outright means a night the job did not run repairs itself the following night. Where a customer has switched a paid module on or off, Set Usage Enabled follows. Quote Usage Update prices each change first, so the summary that reaches the controller in [Slack](https://flowrunner.ai/integrations/slack) shows the charge each correction produces rather than only the seat delta. ### An upgrade page that quotes the number the customer will actually pay A customer opens the upgrade view. The agent calls List Upgrade Offers, which returns only the offers this customer can actually move to, already priced for them, with their subscribe links built in. For the offer they pick, Quote Subscription Upgrade prices the mid-period move, which is not the difference between two list prices because ProAbono credits the unused part of the current term. The customer sees the real figure. If they take it, Upgrade Subscription runs with the timing chosen deliberately, immediate or at the end of the term, rather than left on whichever default the API happens to carry. ### Consulting hours and overages that reach the right invoice Time logged in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) or an approved services record becomes a balance line, with the amount sent as the line total because quantity on this API is informative and does not multiply anything. A negative amount is how a goodwill credit is expressed. Nothing is invoiced yet, since balance lines wait for either the scheduled billing or an explicit call. Before that call, the agent reads List Balance Lines and shows the controller exactly what is sitting there, because billing sweeps up every waiting line and a consulting entry added early is on this invoice rather than next month's. ## Human-in-Loop Highlight ProAbono publishes five different ways to stop a customer and they are not degrees of the same thing. Suspend Subscription pauses billing and can be restarted. Terminate Subscription ends it and cannot be undone, and by default schedules the end for the next renewal rather than cutting access now. Suspend Customer is the one the vendor tells you to reserve for suspected fraud. Invalidate Customer frees your own reference for reuse and revokes their portal links, but explicitly does not terminate their subscriptions, so an invalidated customer keeps being billed under a generated reference. Anonymize Customer is irreversible GDPR erasure that clears the name and email while deliberately keeping the invoices, because accounting rules require them. An offboarding agent that treats these as synonyms produces either a departed customer who is still being charged or a data-subject request executed against the wrong record. So the agent gathers the facts and hands over the choice: "Account Meridian Labs, 2 running subscriptions, next renewal 12 days out, one open invoice for 1,340.00 EUR. Their request was to stop the service. Terminate both subscriptions at renewal and leave the record, or terminate immediately, and is this also an erasure request?" The controller answers, and the agent runs that verb and no other. The erasure, in particular, never happens on an inference. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 51 actions ### Customers 12 - **Create Or Update Customer** Declares one of your users to ProAbono. It is an upsert on your own reference, which is why there is no separate update route, and the response carries the hosted portal links that make a payment page unnecessary. - **Get Customer** Reads one customer by your reference, with their status, currency, and portal links. Status is the entitlement signal, so a suspended or grey-listed customer shows here rather than only failing at billing. - **List Customers** Lists customers page by page. The default page size is small, so a flow that reads one page and stops is looking at a fraction of the account. - **List Customers By Feature** Answers directly which customers currently hold one feature, rather than making you list offers and reason about what each includes. - **Get Customer Billing Address** Reads the address that appears on a customer's invoices, with their tax information. - **Update Customer Billing Address** Sets that address. The tax information field is the VAT number that drives reverse-charge treatment inside the EU, and setting it after an invoice is issued does not re-rate that invoice. - **Get Customer Payment Settings** Reads how a customer is billed, when they are next billed, and whether ProAbono has grey-listed them, which looks like a broken checkout until you read it here. - **Update Customer Payment Settings** Changes how a customer is billed. Setting a payment type here makes collection your responsibility, and the next billing date moves the whole anniversary. - **Anonymize Customer** Clears a customer's personal details in place for a data-subject request. It is irreversible, and it deliberately leaves the subscriptions and invoices behind. - **Revoke Customer Links** Invalidates every portal URL previously issued for a customer. Those links authenticate by themselves, so this is what a leaked link or a departing employee calls for. - **Invalidate Customer** Replaces a customer's reference with a generated one and revokes their links, freeing your reference for reuse. It does not terminate subscriptions, so billing continues under the new reference. - **Suspend Customer** Suspends a customer account. The vendor's guidance is to reserve it for suspected fraud rather than using it to pause a subscription. ### Usages 7 - **List Customer Usages** Returns every feature on a customer's subscription with what they are entitled to and what they have used. This is the read a product should gate on. - **List Feature Usages** The reverse view, returning how every customer is using one feature, which is how you find everyone approaching a limit. - **Get Usage** Reads one customer's usage of one feature. The cheapest call to put in front of a feature gate. - **Increment Usage** Adds to a metered feature each time something is consumed. It refuses for a customer with no valid payment information, which stops you accruing charges you cannot collect. - **Set Usage Quantity** Sets a limitation feature's current quantity outright. Sending the truth each time makes a missed call self-correcting, where a missed increment is simply lost. - **Set Usage Enabled** Switches an on-off feature for one customer, which is how an add-on module is sold outside their plan. - **Update Multiple Usages** Applies several usage changes in one call, each carrying whichever field suits its feature type. This is the shape a nightly reconciliation wants. ### Offers 6 - **List Offers** Returns the offers on sale in a segment with localized price strings ready to display, which is what builds a pricing table. - **List Customer Offers** Returns those offers priced in one customer's currency and language, with their subscribe links already built, which is the version a signed-in page should use. - **List Upgrade Offers** Returns only the offers a customer can actually move up to, already priced as an upgrade, so nobody is shown a plan they cannot switch to. - **Get Offer** Reads one offer. Adding a customer prices it for them, and adding the upgrade flag prices it as a move from what they already have, which is a different number. - **List Features** Returns the features defined in a segment with their types, which is what decides the correct usage operation for each. - **Get Feature** Reads one feature's definition, type, and localized description. ### Subscriptions 10 - **Create Subscription** Subscribes a customer to an offer, optionally overriding the terms for this customer only. Whether it starts running depends on whether the offer has a trial, and overrides can only be set at creation. - **Migrate Subscription** Creates a subscription without billing its first period, for moving a paying customer over from wherever you billed them before. - **Get Subscription** Reads one subscription with its state, pricing, term dates, and features. - **Get Customer Subscription** Reads a customer's subscription by your own reference, which saves a lookup when your system does not hold ProAbono's id. - **List Subscriptions** Lists subscriptions by segment, customer, or payer. Filtering by payer is what answers what a reseller or agency covers across the accounts it sponsors. - **Start Subscription** Starts or restarts a subscription in draft or suspended state. Billing the period immediately is an option, and it takes money. - **Suspend Subscription** Pauses a subscription. This is the reversible one, and it is what a customer taking a break should get. - **Upgrade Subscription** Moves a running subscription to another offer, prorated. Immediate defaults to on and billing defaults to off, and a minimum commitment refuses to upgrade unless it is explicitly waived. - **Terminate Subscription** Ends a subscription. It cannot be undone, and by default it schedules the end for the next renewal rather than cutting access now. - **Update Subscription Term Date** Moves when the current period ends. Pushing it out grants free time, which is the goodwill gesture this API otherwise lacks and is not the same as a discount. ### Quoting 5 - **Quote Subscription** Prices a subscription without creating anything, taking the same body as the create route so a negotiated rate can be shown before it is committed. - **Quote Subscription Start** Prices starting a draft or suspended subscription right now, before an immediate bill takes the money. - **Quote Subscription Upgrade** Prices a mid-period move to another offer, crediting the unused part of the current period. The only way to show the customer the right number. - **Quote Usage Update** Prices a usage change before it is applied, prorated for the remaining period. This is the add-a-seat confirmation. - **Quote Balance Line** Works out the tax-inclusive total of a one-off charge before it is added to a customer's balance. ### Balances 2 - **Create Balance Line** Puts a one-off amount on a customer's balance for consulting, an overage, or a credit. It invoices nothing on its own, and a negative amount is how a credit is expressed. - **List Balance Lines** Returns the lines waiting to be invoiced for a customer or a segment. The read that belongs before billing, because billing sweeps up everything sitting here. ### Invoices 3 - **Bill Customer** Turns everything on a customer's balance into an invoice now, and returns a link that sends them straight to paying it. - **Get Invoice** Reads one invoice. Accounting status and collection state answer different questions, and the response carries the PDF link. - **List Invoices** Returns a customer's or a segment's invoices with totals, currency, status, and PDF links, which together with a date filter is the accounting export. ### BackOffice 1 - **List BackOffice Resources** Reads any BackOffice collection, from discounts and pricing tables to gateway transactions and tax profiles, through one generic route. It reaches what the Live API deliberately leaves out, and answers an empty body rather than an empty list when nothing matches. ### Webhooks 5 - **Create Webhook** Registers a URL with the events it should receive. Creating it is not enough on its own, since ProAbono requires a validation step before anything is delivered. - **Get Webhook** Reads one webhook with its URL, trigger list, and whether it is actually live. - **List Webhooks** Returns the webhooks registered for a business, which is how you find out why deliveries stopped. - **Enable Webhook** Turns a webhook back on so notifications resume. - **Disable Webhook** Stops a webhook delivering. There is no delete route, so this is the teardown and the record remains. ## Triggers 1 triggers ### Event Triggers 1 - **On ProAbono Event** Fires when ProAbono reports one of its events: a customer added, suspended, billed, or charged, a subscription started, renewed, suspended, upgraded, or terminated, an invoice issued, paid, refunded, overdue, or disputed, or a payment permission expiring or failing. The expiring-permission events are the useful ones for a dunning flow, because they arrive before a charge fails rather than after. ## Frequently Asked Questions ### What can FlowRunner do with ProAbono? FlowRunner agents can run Create Or Update Customer, Get Customer, and List Customers in ProAbono, plus 48 more actions. ### Does connecting ProAbono to FlowRunner require OAuth? No. ProAbono connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can ProAbono trigger a FlowRunner workflow automatically? Yes. ProAbono supports 1 trigger that can start a FlowRunner workflow automatically. **Work at ProAbono?** This integration exposes ProAbono to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/proabono. Site index: https://flowrunner.ai/llms.txt