Integrations
Integrations connect an external system to Una and keep your model fed with its data, so you plan and report against live numbers instead of exported spreadsheets.
All Una integrations are read-only. Una never writes back to the connected system.
The four families
| Systems | What it brings in | Typically feeds | |
|---|---|---|---|
| CRM | HubSpot, Salesforce | Deals, pipelines, stages, owners | Revenue models — pipeline velocity, forecasting, account health |
| ERP | NetSuite, Sage Intacct, Campfire | General-ledger balances and their dimensions (accounts, departments, entities) | Financial models — actuals |
| HRIS | Rippling | Workers, with their legal entity, department, employment type and compensation | Workforce models — headcount and payroll planning |
| File / Storage | Azure Blob Storage, Amazon S3 | Flat files that you upload to Una, or that Una reads from your own storage | Data from systems that Una has no direct connector for |
You can run several integrations side by side, including more than one of the same provider — for example two HubSpot accounts feeding different models.
How a connection is set up
The shape is the same whichever system you connect:
- Create the connection under Settings → Integrations, give it a name and pick the provider.
- Provide credentials. HubSpot uses a one-click OAuth consent; the others use credentials your administrator supplies.
- Map the data — choose which fields or dimensions Una pulls, and map them onto your model.
- Load — run the first sync, then set up a schedule to keep it current.
Steps 3 and 4 are where the providers differ most, so follow the page for the system you are connecting.
Related settings
Integrations use several other areas of Settings, which is why they appear alongside each other:
- Data Sources — where each connection's credentials are stored.
- Staging Tables — where the raw data lands before it reaches your model. Tables created by an integration are managed by Una and shown read-only.
- Data Maps — how staged values are translated into model members.
- Import Definitions — how the staged rows are loaded into the model.
You will not normally edit these by hand for an integration; they are listed so you know what the integration created and where to look.
Keeping data current
An integration does not poll continuously. Data refreshes when a sync runs, either because someone triggers it or because a workflow runs on a schedule. To automate it, add the relevant sync activity to a workflow — see Workflow activities → Integration.
Guides
CRM
- HubSpot — full setup walkthrough.
- Salesforce
ERP
- NetSuite
- Campfire
- Sage Intacct — allow extra time; this one needs preparation inside Sage before you start.
HRIS
- Rippling — your Rippling administrator creates a read-only API token for Una. This needs Rippling's paid API add-on.
File / Storage
- Azure Blob Storage Upload — here you push the files to Una, rather than Una pulling from your system.
- Amazon S3 — Una reads files directly from your own S3 bucket.