Microsoft Lists

Microsoft Lists is a Microsoft 365 app for tracking information and organizing work using structured lists. This connector accesses Microsoft Lists through the Microsoft Graph API, letting you read and write lists, list items, columns, and content types in your SharePoint sites.

Power end-to-end data operations for your Microsoft Lists API with Nexla. Our bi-directional Microsoft Lists connector is purpose-built for Microsoft Lists, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Microsoft Lists or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Microsoft Lists workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Microsoft Lists connector authenticates against the Microsoft Graph API using OAuth2 with a delegated (3-legged) authorization code flow through Microsoft Entra ID (formerly Azure AD). Before creating a credential in Nexla, register an application in your Microsoft Entra tenant and collect the client ID, client secret, and tenant-specific authorization and token URLs.

To register an application and obtain credentials, follow these steps:

1. Sign in to the Microsoft Entra admin center or the Azure Portal with an account that has permission to register applications.

2. Navigate to Microsoft Entra ID > App registrations, then click New registration.

3. Enter a name for the application (e.g., "Nexla Integration"). Under Supported account types, choose the option that matches your organization's needs, and add a Redirect URI of type Web pointing to the Nexla OAuth callback URL. Click Register.

4. On the application's Overview page, copy the Application (client) ID and the Directory (tenant) ID. The tenant ID is used to build your authorization and token URLs.

5. Go to Certificates & secrets > Client secrets, click New client secret, provide a description and expiry, and click Add. Copy the secret Value immediately, as it is shown only once.

6. Go to API permissions > Add a permission > Microsoft Graph > Delegated permissions, then add the permissions your integration needs, such as Sites.Read.All for read access or Sites.ReadWrite.All for read and write access to lists and list items. If your tenant requires it, click Grant admin consent.

7. Construct your tenant-specific endpoint URLs using the Directory (tenant) ID from step 4:

   • Authorization URL: https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/authorize
   • Token URL: https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token

The Microsoft Graph API base URL is https://graph.microsoft.com. For detailed information about app registration, delegated permissions, and the authorization code flow, see the Microsoft Graph authentication documentation and the Microsoft Lists (list resource) API reference.

Authenticate

Credentials required

OAuth2 3-legged flow for delegated user access to Microsoft Lists via Azure AD. Requires tenant registration and user consent.

Field	Required	Secret	Description
Client ID	Yes	Yes	A unique public identifier assigned to your application for OAuth2 authentication
Client Secret	Yes	Yes	A private key used to authenticate your application when requesting tokens
Authorization URL	Yes	No	The URL endpoint where users authenticate and authorize access (e.g. https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize)
Client ID Parameter	Yes	No	A unique public identifier assigned to your application (same value as Client ID)
Access Scope	No	No	A space-separated list of permissions your application requests
Token URL	Yes	No	The URL endpoint where authorization codes are exchanged for access tokens (e.g. https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token)
Client Secret Token Parameter	No	Yes	A private key used to authenticate your application when requesting tokens
Base URL	Yes	No	The base URL for the Microsoft Lists (Microsoft Graph) API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Client ID and Client Secret from your Microsoft Entra app registration, along with the tenant-specific Authorization URL and Token URL you constructed in Prerequisites. Set the Base URL to https://graph.microsoft.com, and optionally provide an Access Scope (a space-separated list of Microsoft Graph permissions).

4. Complete the OAuth2 authorization prompt when redirected to Microsoft to grant Nexla delegated access to your Microsoft Lists data.

   If your client secret is compromised, revoke it in the Microsoft Entra admin center under your app registration's Certificates & secrets and generate a new one. Client secrets have an expiry date, so rotate them before they lapse to avoid interrupted access.

   For detailed information about authentication and available endpoints, see the Microsoft Graph authentication documentation and the Microsoft Lists API reference.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Microsoft Lists connector tile, then select the credential that will be used to connect to Microsoft Lists, and click Next; or, create a new Microsoft Lists credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Microsoft Lists endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List all lists in a site

Retrieves all lists available in a SharePoint site.

Use this endpoint to discover the lists in a site before configuring downstream flows against specific lists. For detailed information, see the Microsoft Graph list resource documentation.

[Rest API] List content types in a list

Retrieves all content types associated with a specific list.

For detailed information about content types, see the Microsoft Graph contentType documentation.

[Rest API] Get a single list item

Retrieves a specific item from a list by its ID.

For detailed information about list items, see the Microsoft Graph listItem documentation.

[Rest API] Get search suggestions

Returns a list of search query suggestions based on a partial search query string.

[Rest API] List all SharePoint sites

List all SharePoint sites accessible to the authenticated user — enables site discovery.

Use this endpoint to enumerate the sites available to your credential and obtain the site IDs needed by other endpoints. For detailed information, see the Microsoft Graph site documentation.

[Rest API] Retrieve all items in a list

Retrieve the full collection of items in a list — the primary read path for any Lists integration.

This is the primary read endpoint for ingesting list data. For detailed information about list items and expanding column values, see the Microsoft Graph listItem documentation.

[Rest API] Get site metadata

Retrieve metadata for a specific SharePoint site.

[Rest API] Get list metadata

Retrieve metadata for a single SharePoint list by ID.

[Rest API] Get list column definitions

Retrieve the column definitions (schema) for a list.

For detailed information about column definitions, see the Microsoft Graph columnDefinition documentation.

[Rest API] Get a single column definition

Get a single column definition by ID.

[Rest API] Get a single content type

Get a single content type by ID.

[Rest API] List all versions of a list item

List all versions of a list item.

For detailed information about item versioning, see the Microsoft Graph listItemVersion documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Microsoft Lists data sources can also be manually configured to ingest data from any valid Microsoft Graph API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Microsoft Lists data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Microsoft Lists destination, and select the Send to Destination option from the menu. Select the Microsoft Lists connector from the list of available destination connectors, then select the credential that will be used to connect to Microsoft Lists, and click Next; or, create a new Microsoft Lists credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Microsoft Lists endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create a new list item

Create a new list item — the primary write operation for Microsoft Lists.

Each record from your Nexset is sent as a request to create a new item, with field values mapped into the list's columns. For detailed information about the request body, see the Microsoft Graph create listItem documentation.

[Rest API] Create a new list

Create a new SharePoint list within a site.

For detailed information about creating lists and defining their columns, see the Microsoft Graph create list documentation.

[Rest API] Update a list item

Update column values on an existing list item.

For detailed information about updating item field values, see the Microsoft Graph update listItem documentation.

[Rest API] Delete a list item

Delete a list item from a Microsoft Lists list.

[Rest API] Create a new column

Create a new column definition on a list.

For detailed information about column definitions, see the Microsoft Graph create columnDefinition documentation.

[Rest API] Update list metadata

Update an existing list's metadata (displayName, description, etc.).

[Rest API] Delete a list

Delete an entire list from a SharePoint site.

[Rest API] Update a column definition

Update column definition properties (displayName, required, etc.).

[Rest API] Delete a column definition

Delete a column definition from a list.

Manual configuration

Microsoft Lists destinations can also be manually configured to send data to any valid Microsoft Graph API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Microsoft Graph APIs expect JSON request bodies. For update operations, include the ID of the list, item, or column to be updated at the end of the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Microsoft Lists endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Microsoft Lists endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.