Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The N8N connector uses the following default correlation and object configurations.
Default Correlation Configuration
Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.
You can customize the correlation configuration. Refer to Assigning Source Accounts to Identities for more information.
When you first create the N8N source, the default correlation mapping is:
| Account Attribute | Operation | Identity Attribute |
|---|---|---|
| Equals | Work Email (email) |
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account Attributes
The N8N connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| id | N8N user ID. |
| The user's login email address. | |
| firstName | The user's first name. |
| lastName | The user's last name. |
| displayName | Connector-derived display name (firstName + lastName, falls back to email). |
| isPending | true when the user has been invited but has not accepted the invitation. |
| globalRole | Instance-level role entitlement: global:owner, global:admin, or global:member. |
| projects | IDs of team projects this user belongs to (personal projects excluded). Managed entitlement. |
| createdAt | Account creation timestamp (ISO-8601). |
| updatedAt | Account last-updated timestamp (ISO-8601). |
Default Entitlement Attributes
Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.
Caution
Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.
Default Group Attributes
The N8N connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.
N8N team projects are aggregated as group entitlements.
| Attribute Name | Description |
|---|---|
| id | N8N project ID (native identity). |
| name | Project display name. |
| type | Project type: personal or team. |
| description | Optional project description. |
| creatorId | User ID of the project creator. |
| createdAt | Project creation timestamp (ISO-8601). |
| updatedAt | Project last-updated timestamp (ISO-8601). |
| members | Email addresses of project members. |
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.