Can I Manage n8n Cloud Project-Level Permissions via the REST API?

Based on the current public documentation, the officially documented REST API endpoints are those listed in the API reference. The guides on RBAC—including managing projects and roles—focus on the UI interactions, and there isn’t information confirming that there are additional, publicly supported API endpoints for managing project-level permissions in n8n Cloud.

This means that while the UI allows administrators and project admins to create projects, add/remove users, and move workflows between projects, any underlying APIs for those functions are not detailed in the public API reference. Consequently, if you’re considering a custom Terraform provider to manage project-level permissions via REST, there isn’t officially exposed support for that at this time.

In summary:

• All currently supported and documented endpoints are available in the public REST API reference.
• Project-level RBAC functions (like adding/removing users, managing roles) are intended to be managed via the UI.
• There are no officially supported additional endpoints for project-level permissions beyond what is in the published API documentation.

If you require such functionality, it may be worth following updates from n8n or inquiring through official channels to see if future releases or enterprise plans might expose these features via a public API.

Based on the official documentation, there isn’t any indication that n8n Cloud exposes additional or undocumented REST API endpoints for managing project-level permissions beyond what’s provided in the public API reference. Currently, project-related permissions (such as adding or removing users, assigning roles, or moving workflows/credentials between projects) are managed via the n8n UI. There is no reference or available documentation that these actions are exposed as separate REST endpoints.

If project-level permission management via API is a critical requirement for your Terraform provider approach, you might consider reaching out directly to n8n support or their community channels. They can confirm if there’s an internal API not yet documented or if there are plans to expose such endpoints in the future.

In summary, at this time, the documented public API is the authoritative source for what is available on n8n Cloud.