Pricing parameters

In Make you can choose from over 1000+ ready-made apps to integrate and automate workflows.

Make allows you to automate faster and at scale by integrating with one of 300+ public API endpoints of the Make platform.

Make enables you to build powerful scenarios with access to exclusive enterprise-grade apps, such as enterprise-grade ERP systems: Automation Anywhere, Coupa, Greenhouse Recruiting, Infor M3 Cloud, Microsoft Dynamics 365 CRM, NetSuite, SAP S/4HANA Public Cloud , ServiceNow, Workday Financial Management, and Workday Human Capital Management.

If this feature is enabled for your organization, you can activate all scenarios that include enterprise apps. Without this capability, you can see enterprise apps and build scenarios, but not activate or run them.

All enterprise apps are labeled as "premium tier 3" in Make.

The Analytics dashboard provides a comprehensive view of your account's critical metrics, allowing you to understand exactly what’s happening across all your scenarios for effective oversight and optimization.

Single sign-on (SSO) allows you to use your own provider of user account management, authentication, and authorization services to register and log in to Make.

You can control access to Make by setting up your own OAuth2 or SAML2 compliant Identity Provider (IDP). Single sign-on works with Okta, PingOne, Google, Azure, and dozens of others.

You can create public or team templates which are scalable across business functions and user groups. Learn more about templates.

Make enables you to create and install your own custom apps and share these custom apps with others in your organization.

Make team helps you when you have trouble with our product. We make sure that you are successful in solving whatever issues you come upon.

Pricing plans differ in priority when it comes to customer support.

Create your own Javascript functions and use them in scenarios to enhance Make's data transformation capabilities.

Add customizable metadata to your scenarios so you can organize them by the properties you create. For example, you can add information like a severity tier, client email, or a URL. Once added, you can use this information to filter and sort your scenarios.

Edit and manage your data across multiple scenarios at once.

Maximum storage capacity for all your data stores. Data stores represent persistent data storage and are a perfect tool for sharing and transferring data among your scenarios. Data is stored directly in your account, no registration at a third-party service is needed. You can have more than one data store, but the total amount of storage capacity will vary depending on your subscription.

Data transfer is the amount of data transferred through your scenario. Suppose you have a scenario that retrieves a 100kb image from FTP and reduces its size to 50kb and saves both images to Dropbox. The amount of data used in this scenario is 150kb.

The data moved between modules are counted only once, regardless of the number of modules deployed. The amount of data you have available depends on your subscription.

Access to a personal Make advisor who provides onboarding, adoption, and best practice sharing to help you achieve your unique business goals.

With this feature, you have exclusive access to a growing list of certified and experienced partners to support you with building workflows.

Full-text search for scenario execution history makes it easier to find the right scenario execution and troubleshoot more effectively.

Note: Enabling the full-text search is not retroactive. After enabling the full-text search, you can use the full-text search to find new scenario executions.

Execution log storage refers to the number of days that you can access detailed logs for every execution.

Note: Enabling execution log storage is not retroactive.

Hosting refers to the location where we host the infrastructure that Make runs on.

In incomplete executions storage scenario stores executions that were not successfully finalized due to an error. Each incomplete execution contains the scenario's blueprint and all the bundles that can be mapped into the failed module. See incomplete executions for further information.

Our information security team does a detailed security review to confirm compliance to standards such as ISO 27001 and SOC 2.

The maximum file size that can be automated and processed. The maximum size of a single file is limited according to your subscription.

Some modules can accept a file in their input and/or yield a file in their output. If the maximum file size is exceeded, Make proceeds in accordance with the settings of the enable data loss option. See working with files for further information.

The maximum number of scenarios that are active and running at one time. See active and inactive scenarios for further information.

Data stores represent persistent data storage and are a perfect tool for sharing and transferring data among your scenarios. You may think of one data store as a worksheet in a spreadsheet. See data store for further information.

The maximum time for which a single scenario can run. Maximum scenario execution time should not exceed 40 minutes for hosted version and 60 minutes for a private instance. See scenario execution, cycles and phases for further information.

Minimum interval is the shortest possible time in-between two successive scenario runs. You can set the interval in the schedule setting panel.

Make visual no-code workflow builder enables you to design, build, and automate using our drag-and-drop interface.

With the On-premise agent (On-prem agent) installed on your machine, your scenarios can access applications and databases on your local network without changing the settings of your firewall.

This feature permits you to go over your allocated operations limit without worrying that your scenarios will cease to operate.

This feature gives you the flexibility to purchase an annual package of operations upfront. Unused operations expire only after 12 months, so you don't have to worry about operations expiring every month.

In Core plan, you receive operations every month and they always expire at the end of the month. In Pro and Teams plan, you receive your operations at the beginning of the term so it is good to have a yearly plan to handle seasonality.

With parallel scenario executions, you can process multiple incoming items simultaneously, instead of one after the other.

In rare cases of high volume periods, Make executes your scenarios according to the priority of your plan tier to eliminate queuing time as much as possible.

Each organization is assigned an execution priority. This priority identifies the order in which executions take place during high-volume periods.

You can view executions happening in real-time from within your browser.

Allow everyone to run complex scenarios by just filling in inputs that are marked as required.

Scenario relations allow you to see which scenario is a parent, bridge or child scenario in a scenario chain when using subscenarios. Scenario relations also enable the scenario relations tab.

Get detailed information about your scenarios, current executions, teams, and organizations.

With this feature, you can create and manage an unlimited number of teams in a single organization. Team roles enable granular permission rights and controlled user access to scenarios applications, templates, and connections within the shared teams' folders.

Make your Make account more secure using two-factor authentication (2FA). 2FA means that there are two different factors (your Make credentials and an additional verification code) needed to authenticate you as a user when logging into your Make account.

You can have an unlimited number of users in your organization. With Make you can share access with users in your organization to collaborate on workflows.

All incoming webhooks are stored in a Webhook queue. The queue can start filling up when the scenario responsible for processing the webhooks is disabled (e.g. due to an error) or is processing the webhooks at a slower rate than they are being received. See instant triggers (webhooks) for further information.