What is your goal?Transferring an automation to, for example a business
What is the problem & what have you tried?Just curious about how it works when it comes to sending a system to either a user or a company that would make use of it. When it comes to credits, assuming it will always be running off of them, will the system always be linked to my account and just run there requests off of my account?
Hi @Zach ,
From what I understand, you’re asking how the credit and ownership system works when handing off a built automation to a client or business - specifically whether it stays tied to your account or not.
The cleanest way to hand off a scenario is to export it as a blueprint (a .json file) and have them import it into their own Make account. Once they do that, it runs entirely off their credits with no link to your account.
Just keep in mind they’ll need to reconnect all app integrations using their own credentials, and any webhook URLs will regenerate, so those will need to be updated on the sending service side.
If you keep it running on your account instead, then yes - it will always consume your credits, so you’d want to account for that in your pricing.
With regards,
Mohamed Jahar
Okay cool, so in the case they dont have an account and arent expected to create account i can just simply continue running there system through my account however i just need to implement all there credentials into my system?
Much appreciated, thanks mate!
You can use secure credential requests.