appreciate the instant answer <3 and the ETA
1 Like
Would it be possible to get notify when it goes live? Im very involved and i would love to beta test it and give feedback. i want it to succeed.
p.s i suggested a feature via the “submit a feature request” from the app. it would be awesome if frame ask me if i want to put a specific status to all assets i upload either from folder upload or asset upload
Thank you very much for the quick response. Will n8n also be supported, or can I implement this via an HTTP request node? I’m wondering whether this will still run through Adobe and whether I need an account for this. I’m on the Pro Plan and definitely need access to the API interface. I’d appreciate a notification here in the forum once it becomes available. @Alexhuet – feel free to connect as we’re facing the same challenge. Best regards, David
Experiencing a similar issue on our Pro account, there are no teams available and submitting the form fails with no error. Inspecting the request shows a 500 server error:
Is there an update on when the rework will be live?
Hi there,
I’m having a similar problem. Trying to create a webhook on the developer portal for a Make automation. But the “Team” dropdown has no options available I’m on a Team plan with a Content Admin team role.
Note that the account I’m referring to is not this account, it’s my client’s account who I’m doing this on behalf of.
Tried contacting support, but they tell me to come here.
I’m trying to set up an automation in Make that triggers when new comments are added in Frame. If the webhook isn’t working, I’m open to alternatives, but it has to trigger in Make
Please help!
@tylermyeo can you confirm whether or not your client is on a V3 (Legacy) or V4 account? Their account will indicate whether or not it is a Legacy account, such as my screenshots below:
Team is synomous with the Legacy version of Frame.io, whereas Workspace is the new term for V4 which replaces Team.
Webhooks are currently in the Alpha version of the API and are subject to change, so please issue caution when using them in a production environment (we do not recommend it until it has been moved to the Stable version).
If you wish to create your own V4 node with Make.com, you can do so by using the HTTP request node (@bell was successful in this and can provide more information if you ask nicely!). You will need to log into the Adobe Developer Console and create a project with OAuth Web App credentials which you can then enter into the HTTP request node.
@mattstone this looks like you are creating a Legacy webhook. Are you intending to use this with V4? If so, it will not work. Our webhooks for V4 are currently in an Alpha state and you are more than welcome to test and give us feedback, but please note they are subject to change while in Alpha so we do not recommend using them in a production environment at this time.
Thanks @CharlieAnderson, will test the alpha webhooks and report back.
@CharlieAnderson I’ve forked the Postman collection, setup and OAuth token using an Adobe account with the same email address as my Frame.io account, but all v4 requests are responding with:
{
"errors": [
{
"title": "Unauthorized",
"detail": "Invalid or missing authorization token"
}
]
}
The Authorization header with the token is definitely in the request. Can you please assist?
@mattstone you will get that error if you do not have a linked Frame & Adobe ID (having the same email address for both isn’t the same as linking them). There’s a process for doing this right now that’s only available by reaching out to our support team and asking them to link your Frame.io V4 account to your Adobe ID. If you run into issues when talking to support, please DM me.
Thanks @CharlieAnderson
I’m trying to use the help link in Frame.io to contact support, and seeing this error:
I’ve tried across multiple browsers and confirmed ad block is disabled for the site.
Thanks @CharlieAnderson
Frame support confirmed we’re on V4.
Here’s what I tried in Make:
Webhook node + HTTP request node (Make an OAuth 2.0 request)
Details I used for the HTTP request node:
- Client ID / Secret: from Adobe Developer Console
- Auth URL:
https://ims-na1.adobelogin.com/ims/authorize - Token URL:
https://ims-na1.adobelogin.com/ims/token - Added
https://www.make.com/oauth/cb/customto my redirect URIs in the Adobe console first
This gave me a timeout error when trying to create the connection in Make.
Then I tried opening Make in an incognito window in case my extensions were causing a problem, and I allowed third-party cookies for ims-na1.adobelogin.com. Same problem.
I’m not using any firewalls or VPNs.
Then I added the scopes from Adobe Developer Console to the Make HTTP module, and this time it showed the Adobe login screen for a second before throwing this error:
{
“message”: “The request failed due to failure of a previous request.”,
“code”: “SC424”,
“suberrors”: [
{
“message”: “Cannot find module ‘/data/integromat_local/imt_accounts/custom’\nRequire stack:\n- /data/integromat/imt-web-api/dist/lib/workers/connection_processor.js”,
“name”: “Error”
}
]
}
I’ve tried using a few different browsers (Arc / Safari / Chrome). Also checked the Make status page, and it said there were no problems.
I’m not sure what else to try.
@bell any tips on how you got it working would be hugely appreciated!
@tylermyeo I believe the Make.com redirect is https://www.integromat.com/oauth/cb/oauth2 when doing a HTTP request node. The https://www.make.com/oauth/cb/custom is for when you create a custom app IIRC.
Hey Tyler!
The full URLs for Adobe IMS are the following, just to cover all our bases:
https://ims-na1.adobelogin.com/ims/authorize/v2
https://ims-na1.adobelogin.com/ims/token/v3
2 Likes
Amazing! That let me create the connection in Make. Progress!
I’m unclear on what to enter into the rest of the HTTP module fields to get the webhook working with Frame comments:
I’m seeing some sources say the URL should be https://api.frame.io/v4/accounts/{ACCOUNT_ID}/workspaces/{WORKSPACE_ID}/webhooks
but it’s not clear how to get the account and workspace IDs (I don’t see them listed in the Frame account settings tab).
Until Make.com updates their Frame.io integration to support V4 in a dynamic way like you described, you will need to run a HTTP request node before the webhook one to get the account_id and then another one to get theworkspace_id of the account/workspace you wish to use a webhook for (note that all events are scoped to the Workspace provided during the creation of the webhook. This means events will be sent for actions taken in all projects in that Workspace, and not to a specific project at this time).
GET https://api.frame.io/v4/accounts
then refer to the id from that JSON payload, IE:
{
"data": [
{
"created_at": "2023-09-25T19:18:29.614189Z",
"display_name": "Integration Account",
"id": "17b990f7-bc43-4ed3-80fd-7e203089490b", # <---This here
"image": "https://picture.frame.io/image/convert/frameio-uploads-development/logo.png",
"roles": [
"admin"
],
"storage_limit": 300,
"storage_usage": 300,
"updated_at": "2024-02-07T16:44:41.986478Z",
"v4_migrated_at": "2025-02-02T16:44:41.986478Z"
}
],
"links": {
"next": "/v4/accounts/1234/workspaces/5678/projects?after=g3QAAAACZAACaWRtAAAAJGFiMmNiY2QzLWFkODQtNDQwMC05YTRkLWE1ZDRkMGE4ZTIxM2QABG5hbWVtAAAACVByb2plY3QgMg=="
},
"total_count": 10
}
then make a GET https://api.frame.io/v4/accounts/{account_id}/workspaces and is that id returned there
{
"data": [
{
"account_id": "8c4fa112-6185-4c69-b230-8cca2946f9c9", # <-- account_id is also here
"created_at": "2024-01-25T19:18:29.614189Z",
"creator": {
"active": true,
"avatar_url": "https://assets.frame.io/uploads/cd58cb8e-24b3-4448-8d0f-9532fcd04d11/original.png?response-content-disposition=attachment%3B+filename%3D%22foo.png&Expires=1729857600&Signature=L09h0pi82dCrMYjr9lMHBragByWYh1&Key-Pair-Id=KKI497NESTHMN",
"email": "user_email@example.com",
"id": "196C1A5666BF4EB00A49411B@176719f5667c82b4494214.e",
"name": "Jon Doe"
},
"id": "acf6feed-1696-485e-bd6a-70ac2911b4d6", # <--- this here
"name": "My Workspace",
"updated_at": "2024-02-07T16:44:41.986478Z"
}
],
"links": {
"next": "/v4/accounts/1234/workspaces/5678/projects?after=g3QAAAACZAACaWRtAAAAJGFiMmNiY2QzLWFkODQtNDQwMC05YTRkLWE1ZDRkMGE4ZTIxM2QABG5hbWVtAAAACVByb2plY3QgMg=="
},
"total_count": 10
}
From there you can use those to populate the account_id and workspace_id you want to use to create the webhook with the payload events you want to listen for:
POST https://api.frame.io/v4/accounts/{account_id}/workspaces/{workspace_id}/webhooks
{
"data": {
"events": [
"file.created",
"file.deleted",
"file.ready",
"file.updated",
"file.upload.completed",
"file.versioned",
"folder.created",
"folder.deleted",
"folder.updated",
"comment.completed",
"comment.created",
"comment.deleted",
"comment.uncompleted",
"comment.updated",
"metadata.value.updated",
"project.created",
"project.deleted",
"project.updated"
],
"name": "New Webhook",
"url": "https://url.example.com"
}
}
Since the account_id is returned in the workspace GET, you could just use that id in the response to provide the data needed (they are different in the two response exmaples I listed due to how our documentation generates the data but will be correct in use)
We just published a Webhook Guide on our docs, so please let me know if you have any feedback about it!
Thanks Charlie,
I assume I’m missing something obvious, but I created the HTTP (Make a request) node in Make, and used GET https://api.frame.io/v4/accounts…
…but I get an error: {"errors":[{"title":"Unauthorized","detail":"Invalid or missing authorization token"}]}
It’s the same result when I try the HTTP (Make an OAuth 2.0 request) node.
What am I doing wrong?
Hi @tylermyeo if you are getting a 401/unauthorized error then that most likely means you do not have your Frame.io account linked to an Adobe ID. Currently this is only available by reaching out to our support team to get this resolved. So please do and let me know if you have any questions!
Hi,
we can also not create a webhook. In the settings it shows one workspace but cannot find the name, if I open up the owner account settings it says no workspace. we don’t have a workspace in the dropdown menu, it does not show any options. Due to that we are unable to create one but also receive no error messages.
what do we need to change to be able to create webhooks?
@KoiMedia can you explain a bit more about how you are trying to create a webhook which requires a dropdown menu? Screenshots would be helpful to help troubleshoot. Thanks!