Integrations overview
Alzar connects to outside services so work done in Alzar (estimates, invoices, payments, hours) flows to the tools a business already uses. Alzar stays the system of record: other tools receive data from it, and where data comes back (for example a payment) it updates the matching Alzar record only.
Catalog
| Area | Service | Who connects | Status |
|---|---|---|---|
| Payments | Stripe (card) | Workspace admin | Live |
| Payments | PayPal (and Venmo where offered) | Workspace admin | In development |
| Payments | Moov (ACH bank transfer) | Workspace admin | In development |
| Accounting | QuickBooks Online | Workspace admin | In development |
| Accounting | Alzar Books (sibling ledger) | Platform | Beta |
| Payroll & HR | Gusto | Workspace admin | In development |
| Payroll & HR | Payroll / 1099 CSV exports | Workspace admin | Live |
| Payroll & HR | ADP | n/a | Planned |
| Calendar, Drive, Analytics, Places, Sign-In | Admin / users | Live | |
| Local Services Ads lead intake | Workspace admin | Live | |
| Messaging & email | SMS, transactional email | Platform | Live |
| Data & AI | Gemini AI features, speech-to-text | Platform | Live |
| Data & AI | Retail material price reference | Platform | In development |
Principles that apply to every integration
- Connect once per workspace. Credentials and tokens belong to the workspace that connected them and are never shared across workspaces.
- Alzar does not hold your money. Payment integrations route funds directly to the workspace's own account.
- No raw bank or card numbers on Alzar servers. Card and bank details are collected by the payment provider's own hosted components.
- One-way by default. Data flows from Alzar to the other service; only specific events (such as "invoice paid") flow back.
- Disconnect any time from Settings → Connectors.