Integrations

The Integrations page is an administrator tool for configuring the third-party connections that bring data into ConstructEase. The integrations shown depend on how your organization is set up.

The SupplyPro card configures your SupplyPro connection. You can set the Sync URL and API Key, enter the Portal Credentials used to log in to the SupplyPro portal, and enter the FTP Credentials used to download attachments. The Test Connection button checks that the FTP details work. Save your changes with Save Settings.

View Webhook Requests opens a log of incoming requests, where you can filter by type, acceptance, builder, and errors, and accept orders or change orders.

Trigger Manual Project Scrape opens a form for pulling a single project's SupplyPro data fresh, on demand. By default only projects that already exist in ConstructEase can be re-scraped. Identify the project by its Project ID, its SupplyPro Job ID, or by pasting a SupplyPro Job URL (the Job ID is read from the link for you). If you identify a project that has no Job ID on file, ConstructEase looks the Job ID up automatically from the project's street address, as long as the address matches a single job in SupplyPro. You can optionally set a Builder Name or Supplier to override the values taken from the project. Under Phases, choose what to pull: the schedule, documents, all purchase orders, or any combination. Turn on Create project if not found to have the scrape create the project when no existing one matches, building it from the scraped job details (address, community, plan, lot); this option needs a Job ID or Job URL to identify the job. Turn on Preview only to run the scrape without saving anything, so you can see what would come in first. Click Scrape Project to queue the job. When the scrape finishes, the person who started it gets an email with the outcome and a link to view the project.

When purchase orders are pulled, any memo documents that come with them (schedule notifications, cancellation notices, and notices to proceed) are filed into MEMOS folders in the project's Library instead of alongside the purchase orders. There is one MEMOS folder per trade, and a project only shows the ones for the trades it has enabled.

When configured, the ConstructEase Import Service card sets the source ConstructEase instance that this organization imports project data from, including its source URL and API key, and an option to run the import on an hourly schedule.

When configured, the Dynamics 365 card holds the Finance and Operations integration settings for your organization. A View Request Log option shows the requests sent to Dynamics 365, with filters to find specific projects or failed requests.

The D365 Go-Live Cutoff date sets a boundary for what can be pushed to Dynamics 365. Project shells, phases scheduled, and completions dated before this date are blocked from pushing to Dynamics 365. A Go-Live Cutoff Timezone sets which timezone the date starts in. Leave the date empty to disable the cutoff.

When your organization runs in import-service mode, the Organization API Keys section lets you issue read-only API keys so external systems can pull your builder-imported data. You can create a key, copy it (the full key is shown only once, at creation), and deactivate a key by typing its name to confirm.

The Allow MCP connections setting controls whether people in your organization can connect an AI assistant, such as Claude or Cursor, to read their ConstructEase project data. It is off until you turn it on.

While it is off, the MCP Connections page is hidden from everyone in the organization, so nobody is shown instructions they cannot use.

Turning it off again cuts off every assistant already connected in your organization, the next time one of them tries to read anything. Nobody has to disconnect anything by hand.

Each assistant is connected by an individual person, for themselves. It reads data as that person, so it can only ever see what they can see, and only from the one organization they chose when connecting, apart from settings ConstructEase shares across all organizations. An assistant can read but never change anything.

Each person manages their own connections from MCP Connections in their user menu, not from this page. That is deliberate: connecting an assistant does not require access to Integrations, so neither does disconnecting one.

For the full walkthrough, see MCP Connections.

Integrations is available to administrators with Integrations view permission.

Turning Allow MCP connections on or off requires administrator access. Connecting an assistant, and disconnecting your own, does not — those are available to anyone who can sign in, from MCP Connections in the user menu.