Cross-app data flows
Much of what businesses build integrations for is already connected inside TriostackOne. This reference lists each native flow between apps, with the plan it requires where a plan applies. Plan requirements are per product — the plan of the product named in each flow.
1. Lead capture into CRM
Website → CRM: form submissions on Triostack Website pages create CRM leads instantly, routed to the pipeline you choose. Requires Website Starter or above (form-to-CRM automation).
Wabiz → CRM: new WhatsApp conversations create CRM leads automatically. Requires Wabiz Business or above (CRM & Desk sync).
2. Support conversations into Desk
Mail → Desk: inbound support emails become Desk tickets automatically.
Wabiz → Desk: WhatsApp support conversations are routed into the shared ticket queue. Requires Wabiz Business or above.
Website → Desk: a live chat and help widget can be added to any Website page.
Desk is free on every account, so the Desk side of these flows never needs a paid plan.
3. Customer context across apps
CRM → Desk: the customer context panel shows the customer's CRM history, open deals, and past tickets on every ticket.
CRM → Mail: the CRM context panel shows the sender's deals, tickets, and account history next to each email. Requires Mail Business or above.
4. Sales to delivery and billing
CRM → Finance: a closed-won deal becomes an invoice with the client and value already filled in. Requires Finance Starter or above (automated invoicing from deals).
CRM → Projects: a closed-won deal can spin up a delivery project with the scope and client attached, and the project stays linked to its CRM account or deal. Requires Projects Business or above (client & deal linking).
Projects → Finance: project costs and billing are tracked against actuals for project profitability.
5. People data
HRMS → Payroll: attendance, leave, and salary changes feed each pay run, so payroll starts pre-filled. Automated pay runs require Payroll Starter or above.
HRMS → LMS: new employee records, transfers, and promotions can trigger course enrollment by role, department, or onboarding stage. Requires LMS Starter or above (automated assignment rules).
HRMS → Identity: role changes update a person's access across the platform automatically.
6. Payroll cost into Finance
Payroll → Finance: payroll costs post into Finance after each pay run, for reporting and close. Requires Payroll Business or above (Finance sync) and Finance Starter or above (payroll cost sync).
Best practices
- Check this list before scoping a custom integration between two TriostackOne apps — the connection may only need a plan change, not code.
- When a flow spans two products, check the plan on both sides.
Frequently asked questions
Do I need to configure these flows with code?
No. These are native connections between TriostackOne apps. They're turned on in the products themselves, subject to the plan requirements listed.
Do these flows work if I only use one app?
Each flow needs both apps involved. You can add the second app at any time; your users, permissions, and shared records carry over.