How to import a blueprint into Make.com
Importing takes about four clicks. Almost everything that goes wrong happens afterwards, in the connections, so most of this is about that part.
A blueprint is a JSON file describing a Make.com scenario: its modules, how they are wired together, and how each one is configured. Importing one rebuilds that scenario in your account without you placing a single module by hand.
The import itself takes about four clicks. Almost everything that goes wrong happens afterwards, in the connections, so most of this is about that part.
The import
Open Make.com and go to Scenarios. Click Create a new scenario. In the empty canvas, find the three dots at the bottom of the screen and click them. Choose Import Blueprint, then pick the .json file. Save.
That is it. The scenario appears complete, with every module in place and every filter and router already configured.
The connections are not included, and that is deliberate
Every module that talks to an outside service needs a connection: your Gmail, your Google Sheet, your Stripe account. Those are not in the blueprint file and they cannot be.
A Make connection holds an access token to a real account. If blueprints carried them, buying one would mean receiving somebody else's credentials, and sharing one would mean handing yours over. Any blueprint that appears to arrive with working connections attached should worry you.
So after importing, open each module with a warning triangle and either pick an existing connection or create one. This is the part the setup guides in every Kettleford product spend most of their pages on, module by module, because it is the part where knowing what a field is for actually matters.
Two errors that catch people out
The first is a module that will not open, or opens with fields missing. This usually means the blueprint was exported from a newer version of that app module than your account is offering, or the app has since changed. Delete that one module and add it again from the app list, then re-map its fields. The rest of the scenario stays intact.
The second is a webhook that appears to be there but never fires. Webhook URLs are unique to the account that created them, so an imported webhook module needs a new hook created inside your own account. Click the module, create a new webhook, and then update whatever sends to it with the new address.
Test before you connect it to anything real
Run the scenario once, manually, against test data. Then open the execution history and read what each module actually received and sent. Make shows you the full payload at every step, which is the single most useful debugging tool on the platform and the one people forget exists.
Only once you have seen it do the right thing with a fake order should you point it at a real one. Every Kettleford setup guide says this on its first page, and it is the advice most worth repeating.
Questions
Where is the Import Blueprint option?
At the bottom of the scenario editor, behind the three dots, on a new empty scenario. It is not in the Scenarios list and not in the module picker, which is why people miss it.
Why does every module show a warning triangle after import?
Because none of them has a connection yet. That is expected. Open each one, pick or create a connection to your own account, and the triangle goes away once the module can reach the service.
The scenario imported but the webhook never fires. What is wrong?
The webhook address in the blueprint belonged to the account that exported it. Create a new webhook inside your own account from the module, then paste the new address into whatever is meant to send to it.
