Your systems, connected
The connection needs
to fit the work.
Tell us which systems you use and what you need to read or change. We’ll confirm the connection path and its limits.
Email & calendarTMS & operationsCRM & financeFiles & notes
Shared company contextFreight workflowsFinancial contextCustomer operationsCouncil review
| Source group | Context it can provide | What we confirm |
|---|---|---|
| Email & calendar | Messages, meetings and account context | Accounts, folders, consent and user access |
| TMS & freight systems | Shipment, carrier and lane records | Vendor, version, API scope and record ownership |
| CRM & accounting | Customer and financial context | Source authority, field mapping and currency |
| Files & meeting notes | Documents and operating knowledge | File formats, access, retention and update rules |
A clear status for each connection.
Your proposal should identify each connection as an existing connector, an import, custom implementation or planned work. It should also state the supported read and write actions.
Availability varies by system and setup. We confirm named products during the integration review.
Bring your stack
to the review.
These systems have connector implementations in XecSuite. Your team still needs to confirm access, version and supported actions for the workflow.
| System | Context | Confirm in scope |
|---|---|---|
| Microsoft 365 | Email, calendar and meeting context | Accounts, user grants and allowed actions |
| Google Workspace | Email, calendar and document context | Account access and the data in scope |
| TruckMate | Freight records and supported financial sources | Version, APIs and permitted write actions |
| Power BI | Financial reporting and ledger context | Dataset, refresh rules and reporting periods |
| QuickBooks | Accounting context | Company, fields and currency mapping |
| HubSpot | CRM contacts and customer context | Object mapping, access and sync direction |
Start with the work