Connections

APIs usually use authentication or authorization to limit access to their endpoints.

Make provides you with a list of the most common types of connections with prefilled code that can be edited for your needs. In general, you will need to change the URLs and names of the parameters.

Create a new Connection panel

Types of connections

Common data

When you use an OAuth connection, an ID and secret are generated for your user. To store them, you should use the common data inside the connection.

Once the app is approved, the common data is locked and can't be changed due to security reasons.

Inside the connection, common data can be accessed by the common.variable IML expression.

Common data is encrypted when stored in Make.

Reserved words in connections

Reserved words are variables used internally by Make. Using reserved words for the parameter name key can lead to unexpected results. Avoid using a reserved word.

Make reserved words are:

  • accountName: name of the connection used by the app module,

  • teamID: ID of the team to which the active user is currently assigned.

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.

[
    {
        "name": "apiKey",
        "type": "password",
        "label": "API Key",
        "editable": true,
        "required": true
    },
    {
        "name": "accountName", // reserved word used here!
        "type": "text",
        "label": "Account name",
        "editable": true,
        "required": true
    }
]

The code 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