Connections
APIs usually employ some sort of authentication/authorization to limit access to their endpoints.
Make platform provides you with a list of the most used types of connections while in every each there is a code prefilled. You only need to edit it up to your and/or API's needs.
Mostly, you will need to change the URLs and names of the parameters.
Types of Connections
pageBasic connectionpageJWTpageOAuth 1.0pageOAuth 2.0Common data
When you're using an OAuth connection, an ID and secret are generated for your client. To store them you should use the common data inside the connection.
Make sure nobody else knows the client secret, otherwise your app can get vulnerable.
Once the app becomes Approved, the Common Data gets locked and it can't be changed anymore due to security reasons.
Inside the connection, common data can be accessed by common.variable IML expression.
When you need the common data to be available to all modules, use Apps common data instead.
Common data are stored in encrypted form in Make.
Reserved Words in Connections
Reserved words are variables used internally by Make platform. Using reserved words for the parameter name key can lead to unexpected results. Avoid using a reserved word If you don't have a clear intention of why you want to use it.
Make reserved words are:
accountName: name of the connection used by the app module,teamID: ID of the team to which active user is assigned currently.
If you use a Make reserved word for the name key of a parameter, the value stored in the internal Make parameter will be used by your parameter too.
Consider the following configuration of a connection. The parameter labeled Account Name has his name key set to preserved word accountName.
The setting above leads to mirroring the value from the default Connection name parameter into a parameter labeled Account name. The value accountName is set by Make to the name of the created connection.
Last updated
