How to Use the Make.com Converger Step by Step

The Converger tool in make.com lets you merge data coming from parallel branches into a single, ordered flow without writing code. Understanding how it behaves is essential for building reliable, predictable scenarios that work correctly even when multiple routes run at the same time.

This guide explains what the Converger does, how to configure it, and how it behaves in common automation patterns so you can design stable, efficient workflows.

What the Make.com Converger Does

The Converger in make.com is a special module that synchronizes branches in a scenario. After a router splits your flow into several routes, the Converger lets you:

• Join multiple branches back into one stream.
• Control the order in which merged outputs are processed.
• Avoid duplicate or missing results when branches run in parallel.
• Decide whether incomplete sets of results should continue or be discarded.

In simple terms, each Converger watches the tokens (bundles) that arrive from each incoming route and then emits a new token only when the conditions you set are met.

Core Concepts Behind the Make.com Converger

To use the Converger effectively in make.com, you need to understand several internal concepts that guide how tokens are grouped and processed.

Tokens and Token Set ID

A token represents an item of data moving through your scenario. When a router splits the flow, each branch gets its own tokens. The Converger groups tokens into logical sets using a value called the Token Set ID.

• Tokens with the same Token Set ID belong to one logical group.
• The Converger waits for tokens from each route that share the same Token Set ID.
• If the Token Set ID is blank, the Converger falls back to scenario run identifiers or order of arrival.

You define the Token Set ID using a mapping field on the Converger module. This can come from a field of an incoming bundle or a custom expression.

Routes and Membership

Each incoming path connected to the Converger is a route. The Converger specification lets you decide which of these routes are considered members of a token set for a particular Token Set ID.

Only the routes you select participate in the convergence logic, so you can have some branches that bypass the Converger entirely while others must be synchronized.

When a Token Set Is Complete

A token set is complete when the Converger has received at least one token from each selected route for the same Token Set ID. How the Converger reacts to incomplete sets depends on your configuration, especially the condition field and timeouts.

Configuring the Make.com Converger

When you add a Converger in make.com, you will see several key settings. These determine how tokens are grouped, how long the Converger waits, and what happens if data is missing.

1. Set the Token Set ID

Use the Token Set ID field to define how tokens are grouped:

1. Open the Converger module.
2. In the Token Set ID field, map a value that is common across related tokens (for example, an order ID or customer ID).
3. Ensure each branch provides this value so all related tokens share the same identifier.

If you do not specify a Token Set ID, the Converger uses the scenario run or internal identifiers, which may not match your intended grouping.

2. Choose Member Routes

Select which incoming routes participate in each token set:

1. Locate the list of routes connected to the Converger.
2. Check the routes you want to consider as members.
3. Uncheck any route that should not be required for a complete token set.

Only member routes are counted when determining whether a set is complete.

3. Define the Condition

The condition tells the Converger when to produce an output. You can:

• Require that tokens from all member routes arrive.
• Specify logical conditions on data fields (for example, proceed only when a status equals “approved”).
• Skip or discard sets that do not meet your criteria.

Configure the condition carefully so that the Converger emits a token only when the data from each branch is valid and complete.

4. Configure Timeouts and Cleanup

To avoid holding incomplete sets forever, configure the Converger timeout behavior:

• Set a time after which incomplete token sets are considered expired.
• Decide whether expired sets should be discarded or passed through with partial data (if supported by your scenario design).
• Use this setting to prevent scenarios from accumulating stale or unusable token sets.

How the Make.com Converger Processes Tokens

The internal behavior of the Converger in make.com determines the order of tokens and what happens when new tokens arrive. Understanding this flow helps you debug complex scenarios.

Receiving and Grouping Tokens

When a token reaches the Converger:

1. The module reads the Token Set ID value.
2. It checks whether a token set with this ID already exists.
3. If not, it creates a new set and adds the token from the current route.
4. If yes, it merges the token into the existing set.

This process continues for each route and each Token Set ID until the set is marked complete or expired.

Emitting Output Tokens

Once the token set is complete and the condition is satisfied:

• The Converger emits a new token that aggregates or references the incoming tokens.
• This output token moves on to the next module in the scenario.
• The original raw tokens remain part of the history but the Converger treats the set as finished.

If another token later arrives with the same Token Set ID, the Converger may create a new version of the set, depending on its configuration and the timing.

Handling Late or Missing Tokens

Late or missing tokens can appear when one route is slower than others or when a branch fails. The Converger handles these cases according to your timeout and condition settings:

• If a token arrives after the set has been emitted, a new set can start for the same Token Set ID.
• If the set times out before all tokens arrive, the Converger either discards it or processes partial data, based on your design.
• Careful timeout configuration prevents memory growth and logical errors.

Best Practices for Make.com Converger Usage

To get reliable results from the Converger in make.com, follow these recommendations.

Use Stable Token Set IDs

Always map a stable, deterministic Token Set ID:

• Use IDs that do not change across branches, such as record IDs or reference numbers.
• Avoid values that can differ between routes, like timestamps or random strings.
• Verify that every branch feeding the Converger provides the same logical identifier.

Avoid Unnecessary Routes in the Converger

Include only routes that must be synchronized:

• Do not add branches that produce optional or unrelated data.
• This reduces the risk of incomplete sets and simplifies debugging.
• Use separate Convergers for distinct synchronization needs.

Monitor Scenario Runs

Use the scenario run history in make.com to inspect how token sets behave:

• Look at which routes contributed to each Converger output.
• Check for expired or discarded sets when debugging missing data.
• Adjust Token Set ID mapping if sets do not group as expected.

Learning More About the Make.com Converger

For the most up-to-date and detailed behavior description of the Converger feature in make.com, always review the official documentation. You can read the original reference article at this Converger documentation page.

If you need expert help designing complex converger setups or optimizing automations that rely on make.com, you can also consult specialized automation experts such as Consultevo, who provide consulting, troubleshooting, and scenario architecture services.

By carefully setting your Token Set ID, route membership, conditions, and timeouts, the Converger in make.com becomes a powerful control point that keeps parallel branches in sync and ensures that your automations run in a predictable, maintainable way.

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