Integrations
Last updated: 2026-05-18
SaaSy connects to your existing tools so health scores and churn predictions reflect real data — not guesses. All connectors live under Settings > Integrations in the app.
Available connectors
| Connector | Category | Auth method | What it provides |
|---|---|---|---|
| Stripe | Billing | OAuth / Webhook | Subscriptions, MRR, invoice aging, payment failures |
| HubSpot | CRM | OAuth | Contacts, deals, engagement activity |
| Salesforce | CRM | OAuth | Contacts, accounts, opportunities |
| Jira | Project management | OAuth | Issue count, sprint velocity, delivery health |
| Mailchimp | Email marketing | API key | Campaign open/click rates, audience lists |
| SendGrid | Email marketing | API key | Campaign delivery and engagement data |
| Google Ads | Paid ads | OAuth | Ad spend, conversions, ROAS |
| Meta Ads | Paid ads | OAuth | Ad spend, conversions, campaign performance |
Additional connectors (Intercom, Slack, Discord, Gmail, Outlook, Google Calendar, GitHub) are in the integrations page and can be connected, though their data feeds into the platform differently. Contact support@hellosaasy.ai for details on which signals each one contributes.
OAuth flow walkthrough
For OAuth connectors (Stripe, HubSpot, Salesforce, Jira, Google Ads, Meta Ads):
- Go to Settings > Integrations and click Connect on the connector.
- A pop-up or redirect takes you to the provider's OAuth consent screen.
- Review the requested permissions (listed below) and click Allow or Authorize.
- You are redirected back to SaaSy. The connector status changes to Connected.
- SaaSy begins an initial data sync. For large accounts this may take a few minutes.
What permissions each OAuth connector requests
Stripe
- Read access to customers, subscriptions, invoices, and payment methods.
- Write access is not requested — SaaSy is read-only for Stripe data.
- Stripe webhook registration (see below) is set up automatically.
HubSpot
crm.objects.contacts.read— contact list and activity.crm.objects.deals.read— deal stages and values.timeline— engagement timeline events.
Salesforce
apiscope — standard Salesforce API access for contacts, accounts, and opportunities.refresh_token— allows SaaSy to sync without requiring re-auth.
Jira
read:jira-work— issues, sprints, and project metadata.read:jira-user— user assignment data.
Google Ads
https://www.googleapis.com/auth/adwords— campaign, ad group, and conversion data (read-only).
Meta Ads
ads_read— campaign performance and spend data.ads_management(read-only scope) — creative and audience metadata.
API key connectors
Mailchimp — paste your Mailchimp API key when prompted. Find it under Mailchimp Account > Extras > API Keys. SaaSy stores this key encrypted at rest.
SendGrid — paste a SendGrid API key with at minimum Mail Activity read permission and
Marketing read permission.
Stripe webhook setup
Stripe requires an inbound webhook to send real-time events (payment failures, subscription cancellations, etc.) to SaaSy.
When you connect Stripe via OAuth, SaaSy automatically registers a webhook endpoint at:
https://api.hellosaasy.ai/api/v1/webhooks/stripe
Events listened for:
customer.subscription.updatedcustomer.subscription.deletedinvoice.payment_failedinvoice.payment_succeededcustomer.updated
If you need to register the webhook manually (e.g., using a Stripe restricted API key instead of OAuth), go to your Stripe Dashboard > Webhooks, add the endpoint above, and select the events listed. Retrieve the webhook signing secret and enter it in SaaSy under Settings > Integrations > Stripe > Webhook secret.
Sync frequency
- Event-driven — Stripe webhook events arrive in real time (seconds).
- Polling sync — HubSpot, Salesforce, Jira, and ad platforms sync every 60 minutes.
- Manual sync — Click the refresh icon on any connector to trigger an immediate sync.
Disconnecting an integration
Click the Disconnect button on any connected integration. SaaSy stops syncing data but does not delete historical data already imported. Customer records and health scores are preserved — they will simply stop updating from that source.
Data and privacy
SaaSy reads and stores only the minimum data needed to compute health scores. No payment card numbers or personally identifiable financial data are stored — only aggregated metrics (e.g., MRR, invoice aging in days). Full data handling details are in the Privacy Policy.