Resources · Make integration

HelloAsso Make integrationAutomate HelloAsso with Make.

Can Make react the moment something happens in HelloAsso? Yes. The HelloAsso Make integration offers 2 instant triggers, 9 actions and 3 searches covering orders, payments, checkouts and forms. This guide links your account and builds a first scenario with you, step by step.

Try the HelloAsso integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HelloAsso Make integration do for you?

The HelloAsso Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) listen to your HelloAsso account and act on it. You can read orders and payments, open a checkout, cancel future payments or start a refund, all without writing code.

Keep your records in sync. Watch notifications starts a scenario as soon as HelloAsso reports an event. Add Get order behind it and push the details into a base you already use, for example with the Airtable Make integration.

Send payment links from another tool. Init a checkout prepares a HelloAsso payment and hands back its URL, so a sign-up collected elsewhere can receive a link to pay.

Handle cancellations cleanly. Search payments or Search orders finds the right item, then Init payment refund or Cancel Order does the rest.

What Make does not offer here: no scheduled trigger, only the 2 instant ones, and nothing beyond the 14 listed modules unless you write your own request with Make an API call. Many apps also have an n8n node; n8n vs Make lays out the criteria, and Make training helps if you are new to the editor.

Connect

How do you connect HelloAsso to Make?

  1. 01

    Open the connection window

    Add any HelloAsso module to your scenario and click Create a connection. A connection is your HelloAsso account linked to Make once, then reused by every HelloAsso module. The Connection name field is optional.

  2. 02

    Copy your client credentials

    In HelloAsso, go to Mon Compte, then Integration et API. Copy the Client ID and the Client secret. If HelloAsso asks for a callback URI, enter https://www.integromat.com/oauth/cb/helloasso.

  3. 03

    Paste them into Make

    Back in Make, paste both values into the connection window, or follow the on-screen instructions, and save. From then on, Make can list what it reads in your HelloAsso account while you fill a module.

First scenario

Your first scenario: a HelloAsso payment link on request

GoalWhen a request lands in another app, Make opens a HelloAsso checkout and returns the payment URL.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. This first module is the app where requests arrive, such as the form tool your club already uses.

  2. 02

    Add Init a checkout

    Click the + on the right of that first module, search for HelloAsso and pick Init a checkout. Click Create a connection if your account is not linked yet.

  3. 03

    Fill in the checkout

    Fill the module fields and map the data coming from the first module. Once the connection exists, Make shows what it can read in HelloAsso, so you pick from a list instead of typing.

  4. 04

    Test with Run once

    Click Run once, then open the bubble above Init a checkout to read its bundle, the item passed between modules. The payment URL is what you send on next.

  5. 05

    Set the schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a HelloAsso scenario?

2 modules start a scenario when something happens in HelloAsso. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HelloAsso as soon as it happens.

HelloAsso1Watch notifications

Watch notifications

Instant trigger

In Make“Trigger when a notification occurs”

Your scenario wakes up as soon as HelloAsso sends Make a notification, so the next modules work on fresh data instead of waiting for someone to open the dashboard. What HelloAsso sends travels on as a bundle that later modules can map.

How it fires
instant. HelloAsso calls Make through a webhook as soon as it happens, which is what the lightning badge on the module means.
When to use it
you want each new HelloAsso event copied into the tool your treasurer already reads, without anyone exporting a file by hand.
Watch out
Make asks you to click Create a webhook before Create a connection on this module.
HelloAsso2Watch notifications (manual)

Watch notifications (manual)

Instant trigger

In Make“Triggers when a notification occurs. Webhook to be set manualy in HelloAsso Account”

You get the same instant start as Watch notifications, with one difference that matters: the webhook is set by hand in your HelloAsso account rather than for you. That gives you control over which address your account calls.

How it fires
instant. HelloAsso calls Make through a webhook as soon as it happens.
When to use it
you prefer to register the webhook yourself in HelloAsso, for instance because you manage that account setting directly.
Watch out
until the webhook is entered in your HelloAsso account, the scenario receives nothing at all, so do that before your first Run once.
Modules

What can Make do in HelloAsso?

HelloAsso gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HelloAsso1

Cancel Order

Action

In Make“Cancel future payments for an order”

Stops the payments still to come on a HelloAsso order, so nothing more is collected on it after this step runs.

When to use it
a member asks to end a commitment and the request is logged in another tool your scenario watches.
Watch out
the module needs the order ID. Find it first with Search orders, and remember that Run once cancels for real.
HelloAsso2

Get a checkout

Action

In Make“Get checkout information by ID”

Brings back the details of one checkout when you already hold its ID, so you can reread a payment request you opened earlier.

When to use it
after Init a checkout, later in the same scenario or in another one, to check the checkout before you follow up with the payer.
Watch out
it reads one checkout by ID and does not search, so keep the ID from the earlier module.
HelloAsso3

Get a form

Action

In Make“Get form information by ID”

Hands you the information of one HelloAsso form, looked up by its ID, ready to reuse in the rest of the scenario.

When to use it
a message or a report needs to name the campaign or event a payment belongs to, and you want the form details next to it.
Watch out
without the ID, start with Search forms, which can return several forms at once.
HelloAsso4

Get a payment

Action

In Make“Get a payment by ID”

Gives you one payment in full from its ID, so a later module can use the exact record instead of a guess.

When to use it
a search pointed to a payment and you want its complete details before writing them to your bookkeeping sheet.
Watch out
pick Search payments when you have criteria rather than an ID; this module expects exactly one ID.
HelloAsso5

Get order

Action

In Make“Get an order by ID”

Returns a single HelloAsso order from its ID, which is often the piece of data you want to file or share once something happens.

When to use it
behind Watch notifications, if the notification carries the order ID (check it with Run once), to file the full order in your member list.
Watch out
an order can contain several items; to read one of them, add Get order's item with that item's ID.
HelloAsso6

Get order's item

Action

In Make“Get an order's item by ID”

Zooms in on one line of an order, fetched by its own ID, so you work on a single ticket or membership rather than the whole basket.

When to use it
an event registration holds several tickets and each one should create its own row or badge.
Watch out
this is the item ID, not the order ID. Mixing the two is an easy mistake when mapping.
HelloAsso7

Init a checkout

Action

In Make“Initialize a payment process and return the payment URL.”

Opens a HelloAsso payment for you and returns the payment URL, ready to send to the person who has to pay.

When to use it
someone signs up through a tool outside HelloAsso, and you want to reply with a link to settle the fee.
Watch out
the module only prepares the payment. Add a module after it to deliver the URL, otherwise nobody sees it.
HelloAsso8

Init payment refund

Action

In Make“Initialise a payment refund”

Starts the refund of a HelloAsso payment from your scenario, so a cancellation request does not wait in someone's inbox.

When to use it
an event is called off, or an approval in another app says a supporter gets their money back.
Watch out
it acts on real money. Test on a payment you really intend to refund, since Run once executes the refund.
HelloAsso9

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the HelloAsso API with the connection you already set up, which covers whatever the dedicated modules leave out.

When to use it
the action you need has no dedicated module in the list, but the HelloAsso API offers it.
Watch out
you write the request yourself, so keep the HelloAsso API documentation open while you fill the module.
HelloAsso10

Search forms

Search

In Make“Search forms based on many criteria within an organization”

Lists the forms of an organization that match your criteria, which saves you from copying form IDs by hand.

When to use it
a report has to go through every active campaign, or a later module needs the ID of a form you only know by name.
Watch out
a search can return zero, one or many bundles; each one runs the next modules again.
HelloAsso11

Search orders

Search

In Make“Search orders based on many criteria”

Finds the orders that fit your criteria and passes each match along as its own bundle, one order per bundle.

When to use it
you need to locate an order before cancelling it, or pull a set of orders into a spreadsheet for the board.
Watch out
the result may be empty, a single order or a long list, so check it with Run once before adding an action.
HelloAsso12

Search payments

Search

In Make“Search payments based on many criteria”

Pulls up payments that match your criteria, the fastest route when you know roughly what you are after but not the exact ID.

When to use it
a donor writes in about a charge and you want to find it before starting a refund.
Watch out
several payments can match. Narrow the criteria before chaining a module that acts, such as Init payment refund.
Need help

Need help automating HelloAsso with Make?

A person reads every message.

FAQ

HelloAsso and Make: common questions

01Is the HelloAsso Make integration free?
Yes, HelloAsso is a standard app in Make, so it is available from the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and count usage in operations each month. The price of your HelloAsso account itself is a separate question, covered on the HelloAsso side.
02What do you need to connect HelloAsso to Make?
You need an active HelloAsso account and its API credentials. In HelloAsso, open Mon Compte, then Integration et API, and copy the Client ID and the Client secret. If a callback URI is requested, the Make documentation gives https://www.integromat.com/oauth/cb/helloasso. In Make, add a HelloAsso module, click Create a connection, give it a name if you like, and paste the two values. For the two instant triggers, click Create a webhook first, then Create a connection.
03Does the HelloAsso trigger in Make fire in real time?
Yes. Both HelloAsso triggers, Watch notifications and Watch notifications (manual), are instant: HelloAsso calls Make through a webhook as soon as something happens, instead of Make checking on a schedule. The difference between them is setup. The first one handles the webhook with you in Make, while the manual one expects you to enter the webhook in your HelloAsso account yourself. Scheduled triggers, where Make looks at regular intervals, do not exist for this app, so the 15 minute default only applies if your scenario starts from another app.
04What if a HelloAsso module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the HelloAsso API with the connection you already created, so you do not need a second login. The listed modules cover orders, order items, payments, checkouts, forms, refunds and order cancellation; anything outside that goes through this module. You write the request yourself, so keep the HelloAsso API reference open. If the gap is on the Make side rather than HelloAsso, such as the Free plan limits on active scenarios or file size, moving to a paid plan is the answer.
05Should you use Make or n8n for HelloAsso?
It depends on where you already build. On Make, HelloAsso comes with 14 ready modules, including 2 instant triggers, and a connection you set up once for all of them. Many apps also have an n8n node, so check whether HelloAsso has one and what it covers before you choose. Compare the modules you actually need, the way each tool starts a workflow, and the team that will maintain it. If you already run other scenarios in Make, keeping HelloAsso there keeps everything in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations