Instagram Comment and DMs

:bullseye: What is your goal?

I am creating an Instagram Auto reply and Private DMs Automation

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

Here, In Path-1 for auto reply on Comments, which is working properly but Path-2 for Private DMs , If someone comment ‘Interested’ and ‘Tools’, then a PDF link will be directly sent to their account. But here the filter is not working. Is anyone help me to do this?

:link: Create public scenario page

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

1 Like

Hi @VerbaliTongue ,

Unfortunately, we couldn’t see any filter applied in any of the routes in the blueprint you shared. Could you please recheck to see if anything was missed and share the updated blueprint again?

This will help us review the flow more clearly and assist you better.

Thank you for your understanding.

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation

1 Like

It doesn’t need to be a fallback route, since they are mutually exclusive. All the rest looks fine.

Isn’t it working? What’s the output of module 1 when you comment “Tools”?

Sounds like your filter isn’t triggering because it might be case-sensitive or expecting an exact match. Try using a “contains” or lowercase check for both ‘Interested’ and ‘Tools’ in the filter, that usually fixes this in Make.com scenarios.

1 Like

It doesn’t work, Actually here is not the module called ‘Send a message.’ that trigger the DM, I am using a MAKE free account. Is there any issue?

1 Like

Hi @VerbaliTongue ,

Could you please set the Fallback option from Yes to No and try again?

Setting a Fallback route with a condition will not work as expected, since fallback routes do not evaluate filters. Disabling the fallback and using proper filters on each route should resolve the issue.

Please refer to the attached screenshot for reference.

Have a try and please let us know how it goes.

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation

I’d double-check the filter logic by printing the incoming keyword to a variable right before the filter step, just to see if the text includes spaces or casing that might break the match. I’ve had filters fail just because the keyword came in with an emoji. While testing, I sometimes peek at comments with goonview.com since it loads stuff quickly, which helps confirm what the trigger should look like.