A Make account runs your scenarios with the connections they use — Google, Slack, CRMs, payment and database accounts, each signed in once and kept there. Whoever has your Make password can read that data, change what the scenarios do or send it somewhere else. With 2FA on, Make also asks for the code from your authenticator when you sign in.
Enable two-factor authentication in Make
- Sign in to Make in Chrome on your computer.
- Click your profile icon in the upper-right corner and select “Profile”.
- Open the “2FA” tab and click “Enable”.
- The “Enable Two-Factor Authentication” dialog shows a QR code — leave it on the screen and add it to the extension as described below. If it will not scan, the dialog also shows a key.
- Enter the six-digit verification code from the extension and your Make password, then click “Enable”.
Add Make to Authenticator
- Install 2FA Authenticator from the Chrome Web Store and pin it to the toolbar, so its icon is one click away.
- Leave the Make page with the QR code open. Click the Authenticator icon, then “Add Account” → “QR Code” → “Scan QR from screen”.
- The account appears in the list with a six-digit code that changes every 30 seconds. Rename it if you like — the name is only for you.
- Go back to Make and type the current code into the confirmation field. If it is about to expire, wait for the next one.
- Make confirms that two-factor authentication is on. From now on it will ask for a code when you sign in — click the extension icon and copy it.
No QR code, or it will not scan? Look for the option to enter a key manually on Make’s setup screen, copy the key, and add it in the extension with “Add Account” → “Manual” → “Secret Key”.
Get 2FA Authenticator for Chrome — freeDownload your Make backup codes
Right after enabling, click “Download codes” to save a text file of one-time passwords. Each one signs you in instead of an app code — Make’s answer to a lost phone or a deleted app. Make says to keep the file away from the device with your authenticator, so do not leave it only on this computer.
The code is not accepted?
Most often the QR code changed: the website makes a new one each time its setup page is reloaded or opened again, so the account you added first no longer matches. Start the setup again, add the QR code that is on the screen now and type its code in straight away. Two entries for the same website? Use the newest. Other reasons: why codes are refused.
Typed the key in by hand? Paste it into the TOTP code generator and compare the code with the one in the extension. If they differ, the key was copied wrong — add the account again.
Questions
- Can I use Make 2FA without a phone?
- Yes. Make’s help describes an app on your phone, but all Make checks is the code, and any standard authenticator produces it. The Authenticator extension reads the QR code straight off the Make dialog and generates the codes in Chrome.
- How do I move Make 2FA to a new authenticator?
- Make has no “switch app” step. Open Profile → 2FA, click “Disable”, confirm with a code from the current authenticator — or a one-time password — and your Make password, then click “Enable” again and add the new QR code.
- What if I lose my authenticator?
- At sign-in, enter one of the one-time passwords from the file you downloaded instead of an app code, then set 2FA up again. Make’s help describes no other way back, so keep that file safe.
- Why does Make say my code is wrong?
- Usually the QR code changed: if the dialog was closed or opened again, Make made a new one, and the account you added first no longer matches. Add the QR code that is on the screen now and type its code in straight away. If you have two entries for Make, use the newest.
Your codes, one click from the login page
Authenticator keeps your 2FA codes in the browser, on your device only — free to use, open source, no account and no phone needed. Local backups and optional password protection come built in.
Get 2FA Authenticator for Chrome — free