Skip to content

Integrating SailPoint with Tallyfy

Tallyfy is a cloud-based, no-code workflow and process management platform for organizations that need to document, run, and track repeatable business processes and approvals - without flowcharts, spreadsheets, or manual follow-ups. It lets teams turn any recurring task into a step-by-step template, assign steps to people or AI, and get real-time visibility into where every task and approval stands. This document provides instructions to configure a new direct connection to a Tallyfy source.

Note

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

Supported Features

The Tallyfy connector supports the following:

Account Management

  • Aggregate Account (Users)

Entitlement Management

  • User roles are captured as part of the Account aggregation itself (embedded within each Organization User record), so a separate Entitlement aggregation is not required.

Note

This connector is read-only. It supports account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. Roles on the account are captured as part of account aggregation. Separate entitlement aggregation is not required.

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:

  1. Sign in to Tallyfy.
  2. Go to Settings > Integrations > REST API > VIEW YOUR API ACCESS TOKEN, and copy the Organization ID.
  3. Copy and securely store the following details, which are required during connector configuration:
    • Organization ID
    • API Access Token

Note

  • API tokens are tied to the Tallyfy user account that generated them. Deactivating that account or revoking the token immediately invalidates it.
  • Tokens should be transmitted only over HTTPS and stored securely.
  • Tallyfy authenticates API requests using the HTTP Authorization header with a Bearer token in the format: Authorization: Bearer <API_TOKEN>. For the Organization Users endpoint used by this connector, the Authorization header alone is sufficient. Some other Tallyfy API endpoints may additionally require an X-Tallyfy-Client: APIClient header - if you extend this connector to other resources and get a 401 or endpoint not found error, add that header.
  • OAuth 2.0 (application tokens) is also supported for server-to-server/Enterprise integrations, but personal access token authentication is the standard method for direct API integrations.

For more information about Tallyfy API authentication, refer to the Tallyfy API documentation.

Note

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

Required Permissions

  • Admin - Full access, including account settings and API token management.
  • Standard/Light users - Access is scoped to what their role permits within Tallyfy; a token generated under such a user inherits the same visibility.
  • Tokens inherit the permissions of the user who created them. If a user's role doesn't have access to a given resource in the web interface, API calls to that resource will fail with an authorization error, even if the token itself is valid.