Sage 300 CRE

Finance and operations

Built when you ask for it

Sync Sage 300 CRE job cost, AP and contracts. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Sage 300 CRE connector syncs jobs, job cost, AP, contracts into analytics-ready tables in your data warehouse. Ingest builds it on request, handling auth, pagination and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Jobs
  • Job cost
  • AP
  • Contracts

How it gets built

  1. Choose Sage 300 CRE when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Sage 300 CRE's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Sage 300 CRE itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API credentials issued by the vendor. Sage 300 CRE gives API access to its customers on request. Ask your Sage 300 CRE administrator or account manager for read-only API credentials; Ingest tells you exactly which values it needs when it builds the connector.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Sage 300 CRE connector?
Not as a finished connector yet. Ingest builds it from Sage 300 CRE's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Sage 300 CRE data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Sage 300 CRE API documentation: https://www.sage.com/en-us/products/sage-300-construction-and-real-estate/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for ERP teams: Ramp, SAP, Oracle NetSuite, Microsoft Dynamics 365, Workday, Odoo.

Request Sage 300 CRE