In this article
With Make, you connect FITsociety to other apps. For example, you can pass a new member to your CRM, update tags after a form submission or start a follow-up step after a booking. In Make, an automation is called a scenario. Modules look up data or perform an action; a trigger starts the scenario.
What do you need?
A Make account with access to the FITsociety app.
A FITsociety account with access to the company you want and the permissions needed to manage an integration.
A test member and a mailbox you manage yourself.
This guide applies to the FITsociety app you have been given access to. Don't see the app in Make? Ask the FITsociety helpdesk for access to the private app and the available app link. Make's features and usage limits also depend on your Make plan.
Set up the connection
Open a scenario in Make and add a FITsociety module.
Under Connection, create a new connection. Give it a recognizable name, for example your company name.
Sign in to FITsociety in the window that opens.
Choose the company you want to connect. If you have one suitable company, it may already be selected.
Check the access requested. Health-related data and private events may require additional consent. Read the explanation and give consent deliberately.
Confirm the access and return to Make.
With this sign-in flow, you don't need to enter an API key, client ID or client secret yourself. The connection renews access automatically as long as the consent and access remain valid. Has the sign-in request expired? Start connecting again from Make.
Use the right company
Each connection belongs to the company you chose while connecting. Search fields and actions use that company's data. Want to connect a second company? Create a separate connection for it and give both connections a clear name.
Test safely first
Start with a read module that retrieves a test member. Choose Run once and check the result. You can map fields from this output to a next module; in Make this is called mapping.
Test write actions with fictional data. Invitations, member links and scheduled communication can trigger real emails or notifications. So check both the Make output and the result in FITsociety. Only switch the scenario to automatic once the input and outcome are correct.
For instant triggers, you also create a webhook. Read Start an automation with FITsociety triggers in Make.