BetaTesting connects to the tools your team already uses, and it can be reshaped to look and behave like part of your own product. Some of that is self-serve, set up by you in a few minutes. Some of it is a custom integration built with your account manager.
Reach for this when your engineers want beta issues in their backlog rather than in another tab, when your support team needs to see whether the customer on the phone is in a beta, when your security team requires everyone to sign in through your identity provider, or when you want your community to feel like your brand rather than ours.
Integrations depend on API access, which is part of Subscription and Enterprise plans, so some of this may not be available on your account. The Integrations page is also limited to full admins who are super admins of the company.
Where to find the integrations page
Click your company settings in the left menu.
Click Integrations.
The page has four tabs: BetaTesting API, Single Sign-On, Community OAuth, and Recipe Library.
BetaTesting API
Use the BetaTesting API to manage tests, testers, surveys, and issues programmatically. The tab links to the full API documentation, and it is where you create and revoke your credentials: a Static Token, a single long-lived token best for server-to-server scripts, and OAuth2 Clients, for applications that authenticate on their own behalf. See API authentication for how to create, store, and revoke each one.
The same tab holds Webhooks, which push events to a URL you own rather than making you poll for them. You can subscribe to events covering tests, issues, testers, activities, messages, community membership, and shipments. See webhooks overview and setup for the events available and how to point them at your endpoint.
Single Sign-On
Single sign-on lets your people reach BetaTesting with their corporate credentials instead of another password. BetaTesting supports SAML 2.0, and the setup wizard has presets for Okta, Microsoft Entra ID (Azure AD), Google Workspace, OneLogin, and JumpCloud, plus a generic option for any other SAML provider.
The wizard walks you through connecting the provider, mapping your identity provider's groups onto BetaTesting roles, and reviewing before you go live. A connection stays in draft until you enable it, so you can set it up and test it without locking anyone out. See the single sign-on overview to plan a rollout.
Community OAuth
Community OAuth lets testers sign up for your community through an account they already have with another service, which is useful when your product depends on data from that service. Click Add connection, choose the provider, add your client ID and client secret, and enable it. Strava is the provider currently offered.
If you remove a connection, testers who signed in through it keep their accounts, but they can no longer sign in that way.
Recipe Library
BetaTesting can build custom integration recipes. Recipes follow an "if this, then that" model, so anything available through the API or sent by a webhook can trigger work in another tool. The tab lists popular categories as examples, and recipes can be built for other platforms too.
CRM, such as Salesforce and HubSpot, for handling data privacy requests, giving sales and support visibility into who is in a beta, and pulling customer attributes into custom profile fields for segmentation.
Data warehouses and visualization, such as PowerBI, Tableau, Snowflake, Looker, and BigQuery, for exporting survey responses, issue reports, and tester activity into your own analytics stack.
Issue and task management, such as Jira, Asana, ClickUp, Linear, Azure DevOps, and Monday.com, for turning tester-submitted issues into tickets and keeping statuses in step.
Communication and notifications, such as Slack, Microsoft Teams, SendGrid, and Mailchimp, for alerting a channel when something happens or triggering an email workflow.
Customer support, such as Zendesk, Intercom, and Freshdesk, for attaching beta history and submitted feedback to support tickets.
Product management, such as Productboard and Aha!, for feeding tester feedback and feature requests into your roadmap.
Contact your BetaTesting account manager to get a recipe built.
Integrations set up on a single test
Two integrations live on the test itself rather than on the company integrations page. Open a test, click Advanced Settings, and you will find them there.
Jira Integration connects that test to a Jira project so issues submitted by testers become tickets. It is self-serve and one way. See push issues to Jira for the setup steps and auto-push.
Discourse Integration creates a private discussion forum for the test when it launches.
Customizations
Beyond integrations, several parts of BetaTesting can be shaped to your organization. Most are found in your company settings.
Company branding puts your logo, your colors, and your own subdomain on the experience your testers see.
Tester profile fields let you define the fields you want to collect and track for your testers, such as serial number, product model, or membership tier. You can collect them from participants or set them yourself.
Custom test fields do the same for data you track per test.
Custom issue fields let you add your own fields to the issue submission form, so reports arrive with the details your engineers need.
Tester onboarding customizes what new members see when they join your community.
Things to know
The Integrations page appears greyed out if you are not a super admin of the company, even if you are a full admin.
API credentials are shown in full once. If you lose a secret, delete the client and create a new one.
Custom recipes are built with your account manager rather than configured by you, so allow time for scoping.
Availability varies by plan. Project (Pay as You Go) accounts have the core platform, Subscription plans add API access and more customization, and Enterprise is aimed at mid-market and enterprise customers who need advanced features, deeper customization, and stronger security controls.