Unable to establish OAuth 2.0 connection to Frame.io V4 API in Make.com or n8n - Need help with automation integration

[Roevmos]

Problem Summary

I’m trying to create automated workflows to create projects and folders in Frame.io V4 using Make.com and n8n, but I cannot establish a working OAuth 2.0 connection despite following the documentation and trying multiple configurations.

My Setup

• Frame.io Version: V4 (next.frame.io domain)
• Goal: Create projects and folders via API calls
• Platforms Tested: Both Make.com and n8n
• Adobe Developer Console: Properly configured with Frame.io API integration

Adobe Developer Console Configuration

Project Setup:

• Created project in Adobe Developer Console
• Added Frame.io API to the project
• Configured OAuth Web App credential

Client Details:

• Client ID: 300697ad33c542b896f22c8b03f6fb41
• Client Secret: Available
• Scopes: additional_info.roles, offline_access, profile, openid

Redirect URIs Tested:

• Make.com: https://www.make.com/oauth/cb/app
• n8n: https://oauth.n8n.cloud/oauth2/callback
• Redirect URI Patterns: Properly escaped with \\.

OAuth Endpoints Attempted

Initial Configuration (Failed)

• Authorize URI: https://ims-na1.adobelogin.com/ims/authorize/v1
• Token URI: https://ims-na1.adobelogin.com/ims/token/v1
• Error: Bad Request

Updated Configuration (Failed)

• Authorize URI: https://ims-na1.adobelogin.com/ims/authorize/v2
• Token URI: https://ims-na1.adobelogin.com/ims/token/v3
• Error: Resource not found

Current Configuration (Partial Success)

• Authorize URI: https://ims-na1.adobelogin.com/ims/authorize/v2
• Token URI: https://ims-na1.adobelogin.com/ims/token/v3
• Flow Type: Authorization Code
• Scopes: additional_info.roles, offline_access, profile, openid

Error Details

Make.com Errors

1. Initial: Bad Request when trying different authorize URIs
2. Current: After clicking authorize, I successfully reach Adobe’s login page and can authenticate, but then get redirected back to:

json

{
  "message": "The request failed due to failure of a previous request.",
  "code": "SC424",
  "suberrors": [
    {
      "message": "Cannot read properties of null (reading 'authorize')",
      "name": "TypeError"
    }
  ]
}

n8n Errors

• Error: “Resource not found” when attempting OAuth authorization
• Same endpoints and configuration as Make.com

Attempts Made

1. Scope Variations Tested:

• frameio_api (caused bad request - discovered this isn’t a valid Adobe IMS scope)
• openid,AdobeID
• creative_sdk
• Current: additional_info.roles,offline_access,profile,openid

2. Flow Types Tested:

• Authorization Code
• Implicit Grant (also failed)

3. Different URI Versions:

• /v1 endpoints
• /v2 and /v3 endpoints

Current Status

• Adobe login page appears correctly
• User authentication completes successfully
• Redirect back to automation platform fails
• Error suggests OAuth response parsing issue

Questions

1. Are there specific OAuth endpoints that work reliably with Frame.io V4 API for automation platforms?
2. Is there additional configuration needed in Adobe Developer Console for Make.com/n8n integration?
3. Are there known compatibility issues between Adobe IMS OAuth and these automation platforms?
4. Is there a timeline for when Frame.io V4 API will have stable support in automation tools?

Additional Context

I’ve found references that suggest Frame.io V4 API may not be fully mature for automation workflows yet, and some sources recommend staying on Frame.io V3 for API integrations. However, I’m already on V4 and would prefer to make this work rather than downgrade if possible.

Any guidance would be greatly appreciated! This is blocking several critical automation workflows for our team.

[CharlieAnderson]

hi @Roevmos

the call back for make.com is https://www.integromat.com/oauth/cb/oauth2. If you would like to have make.com have a more native solution, please reach out to their support and make the request.

For n8n (we exploring a community node for V4, stay tuned) you will need to have a webhook server set up on your local machine via a self-signed SSL certificate. I was able to do this myself via ngrok and updating your redirect_uri in the developer console to match what your local redirect is.

The IMS endpoints of

• Authorize URI: https://ims-na1.adobelogin.com/ims/authorize/v2
• Token URI: https://ims-na1.adobelogin.com/ims/token/v3

are correct.

[Roevmos]

Hey Charlie,

Thanks for your quick response.

I’m not a developer from origin, i’m trying to use claude / chatgpt to get my api’s setup in Make / N8N but i’m failing to authorize this OAuth2.0 through both tools.

Do you have any suggestion for me to get my setup finished for my client. I just want to create folders / projects automatically from my crm/system. Is switching back to v3 optional as these node’s are setup in make.com for example.

Thanks

[CharlieAnderson]

Because Adobe IMS requires https for authentication, if you are using n8n locally, you will need to use a self signed certificate to catch the redirect uri when authenticating.

For Make.com I just tested this myself and was able to authenticate successfully. You will want to choose the HTTP node with “Make and OAuth 2.0 request” and fill in your client secret and client id from the developer console with the appropriate scopes as outlined in the project details.

Then you can make your requests, as outlined in the API references:

which should give you a 200 successful response.

once you get here you can start to chain the responses together. I recommend you check out the postman collection to get started with API calls if you are running into issues.

If you are using claude you might be able to ask it to spit out some JSON based on the API references, but FYI the V4 docs are not optimized for LLMs at this time so you will have to make sure things are set up correctly and functional.

[Roevmos]

Hey @CharlieAnderson

I followed all your steps and did exactly what you did, I got one step further and I was able to ‘verify’ my connection via the oauth2.0 - however when I want to use it I get the error:
{"errors":[{"title":"Unauthorized","detail":"Invalid or missing authorization token"}]}

I feel there’s something wrong when i’m doing the verification because once I want to verify my connection it opens up adobe, but directly forward me somewhere and then closes the page. Which then ‘establish’ the connection. But i’m not able to use is.

By any chance, are you able to jump on a 5 min call so I can show you? I can also provide a loom/tella video if you want.

Let me know, I just don’t understand what’s happening. I tried this in both Chrome and Arc but both the same issue

[CharlieAnderson]

Hi @Roevmos the unauthorized comes from you not having an Adobe ID linked to your Frame.io account, like many of the other issues folks have had here. You can reach out to our support team to ask them to help you with this.