Skip to content

Integrating SailPoint with Flowlu

Flowlu is a cloud-based business management platform that combines CRM, project management, task tracking, finance, document handling, and team collaboration in a single workspace. This document provides instructions to configure a new direct connection to a Flowlu source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Flowlu connector supports the following:

Account Management

  • Aggregate Users

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

  • An administrator-level user on the Flowlu tenant.
  • Supported authentication type: OAuth 2.0 Refresh Token grant. The connector exchanges a long-lived refresh token at the Flowlu token endpoint to mint a short-lived access token.
  • An OAuth 2.0 application must be registered in the Flowlu tenant to obtain the client_id and client_secret. The owning administrator then completes the authorization code flow against https://{tenant}.flowlu.com/oauth2/authorize to obtain the initial refresh_token.
  • For more information about OAuth registration and token exchange, refer to the Flowlu API OAuth 2.0 documentation.

Required Permissions

  • API credentials in Flowlu come from a registered OAuth 2.0 application plus a refresh token authorized by an administrator-tier user. It is recommended to provision a dedicated Flowlu user as the OAuth grantor (for example, an automation/service identity) and use that user’s refresh token rather than a human’s personal authorization.
  • The Flowlu user who grants the OAuth authorization must hold an administrator-tier role so that the resulting access token can receive the full organization-wide user list.
  • Non-administrator grantors will receive a restricted or empty user list.
  • For more information about OAuth 2.0, user management, and custom applications, refer to the following resources:

Note

The linked document is not maintained by SailPoint and is subject to change without notice.