Difficulty Saving Scenarios in Shared Organization Account

[Loujain]

Hello,

I’m reaching out for assistance with an issue I’m facing on Make.com. I’ve been invited by an organization to collaborate on their Make account, and I’ve imported a scenario into their workspace. However, I’m encountering a problem: I cannot save the scenario because it requires the organization’s team members to log in first. Unfortunately, they are unable to see the scenario in their account until it’s saved.

I’ve been also invited as an app developer, but that role doesn’t grant me the ability to create or manage scenarios. I’m wondering if anyone has encountered a similar issue and can provide guidance on how to properly set this up so that the scenario is visible and manageable by the organization’s members.

Thank you in advance for your help!

Best regards,

Loujain

[samliew]

Welcome to the Make community!

You can use the Make DevTool Chrome extension to enable “Showcase” mode. This will allow you to save the scenario even if some required fields and connections in modules have not been set-up yet.

From Make DevTool - Help Center :

Make DevTool allows you to debug your Make scenarios by adding an extra pane to the Chrome Developer Tools. Using this new debugger pane, you can check all the manual runs of your scenarios, review all the performed operations, and see the details of every API call performed. Additionally, with Make DevTools you can see which module, operation, or response caused an error in your scenario. This helps you debug your scenario and get your scenario back on track.

I hope this information assists you. Don’t hesitate to respond if you require more help.

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

[Loujain]

Hi,

Thank you so much for your help! I have also an problem. I’m building a chatbot that has two separate flows. Both flows send user info (name, email, etc.) to the same Make webhook.

In Make, I use a router to send the data to two different email modules.
However, when I test it, I receive mixed information — both flows details in the same email.

How can I make sure that when someone goes through the one specific flow, it only triggers that specific email, and when they go through the other flow, it goes to the other email?

Thanks in advance for your help!

[samliew]

No problem, glad I could help with "Difficulty Saving Scenarios in Shared Organization Account"!

1. Which was the most helpful post in this thread?

The Make Community guidelines encourages users to try to mark helpful replies as solutions to help keep this forum organised.

This marks the topic as solved, so that others can:

• save time when browsing the latest activity on the forum, and
• quickly jump to the solution in this topic

To do this, simply click the checkbox at the bottom of the post that is the most helpful in answering your question.

Here’s a magic link to a list of your other “unsolved” topics: status:unsolved

2. Have you learnt something new?

Do bookmark this topic so you can easily find and return to this topic in future.

Here’s a magic link to a list of your bookmarks /my/activity/bookmarks!

3. Have a different/follow-up question? Start a new topic.

Creating a new topic for each question makes it easier for others with the same problem to search for answers. You are also more likely to receive help sooner as new topics are displayed first on the forum’s “new” page!

— @samliew