Is this a bug with Make.com or am I missing something?

Questions
1

:bullseye: What is your goal?

Trying to compare 2 strings with a 'Text operators: equal to" operator.I just want to compare strings.

:thinking: What is the problem & what have you tried?

I have several examples of the function returning TRUE and FALSE when comparing NEWBUSINESSQUOTED and NEWBUSINESSISSUED, and CANCELLATIONCANCELLED and NEWBUSINESSISSUED. So, is this simple string operator just unreliable??? Incredibly frustrating.

:clipboard: Error messages or input/output bundles

So, when NEWBUSINESSQUOTED gets fed in to be checked if equal to NEWBUSINESSISSUED, it will sometimes pass, and other times it won’t pass. You can see in my screenshots below how a string with the word QUOTED in it was somehow equal to NEWBUSINESSISSUED.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

quoted.png

2

Welcome to the Make community!

We’d love to help, however, we require more information that demonstrates the problem to help us reproduce the scenario and any issues and errors.

To allow others to assist you, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario, and the zoomed in parts of the scenario that you are referring to (if your scenario is huge),
  • a full scenario run/execution from the history (showing output “speech” bubbles),
  • relevant module fields (showing how you’ve used any built-in functions, and how you’ve mapped the variables),
  • relevant filters between modules (showing which operators and any built-in functions you’ve used, and how you’ve mapped the variables),
  • relevant module input/output bubbles,
  • if applicable, any error messages,
  • and if applicable, any external services (spreadsheet headers/ sample data/ regex101.com/ etc. to show the item/ record exists, and is set up correctly).
Need help❓View instructions ◀

Uploading Attachments

  • You can upload files and images to this forum by clicking on the upload button:

    Uploading a file attachment here will look like this:
    blueprint.json (12.3 KB)

We would appreciate it if you could upload screenshots here instead of linking to them outside of the forum. This allows us to directly zoom in on the image when clicked, and also having improved privacy from third-party sources.

2. Scenario Blueprint

Providing your scenario will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return. This would benefit you in implementing our suggestions as you can view screenshots of the changes or paste corrected modules back into your scenario.

Need help❓View instructions ◀

A. Export Blueprint

To export your scenario blueprint, click the three dots at the top-right of the scenario editor then choose “Export Blueprint”.

  • You can upload files and images to this forum by clicking on the upload button:

    Uploading a file attachment here will look like this:
    blueprint.json (12.3 KB)

B. Create Public Share Link

You can also share your scenario by creating a public share link.

3. Module Output Bundles

Please provide the output bundles (input bundles are not so crucial) of each of the relevant modules by running the scenario, or get output bundles from a previous scenario run from the “History” tab.

Providing the output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections), especially if external services are involved, and help you with mapping the raw property names from collections.

Need help❓View instructions ◀

Click on the white speech bubbles on the top-right of each module and select “Download output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor as a bundle.txt file. Open the file to check if it has not added additional formatting or encoded the plain text.

  • You can upload files and images to this forum by clicking on the upload button:

    Uploading a file attachment here will look like this:
    output-bundle.txt (12.3 KB)

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the bundles AND format them correctly.

:warning: Formatting IS Important! :warning:

Here are some ways to provide text content in a way that it won’t be modified by the forum.

  • Method 1: Type code fence manually —
    Manually type three backticks ``` in a separate line before and after the content, like this,

    ```
text goes here
```

  • Method 2: Highlight the pasted content, then click the preformatted text/code button —

  • Method 3: Upload your file elsewhere and share the public link —
    This method is only advised for large files exceeding the forum upload limit.

Sharing these details will make it easier for others to assist you, so that you can get better answers, faster.

Hope this helps! If you are still having trouble, please provide more details.

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!

3

Not a Make bug, the equal-to check is strict. Hidden spaces/line breaks in your data cause the mismatch. Trim both values before comparing and it works fine.

4

Hey Moid, in the screenshot I’ve provided, I show a match. Where a string with containing the string ‘QUOTED’ is somehow equal to NEWBUSINESSISSUED (which, doesn’t even contain the word QUOTED). Any ideas?

5

This usually happens in Make when the value you are comparing is not actually a clean string, even though it looks like one in the inspector. In most cases the field coming in isn’t a plain text value — it may be an object, an array, or a quoted wrapper, and Make is auto-converting it during evaluation. That’s why a value containing “QUOTED” can sometimes evaluate as equal to “NEWBUSINESSISSUED”: Make is comparing the underlying raw value, not the displayed inspector text.

To fix it, force both sides to become true strings before comparison. Add a Text → “Convert to string” or wrap the mapped value inside the {{toString(...)}} function. When both inputs are real strings, the “Text operators: equal to” condition becomes fully reliable.

In short: it’s not the operator that is unreliable — it’s the incoming value format. Converting both sides to clean strings will make the comparison behave correctly every time.

6

I don’t think this is the issue. To investigate further we’ll need the information I requested above. Otherwise, please contact support.

If you are still having trouble, please provide more details.

— @samliew