Best practice on accounts for connections

I am going to be leaving my current organisation soon, and I am trying to put together an orderly handover. Part of this will be ensuring that all scenarios in Make.com can continue to run.

Some of the connections used in scenarios have been set up under my personal account. I will obviously need to change these to use another account.

I just wondered if anyone had any ‘best practice’ tips for how to go about doing this with minimal pain - for instance I was thinking of setting up a new make@company.com email address that could be used to create accounts for various services with.

Anyone with any experience of this they could share?

Hi there. Always best practice (in my view) to “Start with the End in mind” as they say. So when you’re beginning any project, use an email alias or email account that is independent of any one user. Just like you say in your example, we’ve used api@ or make@ on the client’s domain to setup accounts and then build the connections. That way, when we leave the project the connections won’t immediately break!

This is a common troubleshooting area. Client: “Hey we had to let Mike go, but now our automations are all broken. Help!”. Anything we can do to avoid that is good.

Good luck on your next adventure! Maybe you’ll become a Make Partner one day…

2 Likes