Integrations
SaaSy connects to the tools you already use, so the data flowing through your workspace is real rather than re-typed. Connected sources feed whichever modules need them — CRM records, marketing campaigns, payroll and HR systems, bank transactions, and the customer health scores described in Health Scoring.
Most connectors live under Integrations in the sidebar (/dashboard/integrations). Email,
calendar, and bank connections are set up in Settings instead — noted below where that applies.
Business systems
| Connector | How you connect it |
|---|---|
| Stripe | Paste a restricted API key |
| HubSpot | OAuth |
| Salesforce | OAuth |
| Intercom | OAuth |
| Jira | OAuth |
To connect Stripe, open Integrations, find the Stripe card, and paste a restricted API key. Stripe does not use OAuth here — there is no "Connect with Stripe" consent screen. Once connected, SaaSy pulls in customers, subscriptions, and payments.
The Stripe connection above is you connecting your Stripe account as a data source. It is separate from how SaaSy bills you for your subscription — changing one does not affect the other.
Marketing and advertising
| Connector | How you connect it |
|---|---|
| Mailchimp | API key |
| SendGrid | API key |
| HubSpot Marketing | Campaign push, configured separately from the HubSpot CRM connector |
| Salesforce Marketing | Campaign push, configured separately from the Salesforce CRM connector |
| Google Ads | OAuth |
| Meta Ads | OAuth |
Notifications and developer tools
Slack, Discord, and GitHub are connected from the Integrations hub by setting up an inbound webhook rather than an OAuth sign-in. Select the card, then use the webhook dialog to get your endpoint URL and generate a signing secret.
Slack has two connection paths in the app: the hub card sets up a webhook, while
/dashboard/integrations/slack runs a full OAuth connect that can list your channels. If you want
Slack notifications tied to a bot, use the dedicated Slack page. Contact support if you're unsure
which one your workspace should use.
Email and calendar
These are configured in Settings, not the Integrations hub. The hub shows a card for each with a link through to the right settings page.
| Connector | Where |
|---|---|
| Gmail | Settings → Email sync |
| Outlook | Settings → Email sync |
| Google Calendar | Settings → Calendar sync |
| Outlook Calendar | Settings → Calendar sync |
HR and payroll
Connect your existing HR or payroll system to bring employee records into SaaSy.
| Connector | How you connect it |
|---|---|
| Gusto | OAuth |
| Rippling | OAuth |
| BambooHR | Enter your BambooHR subdomain, then authorize |
| ADP Workforce Now | Enter credentials supplied by ADP — there is no consent screen |
Each has its own setup page under Integrations.
Banking
Bank accounts connect through Plaid, under Settings → Connected accounts → Bank. Verified accounts feed the finance module — see Finance.
MCP connectors
The MCP section lets you register outbound Model Context Protocol connectors, then discover and test the tools they expose. This is how SaaSy agents reach systems that don't have a built-in connector.
Receiving webhooks
For providers that support inbound webhooks — Stripe, GitHub, Slack, Discord, Intercom, and Meta Ads — SaaSy gives you an endpoint and a signing secret.
- Open Integrations and select the provider's card.
- Open the webhook dialog. It shows your endpoint URL, in the form
/api/v1/webhooks/in/{provider}/{tenant_id}. - Generate a signing secret and copy it.
- Paste both into the provider's own webhook configuration.
Generate the secret yourself and store it — SaaSy does not create one automatically when you connect.
Syncing
HubSpot and Salesforce support scheduled CRM syncing. Other connectors pull data when their own events arrive, or when you trigger a sync manually from the connector's card.
Troubleshooting
A connector shows as disconnected right after I connected it. Reopen the card and check its status. OAuth connections can fail silently if the authorization window was closed early.
Connect is greyed out. Some OAuth providers require credentials configured at the platform level. If a provider's Connect control is unavailable, email support@hellosaasy.ai and name the provider.
Webhook deliveries aren't arriving. Confirm you copied the full endpoint URL including your tenant id, and that the signing secret in the provider matches the one SaaSy generated.