Faster time to market
Ship customer-facing Streak automations without custom integration code.
Streak Connector
Embed customer-facing Streak automations that create and update Pipelines and Boxes, sync records from your product, and trigger workflows from Streak webhooks — all surfaced inside your multi-tenant SaaS app.
Per-customer credential management
Manage each customer's Streak key securely per tenant.
Reliable event handling
Use webhooks to trigger timely workflows and reduce polling.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What teams can integrate and automate with Streak
Teams can sync leads and automate pipeline workflows in Streak: list and manage Pipelines and Boxes, create or update Box fields, read Users and Teams, and register webhooks to respond to Streak events. Use Cyclr’s low-code builder to orchestrate multi-step flows, map fields, and publish governed actions into your embedded marketplace.
PRODUCT USE CASES
Top Use Cases for Streak Integrations
Quickly create integrations between your SaaS application and Streak with Cyclr’s low code integration builder. Publish your Streak integration into your application using Cyclr’s white label embedded integration marketplace.
Create lead records in customer pipelines
On app signup create a Box in the customer’s Pipeline and populate custom fields.
Two-way deal field sync
Map product deal state to Streak box fields and update Boxes when state changes.
Start workflows from Streak events
Use Streak outbound webhooks (box created/updated or stage change) to trigger Cyclr flows.
ORCHESTRATION
How Streak works with Cyclr
Cyclr sits between your SaaS product and Streak to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Streak
Streak processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Streak methods you can orchestrate through Cyclr.
Contacts4
Get Contact by Email
ActionGet a contact with the specified email address
Get Contact
ActionGet a contact with the specified ID
List Pipeline Contacts
ActionGet all contacts in the specified pipeline.
List Box Contacts
ActionGet all contacts in the specified box.
Boxes2
List Boxes
ActionThis call lets you get all boxes contained in the specified pipeline.
List Updated Boxes
ActionThis call lets you get all updated boxes contained in the specified pipeline.
Pipeline1
List Pipelines
ActionGets a list of all pipelines
Users2
Get User
ActionGets the public details for the user specified.
List Teams
ActionGets all the teams the current user is on.
Webhooks5
Contact Updated
WebhookTriggered when a contact is updated
Contact Created
WebhookTriggered when a contact is created
Box Created
WebhookTriggered when a box is created
Get Webhook
ActionTask Due
WebhookTriggered when a task is due
TECHNICAL DETAILS
Streak integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Streak integrations in Cyclr.
API and authentication
- API host
https://api.streak.com- Authentication
- API key
- Credentials
Provide the Streak API key (used as Basic Auth username). Generated from the Streak Integrations panel.
- Method categories
Read, Create, Update, Delete, Webhooks (Pipelines, Boxes, Teams, Users)
Pagination and rate limits
Pagination
Streak docs do not document a single global pagination scheme; list endpoints vary. Confirm Cyclr Console paging behavior during setup.
Rate limits
Streak does not publish global rate limits. Implement 429 handling and exponential backoff; confirm limits in Cyclr Console.
IMPLEMENTATION
Authentication at a glance
Streak uses a per-user API key sent via HTTP Basic Auth (API key as username). Cyclr typically accepts the API key; confirm the exact Console option when installing the connector.
- Authentication method
- API key
- Credential required
Provide the Streak API key (used as Basic Auth username). Generated from the Streak Integrations panel.
Before you begin:
View setup guideAPI keys inherit user permissions; SNI SSL may break legacy clients.
COMMON QUESTIONS
Frequently asked questions
It synchronizes Streak Pipelines, Boxes, Users, Teams and webhooks. You can create, read, update and delete Boxes and Pipelines, map custom fields, attach files and react to outbound webhook events to drive cross-app workflows.
Streak uses a per-user API key via HTTP Basic Auth (the API key is used as the username). Generate a key in the Streak Integrations panel and supply it in Cyclr; confirm the Console credential option during installation.
Yes. Cyclr supports per-customer credential mapping so each tenant can use its own Streak API key, enabling one embedded integration instance to serve many customer accounts securely and separately.
Yes. Cyclr lets you expose Create, Read, Update and webhook-driven actions as auditable MCP tools with per-customer credentials, role-based governance and controlled releases.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorActiveCampaign
Related Crms connector for customer-facing integration workflows.
Related connectorBitrix24
Related Crms connector for customer-facing integration workflows.
Related connectorCapsule
Related Crms connector for customer-facing integration workflows.