Tables in Make
The make plugin includes 16 tables:
Name | Description | Queries |
---|---|---|
API tokens of the currently authenticated user. | ||
For most apps included in Make, it is necessary to create a connection, through which Make will communicate with the given third-party service according to the settings of a specific scenario. | ||
Data Stores are used to store data from scenarios or for transferring data in between individual scenarios or scenario runs. | ||
Functions in Make allow you to transform data. You use functions when mapping data from one module to another. Make offers a variety of built-in functions. On top of that, you can create your own custom functions. | ||
Webhooks allow you to send data to Make over HTTP. Webhooks create a URL that you can call from an external app or service, or from another Make scenario. Use webhooks to trigger the execution of scenarios. | ||
Organizations are main containers that contain all teams, scenarios, and users. | ||
Organization Variables are user-set variables you can use in your scenarios. | ||
Scenarios allow you to create and run automation tasks. A scenario consists of a series of modules that indicate how data should be transferred and transformed between apps or services. | ||
If a scenario terminates unexpectedly because of an error, then the scenario run is discarded. You can set the scenario to store the failed scenario run as an incomplete execution. With that, if an error occurs in your scenario, you can resolve it manually and avoid losing data. | ||
Scenario Logs allow you to explore past runs of your scenarios. | ||
Teams are containers that contain scenarios and data accessible only by the members of the team. | ||
Team Variables are user-set variables you can use in your scenarios. | ||
Existing Users within your account, and their attributes. | ||
Users within your account. | ||
User roles usable for users within your Organizations and Teams. The column `category` signifies where the role can be used. | ||
Users within your account. |