HelloAsso

HelloAsso is the French association payments and fundraising platform, with Plus Billetterie for ticketing. Agents create checkout intents, manage forms, orders, and payments for an organization, run ticketing events, and react to notifications in real time.

Verified 1 trigger 87 actions OAuth available

HelloAsso website Platform Documentation Capability data verified 2026-08-25

A monthly donor writes in asking to stop their giving

Agent reads the order with Get Order and the payments made against it

Get Payment reports the cash-out state of each payment, and which are already in the bank

Agent separates what Cancel Order stops from what only Refund Payment returns

Cancel Order stops the installments still to come, which refunds nothing on its own

The amount already cashed out and the donor's options post to the fundraising channel

A staff member decides on the refund and clears the second factor the route requires

What This Integration Enables

HelloAsso is not a merchant gateway with a charity theme on it. It is built around French associations, and that shows in what the API cares about. An organization record carries whether it may issue a fiscal receipt and whether it is currently allowed to take money at all. A checkout intent has a donation flag that drives the donor's tax certificate rather than the display. And a payment's cash-out state, not its authorization, is what says whether the money has reached the association's bank account.

There is a second product inside the same connector. Plus Billetterie is a full ticketing platform with events, shops, selling items, discount codes, per-ticket forms, and a scanned guest list, and it uses its own object model in which a product is what the buyer receives and a selling item is what it costs. FlowRunner agents run both halves: creating checkout intents and reconciling contributions on the fundraising side, and building, opening, and closing ticket offices on the events side. Where money goes back out, HelloAsso itself insists on a person, which suits how FlowRunner already thinks about human-in-the-loop.

Without FlowRunner

Donor requests handled in a mailbox A stop request sits in a shared inbox and the next installment goes out before anyone acts

Fiscal receipts chased later Whether a contribution earns a tax certificate is discovered after the donor asks for one

Bank transfers arrive as lump sums A single payout lands and nobody can break it back into the gifts it came from

With FlowRunner

Requests worked as a queue The order, its payments, and their cash-out state are read before anything is promised

Receipt eligibility read up front The donation flag and the association's own eligibility are checked when the intent is created

Payouts broken back into gifts The cash-out export reconstructs a transfer line by line against the payments behind it

Use Case Scenarios

A contribution that keeps its tax status

A supporter chooses to give in three monthly installments through the association's own site. The agent creates the checkout intent with the total expressed as an initial amount plus two future terms, and the platform validates that arithmetic before returning the payment page, so a mismatch is caught up front rather than at settlement. Crucially it sets the donation flag correctly, because that field drives the fiscal receipt and a donation form marked otherwise denies the donor their tax certificate. Once the payment is authorized, Get Checkout Intent returns the order it produced along with the metadata the agent attached, which is how the gift is matched to the supporter's record in HubSpot.
Reconciling a payout back to the gifts inside it

HelloAsso transfers money to the association's bank account as a lump sum. The agent reads Export Cash Out for that transfer, which returns the line-by-line detail: every payment and refund that made it up, with the campaign, the payer, the dates, and the credit or debit. Each line is matched to a payment read with Get Payment, whose cash-out state confirms the money genuinely left the platform rather than merely being authorized. The reconciled set appends to Google Sheets for the treasurer, and any line the agent cannot match is posted as an exception rather than silently dropped.
A ticket office opened and closed by a flow

An event goes on sale. The agent creates the event, then the products the buyer receives, then the selling items that price them, then the shop that offers them, in that order, because an event alone sells nothing. It sets the tax rate deliberately on each product, since the create call defaults to the reduced French rate and neither the rate nor the product type can be changed afterward. Opening is a status change on the shop and closing is the same field the other way, which is the fastest way to stop sales without touching a single price. Once the event runs, List Billetterie Attendees is the guest list, and its scan count is what separates an unused ticket from one already through the door.

Human-in-Loop Highlight

HelloAsso built the pause into the refund route itself. Refund Payment is protected by strong authentication: the first call comes back with an error naming which second factor a user must clear, and the resulting token has to be handed back through one of the platform's authorization operations. An unattended flow cannot assume a refund will simply go through, and that is a design decision rather than an obstacle. It also sits next to a fork that trips people up, because Cancel Order stops the installments still to come and refunds nothing, so canceling a monthly donation after three months leaves those three months paid. So the agent does the reading and stops at the decision: "Marie asked to stop her monthly gift. Three payments of 25 euros are already cashed out. Cancel future installments only, or also refund the 75 euros already taken? The refund needs a staff member to clear the second factor." A person answers, clears the factor, and the money that goes back out went back because somebody chose it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

87 actions

Checkout

Create Checkout Intent Creates a checkout intent and returns the hosted payment page to send the contributor to. All amounts are in cents and the arithmetic is validated: the total must equal the initial amount plus every term. Terms are how installments are expressed, and the donation flag drives the fiscal receipt rather than the display.
Get Checkout Intent Returns a checkout intent and, once the payment has been authorized, the order it produced. This is the operation that confirms a checkout, since the return URL's query parameters come from the contributor's browser and this is the server's own answer. Your metadata comes back here.

Directory and Reference Data

Search Directory Forms Searches the public directory of campaigns across every association that has opted into it. It behaves as a synchronization feed rather than a result set: results are ordered by the date their directory visibility changed, and a continuation token then returns only what has changed, including campaigns that have left the directory.
Search Directory Organizations Searches the public directory of associations. Like the campaign search it is a synchronization feed ordered by visibility change, paged by continuation token, and its total count is never returned.
Get Tag Returns one directory tag with, optionally, how many campaigns and associations use it and how much money they have collected.
List Public Tags Returns every public tag the directory currently uses, each with a score. Read this before filtering a directory search by tag, since a tag that is not in the list matches nothing.
List Form Activity Types Returns the activity types available for one kind of campaign, which is what fills the activity type on a quick campaign creation.
List Organization Categories Returns the list of association categories, the values the directory searches filter on.
List Company Legal Statuses Returns the legal statuses recognized for a company payer, used when a business rather than an individual contributes.

Campaigns

Quick Create Form Creates a campaign with a limited set of fields and simple pricing, which can then be finished in the back office. The vendor supports event campaigns only here, tier prices are in cents, and the title generates the campaign URL, which can never be changed afterward.
Update Form State Publishes, hides, drafts, disables, or deletes a campaign. This is the only write that can take a live campaign off sale, and deletion is not reversible through the API. Making a campaign private keeps it reachable by direct URL while removing it from search engines and the directory.
Get Public Form Returns everything published about one campaign: its description, dates, place, tiers, images, and widget URLs. The tiers carry the prices and their identifiers, which is what an order or a ticket refers back to.
Get Form Stats Returns a campaign's participant total and its per-tier and per-option breakdown. The cheap way to check remaining capacity without paging every order.
List Organization Forms Lists an association's own campaigns, newest first, optionally filtered by state and kind. Unlike the directory searches this shows draft and private campaigns too.
List Organization Form Types Returns the kinds of campaign for which an association has at least one campaign. One small request that tells you which campaign types are worth querying.

Organizations

Get Organization Returns an association's public record: name, description, category, legal type, address, logo, and images. Its fiscal receipt eligibility says whether it may issue a tax certificate for a donation, and a compliance flag says whether it is currently allowed to take money at all.
List My Organizations Returns every association the connected user has rights over, with the role held on each. This is a user-token route, so a client-credentials connection answers empty rather than failing, which reads as no associations when it means no user.

Items, Orders, and Payments

Get Item Returns one item bought in an order: the ticket, membership, donation, or product line, with its payer, its share of each payment, and optionally the custom-field answers. The ticket and membership card URLs live here, which is what to send an attendee.
List Form Items Lists what one campaign has sold, every ticket, membership, donation, and product line. Sorting by update date rather than transaction date is what an incremental sync needs, since it catches records that changed.
List Organization Items Lists every item an association has sold across all its campaigns. The right starting point for an accounting export.
Get Order Returns one order with its payer, its items, and every payment made against it. An order is not a payment: one paid in installments has one order and several payments, so the order amount is what was agreed and the payments say what has arrived.
List Form Orders Lists the orders placed on one campaign, newest first. There is no state filter here, so an abandoned or refused order is listed alongside a paid one.
List Organization Orders Lists every order placed with an association across all its campaigns, newest first.
Cancel Order Stops the payments still to come on an order. It refunds nothing: money already taken stays taken, so canceling a monthly donation after three months leaves those three months paid.
Get Payment Returns one payment with its payer, the items it paid for, its cash-out state, and its refund operations. The cash-out state is what says whether the money has actually reached the association's bank account, and the payment and fiscal receipt URLs are the documents to send the payer.
List Form Payments Lists the payments made on one campaign. With no state filter this includes refused, abandoned, and pending payments, and sorting by update date is how a refund or a contested payment surfaces in a sync.
List Organization Payments Lists every payment made to an association across all its campaigns. Filtered to authorized and sorted by update date, this is the reconciliation query.
Refund Payment Refunds a payment in full or in part. The route is protected by strong authentication: the first call names which second factor a user must clear, and the resulting token has to be handed back through one of the platform's authorization operations. Amounts are in cents and partial refunds are limited by the underlying processor.
Export Cash Out Returns the line-by-line detail of one cash-out: every payment and refund that made up a transfer to the association's bank account, with the campaign, the payer, the dates, and the credit or debit. This is the bank reconciliation operation.

Partner and Notification Settings

Get Partner Returns the API client's partner record: display name, description, logos, client configuration, registered notification URLs, and usage statistics. The read that shows which notification URLs are live.
List Partner Organizations Lists every association that has authorized this partner. Like the directory feeds it is ordered by visibility change and paged by continuation token rather than by page count.
Update Partner Domain Sets the domain the platform will redirect back to at the end of the authorization screen. Getting it wrong breaks every new authorization, and since existing links keep working, the damage shows up only the next time an association tries to connect.
Set Partner Notification URL Registers where notifications are posted for every association linked to this partner, and returns the signature key for verifying them. The registration is keyed on notification type rather than URL, so calling it twice for the same type replaces the earlier URL silently. Save the returned key, since it is shown once.
Delete Partner Notification URL Removes a global partner notification URL. It is addressed by type rather than by URL, so leaving the type empty removes the untyped catch-all registration and whatever URL currently occupies that slot.
Set Organization Notification URL Registers where notifications are posted for one association, and returns the signature key for verifying them. Use this rather than the global URL when a partner serves many associations. Save the returned key, since it is not readable afterwards.
Delete Organization Notification URL Removes a per-association notification URL. Addressed by association and type rather than by URL, so it removes whatever occupies that slot.

Ticketing: Organizers and Clients

List Billetterie Organizers Lists the organizers a ticketing key can reach. This is how you find your organizer identifier, which every other ticketing operation needs, and because a key is tied to a single organizer it normally returns exactly one.
Get Billetterie Organizer Returns one organizer with its type, contact details, media, and slug.
Update Billetterie Organizer Updates an organizer's name, type, contact details, media, or slug. Changing the slug changes the public address of every shop and ticket office underneath, so links already handed out stop working.
Delete Billetterie Organizer Removes an organizer. This is the top of the tree: every event, shop, product, and ticket underneath belongs to it, and the key on the connection is tied to this organizer.
Get Billetterie Client Returns one client, a buyer's record across the organizer, with their email, the events and campaigns they have bought into, their orders, and their lifetime spend. There is no list route for clients, so a client is reached from an order or an attendee.

Ticketing: Events and Attendees

List Billetterie Events Lists an organizer's events. An event is the container for everything else: its ticket categories, products, selling items, shops, discount codes, and forms all hang off it.
Create Billetterie Event Creates an event. Creating it sells nothing, since an event needs a selling item and a shop before anyone can buy. The fees mode decides who pays the ticketing fee, and the timezone defaults to Paris, which quietly shifts every sales window for an event elsewhere.
Get Billetterie Event Returns one event with everything configured on it: status, dates, place, fees mode, tax treatment, queue and waitlist settings, and the identifiers of its form and content.
Update Billetterie Event Updates an event. Setting the status to published is what puts it on sale and canceled is what takes it off, with the sales history kept either way. Changing the fees mode after tickets have sold applies only to sales from that point.
Delete Billetterie Event Removes an event and everything configured under it. Canceling or disabling on the update route is preferable once tickets have sold, because that keeps the sales history.
List Billetterie Attendees Lists the attendees of an event, one record per ticket, with its unique ticket identifier, the buyer's email, the seat, the price paid, and the status. This is the guest list, and the interaction count says how many times a ticket has been scanned.
Get Billetterie Attendee Returns one attendee: the ticket identifier, the holder, the seat, the form answers, the access token, and how many times it has been scanned. The access token is what a door-scanning app checks.

Ticketing: Categories and Discounts

List Billetterie Ticket Categories Lists an event's ticket categories, the headings that group selling items on the ticket office page. A category is presentation and capacity, not price.
Create Billetterie Ticket Category Creates a ticket category on an event. Its maximum count caps the whole category, which is how several ticket types share a pool of places.
Get Billetterie Ticket Category Returns one ticket category with its name, description, capacity, and translations.
Update Billetterie Ticket Category Updates a ticket category. The index is available only here and is what reorders the categories on the ticket office page.
Delete Billetterie Ticket Category Removes a ticket category. Selling items pointing at it lose their grouping.
List Billetterie Discounts Lists an event's discount codes with their type, amount, usage cap, and which selling items they apply to.
Create Billetterie Discount Creates a discount code on an event. The amount means two different things: a percentage type takes a fraction between zero and one, while a fixed type takes an amount in cents. The name must be unique within the event, and leaving the selling items empty applies the code to everything on sale.
Get Billetterie Discount Returns one discount code with its type, amount, status, usage cap, and the selling items it covers.
Update Billetterie Discount Updates a discount code. Setting the status to disabled is how a promotion is stopped without losing the record of who used it.
Delete Billetterie Discount Removes a discount code. Disabling it is preferable once the code has been used, since that keeps the record.

Ticketing: Forms

List Billetterie Forms Lists the forms defined on an event, the extra questions asked at checkout or per ticket, with their fields.
Create Billetterie Form Creates a form on an event. Where it is attached decides how often it is asked: on the event once per order, on a selling item once per line, and on a product once per ticket.
Get Billetterie Form Returns one form with its full field definitions, which is what a response's values have to line up with.
Update Billetterie Form Updates a form. The fields replace the whole definition, so omitting a question removes it, and removing or renaming a field that existing responses answered leaves those answers orphaned.
Delete Billetterie Form Removes a form. Anything pointing at it stops collecting those answers, and existing responses lose their definition.
List Billetterie Form Responses Lists the answers buyers have given to an event's forms. This is where the dietary requirement, the shirt size, and the emergency contact live, since an attendee record carries only the identifier of its response.
Create Billetterie Form Response Records an answer set against a form. Its identifier is what an order placed through the API takes, which is how it carries the same answers a buyer would have typed at checkout.
Get Billetterie Form Response Returns one form response with the answers it holds.
Update Billetterie Form Response Corrects the answers on a form response, the operation for a buyer who gave the wrong shirt size. The values replace the stored answers, and there is no delete route for a response.

Ticketing: Products, Prices, and Shops

List Billetterie Products Lists an event's products. A product is not a price: it is the thing a buyer receives, with its own capacity, tax rate, and per-ticket form. What it costs is decided by the selling item that offers it.
Create Billetterie Product Creates a product, the ticket or good a buyer receives. The tax rate is required and defaults to the reduced French rate, so getting it wrong misstates VAT on every sale. A product alone sells nothing without a selling item and a shop.
Get Billetterie Product Returns one product with its type, capacity, tax rate, sales window, and the form asked per ticket.
Update Billetterie Product Updates a product. The tax rate and the type are not updatable, since the vendor's update schema omits both, so a product created at the wrong rate or as the wrong kind has to be replaced rather than corrected.
Delete Billetterie Product Removes a product. Selling items that offer it stop working, so disabling the selling item is the safer move once the event has sold.
List Billetterie Selling Items Lists an event's selling items, the priced offers on the ticket office page. This is where prices live: a selling item joins a product to a price, a category, and one or more shops.
Create Billetterie Selling Item Creates a priced offer on an event. The steps are required and are the price, so at minimum send one base step carrying the base price in cents. Two of the four statuses are visible but unbuyable, which is how a coming-soon line is made, and the shop identifiers decide where the offer appears.
Get Billetterie Selling Item Returns one selling item with its price steps, status, caps, price modifiers, and the shops it appears in.
Update Billetterie Selling Item Updates a selling item. Sending the steps replaces the price structure entirely, so read the item first and send the complete list back. Disabling is how an offer is taken off sale without losing what it has already sold.
Delete Billetterie Selling Item Removes a selling item. Disabling it is preferable once anything has sold, since that status keeps the sales history and deleting does not.
List Billetterie Shops Lists an event's shops, the public ticket office pages. An event can have several, each with its own theme, slug, layout, and set of selling items, and each carries its takings to date.
Create Billetterie Shop Creates a shop, a public ticket office page for an event. A second shop is how one event sells to two audiences at different prices. A hidden status keeps the shop working for anyone holding its URL while removing it from listings.
Get Billetterie Shop Returns one shop with its status, layout, theme, locale settings, and takings, plus whether it is the event's principal ticket office and what its waiting room is doing.
Update Billetterie Shop Updates a shop. Setting the status to enabled is what opens a ticket office and disabled is what closes it, which is the fastest way to stop sales on an event without touching a single selling item. Changing the slug breaks every link already handed out.
Delete Billetterie Shop Removes a shop. Its public URL stops working immediately, and any selling item that pointed only at this shop is offered nowhere. Disabling it closes the shop without either consequence.

Ticketing: Orders and Refunds

List Billetterie Movements Lists an organizer's movements, which are its orders and its refunds in one stream, told apart by a type field. There is no separate orders route, so a flow counting sales has to exclude the refunds itself.
Create Billetterie Order Places an order on behalf of a buyer, the API equivalent of someone going through the ticket office. The same vendor route also issues refunds, distinguished by a type field, and this operation never sends it, so it can only ever create an order. A form response identifier carries the checkout answers and discounts apply promotions.
Create Billetterie Refund Issues a refund. Three ways to say how much, and they are not interchangeable: a fixed amount in cents, a proportion, or the cost of the named lines. The pointer type says whether the named strings are identifiers or keys, and getting that wrong matches nothing and refunds nothing.
Get Billetterie Movement Returns one movement, an order or a refund, with its lines, buyer, discounts, donation, and status. Read the type first, since an empty type is an order and a refund type is money going back.
Update Billetterie Movement Updates an order or a refund. This is also the ticket administration operation: it changes who a ticket was sent to, swaps what a line admits to, moves someone's seat, and corrects billing details. Sending the selling items instead replaces the order's lines, which is a much larger change.

Triggers

1 triggers

Event Triggers

On HelloAsso Notification Fires when HelloAsso posts a notification: a payment authorized, refunded, refused, or contested; an order created; a campaign created; or an association renamed. Only four notification types exist and several distinct events share each one, so read the body rather than trusting the type alone.

Frequently Asked Questions

What can FlowRunner do with HelloAsso?

FlowRunner agents can run Create Checkout Intent, Get Checkout Intent, and Search Directory Forms in HelloAsso, plus 84 more actions.

Does connecting HelloAsso to FlowRunner require OAuth?

Yes. HelloAsso connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can HelloAsso trigger a FlowRunner workflow automatically?

Yes. HelloAsso supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with HelloAsso

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us