# SailPoint N8N SaaS Connector Documentation > N8N SaaS Connector Documentation # Documentation # Connecting SailPoint and N8N SaaS To connect SailPoint with N8N Cloud, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Select **Create Manual Work Items** to allow the connector to create manual work items for certain operations. You can also enable this option so the source supports additional source management features such as creating accounts and access profile management. > **Important** > > Once you enable this feature, you cannot disable it. For more information on manual work items in SailPoint, refer to [Work Items](). For more information on SailPoint features, refer to [SailPoint Identity Services](). 7. Select **Save**. ## Connection Settings The following values are required for SailPoint to connect to your N8N instance. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. Enter the HTTPS **Base URL** of your N8N instance - for example `https://your-instance-name.app.N8N.cloud`. Use the URL your administrators publish for API access; do not append `/api/v1` paths. 3. Enter the API key from [Prerequisites](). Paste the full key string; it is stored as a secret in SailPoint. 4. Select **Save**. ## Aggregation Settings > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Select **Aggregation Settings** from the menu. 2. In **Connection Timeout (Minutes)**, enter the number of minutes SailPoint waits for a response before timing out. 3. In **Page Size**, enter the number of records to fetch in one request. The minimum value is 1 and the maximum value is 250. By default, the page size is 100. 4. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Dataset Management Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history. > [!NOTE] > > Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric]() for more information. For more information, refer to [Managing Datasets and Resources]() for datasets, resources, owner correlation, and aggregation. ## Datasets A *dataset* is a named group of one or more related resources that the source aggregates together. When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources. > [!NOTE] > > Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them. ### Dataset Aggregation Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](). ## Resources A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model. In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation. For more information, refer to [Managing Resources](). ### Owner Correlation Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](). ## Supported Datasets Go to **Dataset Management \> Datasets** on your N8N SaaS source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation. > [!NOTE] > > Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](). The connector aggregates automation and AI topology in the Workflow Graph dataset and stored integration credentials in the Credentials dataset. Both datasets use a default aggregation schedule of daily at 02:00 UTC (`0 2 * * *`). During workflow-graph aggregation, the connector scans all workflows once (`GET /api/v1/workflows`, paginated), derives agent, tool, and MCP resources from workflow node graphs, and then scans credentials separately (`GET /api/v1/credentials`, paginated). | Dataset name | Associated resources | Dataset ID | | --- | --- | --- | | Workflow Graph | Workflow, Agent, Tool, MCP Client, MCP Server | `N8N:workflow-graph` | | Credentials | Credential | `N8N:credentials` | ### Workflow Graph The Workflow Graph dataset aggregates automation and AI topology from the workflows API. The connector emits at least one Workflow resource row for every workflow and emits additional resource rows for workflows that contain AI or MCP nodes. ### Credentials The Credentials dataset aggregates all stored credentials from the credentials API independently of workflow scans. The connector includes orphaned and globally shared credentials. The N8N API never returns secret credential values. ## Supported Resources A resource represents an object type that the connector collects from N8N, such as workflows, AI agents, tools, MCP endpoints, or stored credentials. Each resource defines the attributes the connector collects for that object type and how SailPoint displays each object. For more information, refer to [Managing Resources](). > [!NOTE] > > When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources. | Resource name | Resource type | Resource ID | | --- | --- | --- | | Workflow | Application | `N8N:workflow` | | Agent | Agent | `N8N:agent` | | Tool | Capability | `N8N:tool` | | MCP Client | Capability | `N8N:mcp-client` | | MCP Server | Application | `N8N:mcp-server` | | Credential | Credential | `N8N:credential` | ## Workflow Attributes The following table lists schema attributes for the Workflow resource (`N8N:workflow`). | Property | Value | | --- | --- | | Name | Workflow | | Type | `std:application` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | N8N workflow ID (stable native identity). | | `name` | string | Yes | Workflow display name. | | `description` | string | No | Connector-generated description for this workflow. | | `active` | boolean | No | Indicates whether the workflow is active (enabled) in N8N. | | `workflowType` | string | No | The connector derives this classification: `APPLICATION`, `AGENT`, `MCP_SERVER`, or `AGENT_MCP_SERVER`. | | `nodeCount` | integer | No | Total number of nodes in the workflow. | | `projectId` | string | No | N8N project ID this workflow belongs to (when returned by API). | | `projectName` | string | No | N8N project display name (when returned by API). | | `tags` | string list | No | Workflow tag names (when returned by API). | | `createdAt` | string | No | Workflow creation timestamp (ISO-8601 UTC). | | `updatedAt` | string | No | Workflow last-updated timestamp (ISO-8601 UTC). | | `spStatus` | string | No | The connector sets this normalized lifecycle status from the `active` attribute: `Active` when `active` is `true`, `Inactive` when `false`. | | `spDescription` | string | No | Source-system description copied from the workflow description field for governance display. | ## Agent Attributes The following table lists schema attributes for the Agent resource (`N8N:agent`). | Property | Value | | --- | --- | | Name | Agent | | Type | `std:agent` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | Stable native identity: `{workflowId}:{nodeId}` for both root agents and sub-agents. | | `name` | string | Yes | Agent node canvas display label. | | `description` | string | No | Connector-generated description for this agent. | | `spBusinessApplication` | string | No | SailPoint business application identifier. Always `N8N` for N8N AI agents. | | `agentKind` | string | Yes | `AGENT` for root workflow-level AI agents; `SUB_AGENT` for inline sub-agent nodes that connect as tools to a parent agent. | | `active` | boolean | No | Indicates whether the parent workflow is active (enabled) in N8N. | | `agentNodeType` | string | No | N8N node type of the primary agent node (e.g. `@N8N/N8N-nodes-langchain.agent`). | | `agentNodeName` | string | No | Canvas display label of the primary agent node within the workflow. | | `languageModel` | string | No | The language model provider that the agent uses (for example, `openai`, `anthropic`, or `google`). | | `toolCount` | integer | No | Number of tool sub-nodes wired to this agent via the `ai_tool` channel (root agents only). | | `mcpClientCount` | integer | No | Number of MCP Client Tool sub-nodes wired to this agent (root agents only). | | `nodeId` | string | No | N8N node UUID within the workflow JSON (sub-agents; absent for root agents). | | `workflowId` | string | No | Workflow ID containing this sub-agent (sub-agents only). | | `workflowName` | string | No | Workflow display name (sub-agents only). | | `parentAgentNodeId` | string | No | Node UUID of the parent agent this sub-agent is wired to (sub-agents only). | | `parentAgentNodeName` | string | No | Canvas label of the parent agent node (sub-agents only). | | `projectId` | string | No | N8N project ID (when returned by API). | | `projectName` | string | No | N8N project display name (when returned by API). | | `tags` | string list | No | Workflow tag names (when returned by API). | | `createdAt` | string | No | Workflow creation timestamp (ISO-8601 UTC). | | `updatedAt` | string | No | Workflow last-updated timestamp (ISO-8601 UTC). | | `spStatus` | string | No | The connector sets this normalized lifecycle status from the parent workflow `active` flag: `Active` or `Inactive`. | | `spDescription` | string | No | For sub-agents: `toolDescription` parameter. For root agents: workflow description field. | ## Tool Attributes The following table lists schema attributes for the Tool resource (`N8N:tool`). | Property | Value | | --- | --- | | Name | Tool | | Type | `std:capability` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | Stable native identity: `{workflowId}:{nodeId}`. | | `name` | string | Yes | Tool node canvas display label. | | `description` | string | No | Connector-generated description including tool type. | | `spType` | string | Yes | Capability type. Always `TOOL` for N8N tool sub-nodes. | | `toolNodeType` | string | No | Full N8N node type string (e.g. `@N8N/N8N-nodes-langchain.toolHttpRequest`). | | `nodeId` | string | No | N8N node UUID within the workflow JSON. | | `workflowId` | string | No | Workflow ID containing this tool node. | | `workflowName` | string | No | Workflow display name. | | `parentAgentNodeId` | string | No | Node UUID of the AI agent this tool is wired to. | | `parentAgentNodeName` | string | No | Canvas label of the parent AI agent node. | | `credentialIds` | string list | No | N8N credential IDs referenced in this tool node's parameters (when available). | | `spStatus` | string | No | The connector sets this normalized lifecycle status from the parent workflow: `Active` or `Inactive`. | | `spDescription` | string | No | Tool description from the node's `toolDescription` or `description` parameter. | ## MCP Client Attributes The following table lists schema attributes for the MCP Client resource (`N8N:mcp-client`). | Property | Value | | --- | --- | | Name | MCP Client | | Type | `std:capability` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | Stable native identity: `{workflowId}:{nodeId}`. | | `name` | string | Yes | MCP Client Tool node canvas display label. | | `description` | string | No | Connector-generated description including server URL. | | `spType` | string | Yes | Capability type. Always `MCP_CLIENT` for N8N MCP Client Tool nodes. | | `serverUrl` | string | No | SSE endpoint URL for the remote MCP server that this client connects to. | | `authMethod` | string | No | Authentication method: `bearer`, `header`, `multipleHeaders`, `oauth2`, or `none`. | | `toolsFilter` | string | No | Defines which tools from the server the agent can use: `ALL`, `SELECTED`, or `ALL_EXCEPT`. | | `nodeId` | string | No | N8N node UUID within the workflow JSON. | | `workflowId` | string | No | Workflow ID containing this MCP client node. | | `workflowName` | string | No | Workflow display name. | | `parentAgentNodeId` | string | No | Node UUID of the AI agent this MCP client is wired to. | | `parentAgentNodeName` | string | No | Canvas label of the parent AI agent node. | | `spStatus` | string | No | The connector sets this normalized lifecycle status from the parent workflow: `Active` or `Inactive`. | ## MCP Server Attributes The following table lists schema attributes for the MCP Server resource (`N8N:mcp-server`). | Property | Value | | --- | --- | | Name | MCP Server | | Type | `std:application` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | N8N workflow ID (same as the corresponding Workflow resource when the workflow exposes an MCP Server Trigger). | | `name` | string | Yes | Workflow display name. | | `description` | string | No | Connector-generated description for this MCP server workflow. | | `active` | boolean | No | Indicates whether the workflow is active and the production MCP URL is live. | | `authMethod` | string | No | Authentication method required for MCP clients: `bearer`, `header`, or `none`. | | `exposedToolCount` | integer | No | Number of tool nodes exposed by this MCP server workflow. | | `exposedToolNames` | string list | No | Canvas names of tool nodes attached to the MCP Server Trigger. | | `projectId` | string | No | N8N project ID (when returned by API). | | `projectName` | string | No | N8N project display name (when returned by API). | | `createdAt` | string | No | Workflow creation timestamp (ISO-8601 UTC). | | `updatedAt` | string | No | Workflow last-updated timestamp (ISO-8601 UTC). | | `spStatus` | string | No | The connector sets this normalized lifecycle status from the workflow `active` flag: `Active` or `Inactive`. | ## Credential Attributes The following table lists schema attributes for the Credential resource (`N8N:credential`). | Property | Value | | --- | --- | | Name | Credential | | Type | `std:credential` | | Identity attribute | `identity` | | Display attribute | `name` | ### Attributes | Attribute | Type | Required | Description | | --- | --- | --- | --- | | `identity` | string | Yes | N8N credential ID (stable native identity). | | `name` | string | Yes | Credential display name. | | `description` | string | No | Connector-generated description including credential type. | | `credentialType` | string | Yes | N8N credential type string (e.g. `slackApi`, `googleSheetsOAuth2Api`, `httpHeaderAuth`). | | `isGlobal` | boolean | No | Indicates whether the credential is shared globally across the N8N instance. | | `isManaged` | boolean | No | Indicates whether an external process manages the credential (for example, through environment variables). | | `createdAt` | string | No | Credential creation timestamp (ISO-8601 UTC). | | `updatedAt` | string | No | Credential last-updated timestamp (ISO-8601 UTC). | | `spStatus` | string | No | The connector does not populate this attribute because the N8N credentials API does not include an active flag. | # Integrating SailPoint with N8N SaaS This guide describes the requirements and configuration steps to connect SailPoint to N8N Cloud (or another N8N deployment that exposes the standard N8N REST API). The connector uses the N8N REST API to run test connection, aggregate N8N platform users as accounts, and aggregate N8N team projects as group entitlements for user governance. The connector also uses Dataset 2.0 to aggregate workflows, agents, tools, MCP clients, MCP servers, and stored credentials as machine identities. The N8N API does not return secret credential values. The connector aggregates credential metadata only. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features | Feature | Description | | --- | --- | | Test connection | Validates reachability of the N8N API and the configured API key using a lightweight workflows request. | | Account aggregation | Aggregates N8N platform users (`GET /api/v1/users`). | | Entitlement aggregation | Aggregates N8N team projects as group entitlements (`GET /api/v1/projects`). Personal projects are excluded from account membership. | | Dataset aggregation | Aggregates machine identities using Dataset 2.0: dataset `N8N:workflow-graph` (workflows, agents, tools, MCP clients, MCP servers) and dataset `N8N:credentials` (stored integration credentials). | | Activate and Deactivate N8N Agents | Activates and deactivates N8N agents. | ### Non-Human Identity Discovery - Aggregate N8N workflows, agents, tools, MCP clients, and MCP servers - Aggregate N8N stored integration credentials Refer to Dataset Management for more information. Refer to [Discovering Potential Non-Human Accounts]() for more information. ## Supported Versions The connector supports the following N8N versions: - N8N Cloud, version 2.17.6 > [!NOTE] > > Verify compatibility with your tenant. Newer minor releases might work if the REST API remains compatible. ## Prerequisites - [N8N API key](<#creating-an-api-key>). SailPoint sends the key in the X-N8N-API-KEY header. ### Creating an API Key SailPoint authenticates to N8N using an **API key** sent as the `X-N8N-API-KEY` header. 1. Sign in to **N8N**. 2. Go to **Settings** \> **N8N API**. 3. Select **Create an API key**. 4. Choose a **Label** and set an **Expiration** time for the key. 5. (Optional) If your organization uses an enterprise plan that scopes API keys, include read scopes required for workflows, credentials, users, and projects - for example `workflow:read`, `workflow:list`, and credential read access as defined by your N8N deployment. 6. Copy the API key and store it securely. You will paste it into the SailPoint source as **API Key**. Grant the key only the permissions your organization requires for discovery and governance. Secret credential values are never returned by the N8N API; the connector aggregates credential metadata only. For UI-specific steps and screenshots, refer to [N8N API authentication documentation]() or your internal runbooks. # 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](<#default-account-schema>) must be defined as strings if not specified. The N8N SaaS 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 SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | email | 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 SaaS 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. | | email | 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 SaaS connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. N8N SaaS 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. | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings]().