Discover features to manage organization usage and members.

Monitor operations, errors, and execution metrics across your scenarios to optimize performance.

Set credit limits for teams to control consumption and pause scenarios when limits are reached.

Delete all your user data stored on Make including scenarios, connections, and personal information.

Set session timeout to automatically log out inactive users. 

Monitor user activity across your organization or team.

Enable or disable experimental and AI features across your organization.

Enforce two-factor authentication (2FA) for your organization (Enterprise plans only). 

Enable, manage, and view private spaces in your organization. 

Analytics dashboard

Credits per team management

Delete user data

Set the length of your session timeout

Audit logs

Feature controls

Two-factor authentication enforcement

Private spaces

Request sales tax exemption

Administration

A safety feature that saves unfinished scenario runs when errors occur, preventing data loss. Stored in the Incomplete Executions tab, you can retry automatically, resolve manually, or delete them. Disabled by default, enable it in Scenario settings.

Incomplete_executions

incomplete_executions

Error handlers act as a safety net that catches unexpected failures to prevent your scenarios from failing. They allow you to define exactly how the system should react, such as by retrying the task, ignoring the mistake, or rolling back changes.

error_handler

The Rollback error handler stops a scenario and reverts changes made by modules that support transactions to ensure data remains consistent when an error occurs.

Rollback

An automated workflow within the Make platform. You build it by connecting modules together, and it runs based on a trigger you set up.

scenario

a list or sequence of characters (like letters, numbers, and symbols) used to represent text in a computer programming.

string

An operation is a single module run to process data or check for new data. 

Operations

Credits (formerly operations) are the currency for running scenarios.

Credits

A route is a path that data can flow through in a scenario, visualized as the dotted lines between modules.

Route

scenario_plural_lowercase

scenario_singular_lowercase

Scenario_plural

Scenario_singular

product_name

Help Center

What is Make?

What's an API?

What's a scenario and which type should you use?

Learn the basics

Step 1. Plan your scenario

Step 2. Get your apps ready

Step 3. Add your first app

Step 4. Create a connection

Step 5. Set up the trigger

Step 6. Test the module

Step 7. Add another module

Step 8. Map data

Step 9. Test your scenario

Step 10. Schedule your scenario

Create your first scenario

Step 1. Get your app ready

Step 2. Add a router

Step 3. Set up another module

Step 4. Add a filter

Step 5. Test your scenario

Step 6. Add an aggregator

Step 7. Test the final scenario

Expand your scenario

Get started

Credits & operations

Connect an application

Schedule a scenario

Clone a scenario

Delete a scenario

Active and inactive scenarios

Scenario execution flow

Scenario history

Scenario blueprints

Scenario templates

Scenario sharing

Scenarios & connections

Introduction to Make apps

Types of modules

Module settings

Update legacy modules with new modules

Webhooks

Select the first bundle to process

Apps & modules

Item data types

Type coercion

Mapping

Filtering

Mapping arrays

Working with files

Data & mapping

Aggregator

Iterator

Router

Tools

Keyboard shortcuts

Resources

Canvas interaction model

Key concepts

Search for scenarios and scenario runs

Scenario settings

Scenario notes

Scenario inputs and outputs

Subfolders

Labels

Subscenarios

Create and manage scenario templates

Custom scenario properties

Variables

Incomplete executions

Scenario execution, cycles, and phases

Restore and recover scenario

Undo and redo scenario changes

Scenario run replay

Scenarios

Call Google APIs with OAuth 2.0 HTTP request

Connect to any web service using OAuth 2.0

Connect to Google services using a custom OAuth client

Replace connections across multiple modules

Manage connection and key usage notifications

Credential requests

Dynamic connections

On-premise agent

Devices

Keys and certificates

Allow connections to and from Make IP addresses

Connections

If-else and Merge

Flow control

Converger

Text parser

Use functions

General functions

Math functions

Math variables

Text and binary functions

Date and time functions

Tokens for date/time parsing

Tokens for date/time formatting

Array functions

Custom functions

Functions

Methods of securing data

AES (Advanced Encryption Standard)

PGP (Pretty Good Privacy)

Digital signature

Hash functions

Securing data with Make

Data stores

Data structures

Make DevTool

Developers

Explore more

Introduction to Make AI Agent (New)

Create your first AI agent

Sales outreach AI agent use case

Slack-triggered AI agent

Telegram-triggered AI agent

Email-triggered AI agent

Form-triggered AI agent

Webhook-triggered AI agent

Mailhook-triggered AI agent

Create AI agents for different triggers

Input files for AI agents

Knowledge files for AI agents

Knowledge app modules

Input files and knowledge files for AI agents

Make AI Agent (New) app

Make AI Agent (New) best practices

Credit usage for AI agents

Make AI Agent (New)

Introduction to AI agents

Manage AI agents

Module tools for AI agents

Scenarios for AI agents

MCP tools for AI agents

Tools for AI agents

AI agent best practices

AI Agents configuration

Make AI Agents app

Step 1. Set up the AI agent

Step 2. Create the AI agent's tools

Step 3. Create a scenario to send tasks to the AI agent

AI agent use case

Make AI Agents

Introduction to MCP

Get started with Make MCP server

Make MCP server

Connect to Claude Desktop

Connect to ChatGPT

Connect to Cursor

Connect to OpenAI

Connect to OpenAI API

MCP toolboxes

Make Skills

Model Context Protocol

Introduction to Make Grid

Access Make Grid

Explore Make Grid

How to use Make Grid

Make Grid