Prepare your Make account

To use Make Bridge, you will need to set up a Service User account within your Make organization, obtain an API key, and prepare the type of sandboxing you require for your users.

To get started, you will need a Make account with the Make Bridge plan.

Set up a Service User account

We recommend that you create a Service User account that will be used as a management entity for your users’ automations. Using a Service User account ensures that Make Bridge will not be attached to a personal account within your organization. In the Make platform, actions of your users will be interpreted as actions of the Service User.

To create a Service User account:

1

Log in to Make and select the organization where you want to create your Service User account.

2

Under the Users tab, click + Invite a new user.

3

Enter the Email for this account.

4

Enter the Name for this account. We recommend entering the name Service User.

5

For the Role, select Admin.

6

Optional: Add a note.

7

Click Save.

Obtain your Service User account API key

An API key is required to integrate Make Bridge into your product and initialize the flow. This API key should be created using the Service User account.

To create an API key:

1

Log in to Make using your Service User account credentials.

2

At the bottom of the left sidebar, click Profile icon > Profile.

3

Under the API Access tab, click Add token.

4

Enter a Label to identify the use of this token.

5

Select your required Scopes:

Actions
Scopes

Working with connections:

connections:read

connections:write

Working with webhooks:

hooks:read

hooks:write

Rendering the forms in the flow:

imt-forms:read

Working with keys:

keys:read

keys:write

Reading details of the organization, checking permissions and licenses, etc.:

organizations:read

Working with scenarios:

scenarios:read

scenarios:write

Managing the teams:

teams:read

teams:write

Working with templates:

templates:read

templates:write

Retrieving data of the System User:

user:read

Working with the instancing flows:

instances:read

instances:write

6

Click Save.

7

The new key will appear on this profile's API Access dashboard. Copy the API key to your clipboard and store it in a safe place, as it will not be shown again.

Prepare user-level or team-level sandboxing

Depending on your users’ requirements and how you wish to divide data, you can set up user-level or team-level sandboxing. As actions in Make pertaining to integrations will be interpreted as actions of the Service User, sandboxing is how you can identify which automations are related to your specific users.

User-level sandboxing is the best option if you want every user to have their own set of integrations that are not seen by others. Team-level sandboxing is preferred if you want integrations, connections, and webhooks to be shared with others who are within the same context.

We recommend creating a special team, using the Service User account, that you will use to develop and test the users' templates.

Last updated