How to Configure Okta SAML SSO for Make.com

This guide explains how to connect Okta SAML single sign-on (SSO) with make.com so your users can access the platform securely using their corporate Okta accounts.

Prerequisites for Okta SAML and Make.com

Before you start, confirm that you have the right access and information to integrate Okta with make.com.

• An Okta administrator account with permissions to create and configure applications.
• An organization or team account in make.com with admin access to security or SSO settings.
• A supported browser to open both Okta and make.com configuration pages.

If you need advanced SSO strategy or consulting, you can also review external implementation resources such as Consultevo.

Create a New Okta SAML Application for Make.com

First, you will create a new SAML integration in Okta that will represent make.com.

Step 1: Add an Okta SAML app for Make.com

1. Sign in to your Okta admin console.
2. Go to Applications > Applications.
3. Click Create App Integration.
4. Select SAML 2.0 as the sign-in method.
5. Click Next to open the configuration wizard.

Okta now provides a blank SAML configuration that you will tailor for make.com.

Step 2: Name the Okta SAML app for Make.com

1. In the General Settings screen, enter an application name such as Make.com SAML.
2. (Optional) Upload a logo if you want the app to be easily recognizable for your users in Okta.
3. Click Next to continue to the SAML settings.

Configure SAML Settings for Make.com

In this section you will enter the SAML configuration that links Okta with make.com.

Step 3: Enter the basic SAML settings for Make.com

In the SAML Settings page:

1. Locate the Single sign on URL field and enter the Assertion Consumer Service (ACS) URL provided by make.com in its SSO configuration area.
2. In the Audience URI (SP Entity ID) field, paste the Entity ID supplied by make.com.
3. Ensure the Name ID format matches the value expected by make.com (typically EmailAddress or a similar standard identifier).
4. Select the Application username format that corresponds to the user field make.com uses, usually the email address.

The ACS URL and Entity ID must match exactly the values displayed in your make.com SSO configuration interface.

Step 4: Configure attribute statements for Make.com

Attribute statements ensure make.com receives the correct user data from Okta. Common attributes are:

• email – mapped to user.email.
• firstName – mapped to user.firstName.
• lastName – mapped to user.lastName.

To configure attributes:

1. In the Attribute Statements section, click Add for each attribute you need.
2. Enter the attribute Name exactly as required by make.com.
3. Select the Value from the Okta user profile drop-down menu, such as user.email.
4. Repeat for all attributes that make.com expects.
5. Click Next when finished.

Finish and Assign the Okta App for Make.com

Step 5: Review and save the SAML configuration

Okta now shows a summary of your SAML settings for make.com.

1. Review all fields for accuracy, including URLs, entity ID, Name ID format, and attribute statements.
2. Select how you plan to use this integration, usually I’m an Okta customer adding an internal app.
3. Click Finish to create the application.

Step 6: Assign users or groups to the Make.com app

Next, you must grant access to the new Okta application so users can sign in to make.com.

1. Open the application you just created in Okta.
2. Go to the Assignments tab.
3. Click Assign and choose Assign to People or Assign to Groups.
4. Select the users or groups who should have SSO access to make.com.
5. Click Done to save your assignments.

Connect Okta SAML Metadata to Make.com

Now you will copy SAML metadata from Okta and paste it into the SSO configuration area of make.com.

Step 7: Download or copy Okta SAML details

1. In the Okta app, open the Sign On tab.
2. Find the SAML 2.0 section.
3. Click View Setup Instructions or the equivalent link to open the SAML instructions page.
4. Locate the following items:
   • Identity Provider Single Sign-On URL
   • Identity Provider Issuer (Entity ID)
   • X.509 Certificate
5. Either download the certificate or copy it in the format requested by make.com.

Step 8: Add Okta SAML data into Make.com

In a separate browser tab, open your organization or team settings in make.com.

1. Go to the SSO or security section dedicated to SAML configuration.
2. Paste the Identity Provider Single Sign-On URL from Okta into the matching field in make.com.
3. Paste the Identity Provider Issuer or Entity ID value into the appropriate field.
4. Upload or paste the X.509 Certificate exactly as exported from Okta.
5. Verify that all fields required by make.com are completed.
6. Save or update your SSO configuration.

Test Okta SAML Login to Make.com

After saving your configuration on both sides, you should confirm that users can sign in to make.com through Okta.

Step 9: Perform a basic SSO test

1. Log out of make.com, or open a private/incognito browser window.
2. Navigate to the SSO login URL or organization login page for make.com.
3. Choose the option to sign in with Okta SAML.
4. Use a test account that has been assigned to the Okta application.
5. Verify that you are redirected to Okta, successfully authenticated, and then returned to make.com.

If the login succeeds and you reach your dashboard, the Okta SAML integration for make.com is functioning as expected.

Step 10: Troubleshoot common SAML issues

If authentication fails, review these common issues:

• Mismatched URLs – Confirm that the ACS URL and Entity ID in Okta exactly match the values in make.com.
• Certificate problems – Ensure you copied the full X.509 certificate, including header and footer lines.
• Incorrect Name ID format – Verify that the Name ID format in Okta is accepted by make.com and that it matches the user identifier.
• Missing attributes – Check that mandatory attributes configured in make.com are actually sent from Okta.
• User not assigned – Make sure the test user is assigned to the Okta application and is allowed to sign in.

For detailed, product-specific screenshots and up-to-date values such as exact URLs and attribute names, always refer to the official documentation at the Okta SAML help page for Make.com.

Maintain and Monitor Okta SAML for Make.com

Once your integration is working, keep it secure and reliable over time.

• Monitor sign-in logs in both Okta and make.com to detect unusual access patterns.
• Rotate the X.509 certificate according to your organization’s security policy and update it in make.com when changed.
• Regularly review user and group assignments in Okta to ensure only authorized users can reach make.com.
• Update SAML attributes if your identity model or user profile fields change.

By following these steps, you can keep the Okta SAML connection for make.com stable, secure, and aligned with your organization’s access policies.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help