How to Use Custom Scenario Properties in Make.com

Custom scenario properties in make.com let you define configuration values for a scenario without hard-coding them into modules. This guide explains how to create, manage, and use these properties so your automations are easier to maintain and reuse.

What Are Custom Scenario Properties in Make.com?

Custom scenario properties are name–value pairs stored at the scenario level. They work like configuration variables that you can reference across modules, routers, or error handlers.

They are useful when you need to:

• Store API keys, IDs, or environment-specific values.
• Switch between testing and production settings quickly.
• Reuse the same value in multiple modules.
• Update configuration without editing every individual module.

You can manage these properties directly from the scenario editor interface.

Accessing Scenario Settings in Make.com

Before you work with custom scenario properties, open the scenario where you want to use them.

1. Log in to your make.com account.
2. Open the desired scenario from your dashboard.
3. Click the scenario name or the settings icon in the scenario editor.

The scenario settings panel is where you will find and manage custom scenario properties.

How to Create Custom Scenario Properties in Make.com

Creating new custom properties in make.com is straightforward. Follow these steps from the scenario editor.

Step 1: Open the Custom Scenario Properties Panel

1. In the scenario editor, look for the settings section.
2. Open the Scenario settings or equivalent configuration area.
3. Locate the Custom scenario properties section.

This panel lists all existing properties and lets you add new ones.

Step 2: Add a New Property

1. Click Add or the + button in the custom scenario properties section.
2. Enter a clear, descriptive name for the property (for example, base_url or default_email).
3. Enter the value you want to store.
4. Confirm or save the property.

Each property becomes a configurable field you can reference later in any compatible module within the scenario.

Step 3: Organize and Name Properties Effectively

To keep your make.com scenarios easy to manage, follow these naming and organization tips:

• Use lower_snake_case or similar consistent naming.
• Group related properties with a prefix, such as crm_ or mailing_.
• Avoid generic names like value1 or test.
• Document the purpose of each property in an internal note or documentation tool.

Editing and Deleting Properties in Make.com

You can change or remove custom scenario properties at any time. This is useful when you rotate credentials or switch between environments.

How to Edit an Existing Property

1. Open the Custom scenario properties section in the scenario settings.
2. Locate the property you want to edit.
3. Click into the property’s name or value field.
4. Update the value as required.
5. Save or confirm the changes.

All modules that reference this property will start using the new value the next time the scenario runs.

How to Delete a Property

1. Open the Custom scenario properties section.
2. Find the property you want to remove.
3. Click the Delete or trash icon next to the property.
4. Confirm the deletion if prompted.

Before deleting, check that no module still depends on this property. Removing an in-use property can cause module errors at runtime.

Using Custom Scenario Properties in Make.com Modules

After defining properties, you can reference them in modules across your scenario. This lets you centralize configuration and avoid repetitive manual edits.

Inserting Properties into Fields

1. Open a module in the make.com scenario editor.
2. Click into a field that supports mapping or dynamic values.
3. Open the mapping panel or variable browser.
4. Look for the section listing Custom scenario properties.
5. Select the desired property to insert it into the field.

When the scenario runs, make.com resolves the property to its stored value.

Typical Use Cases

You can apply custom scenario properties in many situations:

• API endpoints: Store the base URL or endpoint path and reference it in HTTP modules.
• Authentication values: Keep tokens or keys as properties (when supported) instead of hard-coding them in each call.
• Default recipients: Set default email addresses used by email or notification modules.
• Feature flags: Use properties to toggle certain branches on or off by evaluating property values in filters or routers.

Best Practices for Make.com Scenario Configuration

Well-structured custom scenario properties make your automations easier to maintain and debug.

• Centralize configuration: Place every reusable value in a property rather than duplicating it in modules.
• Use clear naming: Indicate type or purpose in the property name, like webhook_secret or report_frequency_days.
• Review regularly: Clean up unused properties to keep the scenario configuration tidy.
• Test after changes: When you update property values, run the scenario manually to confirm that all modules behave as expected.

Where to Learn More About Make.com Features

You can find the original reference for custom scenario properties in the official documentation at this make.com help page. It contains the most up-to-date details about available options and interface behavior.

For broader automation strategy, optimization, and implementation help, you can also visit Consultevo, a site focused on automation consulting and scenario design.

Summary: Streamline Configuration in Make.com

Custom scenario properties help you separate configuration from logic inside make.com scenarios. By defining reusable properties, referencing them in modules, and managing them from the scenario settings, you reduce duplication and simplify maintenance. Use them to store endpoints, IDs, defaults, and other key values so your automation projects remain flexible, clean, and easy to update.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help