Fits into the systems you already run.
Connectors are configured by your administrators, credentials are encrypted at rest, and every run is logged with what was read and written.
| System | What happens | When | Data |
|---|---|---|---|
| Esri ArcGIS Enterprise | Reads feature services for the asset layers you choose (water mains, streets, parks) and keeps each capital asset linked to its feature by GlobalID. Location, install date and condition flow to Sepal; cost and book value can flow back as attributes. | Nightly, or on demand | Assets, locations, condition |
| Cityworks AMS | Pulls labor hours and material costs from closed work orders and posts them as a balanced journal entry against the work order’s account. Storeroom issues in Sepal are charged to the work order. | Every 30 minutes | Work orders, labor, materials, inventory issues |
| Laserfiche | Archives approved invoices, contracts and personnel documents to your Laserfiche repository with a template you choose, then stores the Laserfiche entry ID on the Sepal record. | When a record is approved | Attachments and metadata |
| CIS Infinity | Imports the daily utility-billing GL summary file and posts it as one balanced entry in the water, wastewater and storm funds. Re-running a file is safe; it’s keyed to the file’s date. | Daily | GL summary by account |
| Power BI | An OData v4 feed of every record type an API key is allowed to read. Department scope and field masking apply exactly as in the app, so analysts never see more than they should. | Live | Any record type |
| JD Edwards EnterpriseOne | A conversion agent that reads JDE through AIS / Orchestrator, a read-only database login or CSV extracts, maps the tables and stages them for validation. Used for conversion and for running both systems in parallel. | During implementation | Masters, balances, history, open items |
For everything else
The same API the Sepal app uses is available to your systems, with keys scoped to exactly what each integration needs.
- REST and RPC API
Every screen in Sepal is built on the public API, so anything a person can do, an integration can do — with the same permission checks.
- Signed webhooks
Subscribe to events like “purchase order approved” or “payroll posted”. Payloads are signed with HMAC-SHA256 and retried with backoff.
- Files your bank and carriers expect
NACHA CCD+ and PPD, positive pay, EDI 834 benefit enrollment and 1099 exports.
- CSV imports with validation
Any record type can be imported from a spreadsheet. Rows are validated and staged first; re-running skips what already exists.