Skip to content

Integrating SailPoint with Ziflow

Ziflow is a cloud-based online proofing and creative review platform for organizations that need to streamline how creative content moves through review, feedback, and approval across teams and stakeholders. It combines centralized feedback management, automated review workflows, annotation and markup tools, version control, and routing/automation into a single unified system, providing real-time visibility into review status, feedback consolidation, and approval progress - across virtually any creative asset type (images, video, documents, web pages, audio) from first draft through final sign-off. This document provides instructions to configure a new direct connection to a Zoflow source.

Note

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

Supported Features

The Ziflow connector supports the following:

Account Management

  • Aggregate Users

Entitlement Management

  • Aggregate Roles
  • Aggregate Groups

Note

This connector is read-only. It supports account and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

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

Before configuring the Ziflow connector, ensure the following requirements are met:

  1. Sign in to Ziflow with an administrator account (API key access is available to administrators on Free, Standard, Pro, and Enterprise plans).
  2. Go to Settings > API Settings > General to review and manage API access for your account.
  3. Select your profile avatar in the lower-left corner of Ziflow and choose View profile.
  4. Select the API Key tab near the bottom of the profile page.
  5. Select the copy icon next to the key to copy your API Key (generated automatically per user - no separate enable step is required).
  6. Copy and securely store the following details, which are required during connector configuration:
    • API Key (used for header-based authentication on all API calls)
    • Base URL - https://api.ziflow.io/v1

Note

  • Ziflow's API key is tied to an individual user's profile, not the account as a whole - each user with API access generates their own personal key under View profile > API Key. There is no separate company-wide/shared token.
  • Because the key is personal, deactivating or offboarding the staff member who generated it will likely break any integration using it. Ziflow recommends creating the connector under a dedicated service/role-based account (not a named individual) so access isn't lost if that person leaves the organization.
  • Regenerating the key immediately invalidates the old one - there's no documented grace period or dual-key overlap, so any integration still using the previous key will fail right away and must be reconfigured with the new key before it works again.

For more detailed information on obtaining an access token, refer to the official Ziflow documentation: Welcome to the Ziflow API.

Note

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

Required Permissions

Roles That Can Generate Tokens

Ziflow's default roles include User, Manager, Billing, and Admin (Free and Standard editions offer Manager, Billing, or Admin; Pro and Enterprise editions add the User role as well). Since the API Key lives under each individual's own profile rather than a company-level setting, generating a key isn't gated behind a special "API" permission - it's tied to whether the user role has access to Settings at all.

  • Admin - Required at minimum. Admins have access to the Settings area (including API Settings) and can view/copy their own API Key from View profile > API Key. This is the minimum role needed to generate a token for yourself.
  • Account Owner - Has full permissions equivalent to a user assigned all four roles (User, Billing, Manager, and Admin) combined. The Account Owner can also manage account-wide API-related settings under Settings > API Settings > General, transfer ownership, and manage other users' roles - but is not required just to generate a personal API key; Admin is sufficient for that.
  • Manager / User / Billing roles alone - Do not have Settings access by default, and therefore cannot reach the API Key tab, unless an Enterprise admin has explicitly granted them access via Custom Permissions (Settings > Permissions), which lets Enterprise accounts override default role restrictions on a per-feature basis.