White-label marketplace
Publish integrations inside your product for customers.

Embed Userpilot-driven in-app experiences and automation for your customers. With Cyclr you can build white-label, customer-facing integrations that identify users, track events, trigger flows and surface Userpilot data inside your product without custom connector maintenance.
Publish integrations inside your product for customers.
Expose vetted Userpilot actions as controlled tooling.
Central retries, monitoring and rate-limit handling.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Cyclr lets product and engineering teams create customer-facing Userpilot integrations and orchestrate multi-step workflows across systems. Use Cyclr’s low-code builder to map tenant credentials, push identities and events into Userpilot, run bulk imports or exports, react to Userpilot webhooks, and expose supported methods as governed MCP tools for end users.
PRODUCT USE CASES
Quickly create integrations that sync user profiles, send backend events to Userpilot, trigger in-app flows from external systems and export analytics. Publish integrations through Cyclr’s white-label embedded marketplace and control which Userpilot actions customers can run.
Automatically upsert identified users and company properties after SSO or CRM sync to keep in-app experiences accurate.
Push server-side events into Userpilot to measure feature usage and drive targeted in-app flows.
Invoke or react to Userpilot events and trigger automations when external product events occur.
ORCHESTRATION
Cyclr sits between your SaaS product and UserPilot to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
UserPilot processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore UserPilot methods you can orchestrate through Cyclr.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing UserPilot integrations in Cyclr.
https://analytex.userpilot.ioAPI token (App token from Environment settings).
Identify users, track events, bulk import and export, delete, analytics, webhooks.
Analytics and exports use cursor-based pagination; many identify/track endpoints are single-request and not paginated. Check each endpoint for details.
Identify and Track APIs typically enforce 600 requests per minute per application token; bulk jobs and exports are often limited to one active job.
IMPLEMENTATION
Authenticate using a Userpilot API token (App token) in the Authorization header; include API version header and use HTTPS for all requests.
API token (App token from Environment settings).
Environment-specific endpoints (analytex vs analytex-eu) and some features require Growth/Enterprise plans.
COMMON QUESTIONS
Cyclr uses each tenant’s Userpilot API token to call Userpilot REST endpoints and to receive webhook events when configured.
Userpilot REST APIs use an API token (App token) supplied in the Authorization header and require HTTPS and an API version header.
Yes. Userpilot supports outbound webhooks for many event types, with signature verification and plan restrictions.
Cyclr can orchestrate retries, backoff and use bulk job endpoints while respecting Userpilot job and rate-limit constraints.
KEEP EXPLORING
Related Product Management connector for customer-facing integration workflows.
Related connectorRelated Product Management connector for customer-facing integration workflows.
Related connectorRelated Product Management connector for customer-facing integration workflows.