As we move ahead into 2024, we’ve got some exciting news to share with you!
From today, Dynamic Connections in Make will transform the way you set up modules with specific connections!
No more manual headaches - this capability eliminates pain points for scenario designers by allowing a seamless transition between, for instance, Salesforce sandbox and production or managing multiple scenarios for different user connections.
Advanced Makers who are experienced in lifecycle management and various environments will find this capability to be a game-changer.
Key benefits
Design scenarios that effortlessly adapt to context.
Easily make connection changes and troubleshoot during design.
Create API-executable scenarios with diverse connections.
If you’re an Enterprise user, now’s the perfect time to log into Make and try Dynamic Connections out for yourself!
Helpful Resources:
Check out the guide in the Help Center Explore the possibilities of Dynamic Connections on our blog
@samliew your level of awareness is truly incredible! I just came in to add a link to the blog post to the announcement and here you are, already on top of it.
Is Dynamic Connections the solution to this scenario:
I have 20 customers.
Each customer has a CRM and a Zoom account.
Each customer sends webinar registrations from their CRM to their Zoom account.
At the moment I have to build 20 copies of the scenario, which are all identical apart from the Zoom accounts they’re connected to.
Will this let me build a single scenario and route the webinar registrations to the correct Zoom account by including the connection to use in the input data?
If so, that would streamline and simplify my operations enormously.
Final question: can the Enterprise plan ever be affordable for a small business? I’m currently on Teams and would be upgrading just for this one feature. But I’m not a corporation; I can’t justify “speak to a salesperson” levels of monthly subscriptions.
I think your situation would be a great fit for Dynamic Connections. On the affordability question, I guess it comes down to the business value for you vs. the expected cost.
One alternative route that would simplify your workflow is to automate the creation of the additional customer-specific scenarios yourself. It should be possible to use the Make App (and some of the additional Make API endpoints for connection creation) to automatically create a scenario with the appropriate connections.
You’d still have the problem of maintaining multiple scenarios if things changed. But you could possibly minimize that by splitting up your scenarios so that the customer-specific parts were separate and invoked by HTTP/webhook. That way you could maintain the non-specific parts as single scenarios.
It would be complex - but that’s the trade off. Whether it’s worth it depends on how big a problem you find it in the first case!
As we move ahead into 2024, we’ve got some exciting news to share with you!
Key benefits
Check out the guide in the Help Center
