FITsociety Help EN

Start an automation with FITsociety triggers in Make

3 min read

In this article

A FITsociety trigger starts your Make scenario when something happens, for example when a member is created or a booking is cancelled. You then let Make run a following step in FITsociety or another app. For this, you need access to the FITsociety app in Make and a working connection with the right company.

Choose an instant trigger

Open the FITsociety app in your scenario and choose the event you want to respond to. Modules labeled INSTANT receive events through a webhook: the connection through which FITsociety passes a new event to Make.

The FITsociety events cover, among other things, created or changed members, new or cancelled bookings and assigned or completed forms. Choose from the triggers available in your app version. Use one specific event that fits your goal.

The available data depends on the event type and the consent granted. An event about a payment or conversation does not automatically give access to all financial data or the full conversation content. Certain data requires additional consent.

Create the webhook

  1. Add the instant trigger you want as the first module.

  2. Under Webhook, create a new webhook.

  3. Give it a recognizable name and choose your FITsociety connection.

  4. Save the webhook and the module.

Use the webhook setting of the FITsociety trigger. Follow the instructions of that module; you don't need to build your own receiving endpoint. Before testing, check that the connection belongs to the intended company.

Test the first event

  1. Click Run once.

  2. Then perform the matching action in the connected FITsociety company. For example, use a fictional member.

  3. Open the trigger result. Check the event type, the event ID and the available data.

  4. Add the following step and map only the fields you need.

  5. Save the scenario and check the schedule. For immediate processing, choose Immediately as data arrives where available.

Test with a new event after the webhook has been created. An instant trigger is not a full historical export. Make may process received events in a queue, depending on your scenario's schedule and limits.

Duplicate processing and other triggers

An event can be delivered again after a temporary failure. Use the event ID to keep track of whether you have already processed it. Also give FITsociety write actions a stable Source operation key, as explained in Prevent duplicate changes in Make.

A polling trigger, by contrast, checks for new data on a schedule. Choose its starting point and check schedule deliberately; such a trigger does not use an instant webhook. Check in the module help which data it fetches, and for new events use the matching instant trigger when it is available.

Read more about scheduling in Make on scheduling scenarios.

No connection yet? Read Connect FITsociety to Make.

Was this article helpful? Thanks for your feedback!

Thanks, we read every comment.

Related articles