Summit Hub
← All guides · Connected workflows

Connected workflows

Connecting Buildxact

Link your Buildxact account so the app can read your jobs, estimates and costs and keep each deal's Buildxact figures up to date.

What it's for

The app reads your Buildxact jobs and estimates to show what's been quoted and what's been spent on each job. To do that it needs a set of Buildxact API credentials for your business. You enter them once on the Buildxact card in Settings; the app looks after signing in to Buildxact from then on.

Before you start

You need three things from Buildxact:

  • your Buildxact username (the email address you sign in with),
  • an API Key, and
  • your Subscription Key.

Step 1: generate an API Key

  1. Sign in to Buildxact.
  2. Go to My Business → API → API Keys. The Buildxact card in Settings links straight there.
  3. Create a new API key and copy it. Keep your Subscription Key from the same area to hand too.

Step 2: enter your details in Settings

  1. Go to Settings and find the Buildxact card.
  2. Paste the API Key, then enter your Username and Subscription Key.
  3. Click Save Settings.

Saving stores those details for the Buildxact sync. The app then tries to swap them for its own short-lived sign-in with Buildxact, and renews that sign-in automatically, so you don't need to come back and reconnect. Saving doesn't tell you whether Buildxact accepted the details: if they're wrong, the save still goes through and no Buildxact data appears (see Troubleshooting below).

The saved keys are never shown again in full. The card shows dots in their place; leave a field empty to keep what's already saved, or type a new value to replace it.

When you need the Tenant ID

Most businesses can leave Tenant ID empty. The app works it out for you when your API key can only reach one Buildxact business.

Fill it in when your API key can reach more than one Buildxact business (for example, if you run several companies under one login). The Tenant ID tells the app which of those businesses belongs to this account, and it's what ties incoming Buildxact updates to your organisation.

Step 3: register the webhook

The webhook lets Buildxact tell the app the moment something changes, rather than waiting for the next scheduled refresh.

  1. In Buildxact, go to My Business → API → Webhooks.
  2. Register a new webhook pointing at /api/webhooks/buildxact on this app's web address (for example https://your-app-address/api/webhooks/buildxact).
  3. Buildxact shows you a signing secret. It's shown only once, so copy it now.
  4. Back on the Buildxact card in Settings, paste it into Webhook Secret and click Save Settings.

Each organisation has its own webhook secret. If you lose it, register the webhook again in Buildxact and paste the new secret in.

What the status pill means

The pill at the top right of the Buildxact card shows where things stand:

  • ✓ Connected: your username, API Key and Subscription Key are all saved. It doesn't check that Buildxact accepts them; data showing up on your deals does. A small "expires" time may show next to it; that's only the current sign-in window, and the app renews it on its own.
  • Not configured: no Buildxact details are saved yet. Follow the steps above.
  • Disconnected: some details are saved but not all three of username, API Key and Subscription Key. Fill in whichever is missing and save again.

Troubleshooting

  • "This Buildxact account is already connected to another Summit account." Those Buildxact details are already in use by a different account in the app. Disconnect them there first, or contact support if you didn't expect this.
  • The pill stays on Disconnected after saving. One of username, API Key or Subscription Key is still empty. Check all three and save again.
  • The pill says Connected but no Buildxact data appears. Check the API key is still active in My Business → API → API Keys and that you copied it in full. If you replaced it in Buildxact, paste the new key in and save. If your key reaches several Buildxact businesses, check the Tenant ID is filled in.
  • Changes in Buildxact take a while to show up. The webhook may be missing or its secret out of date. Check it's registered under My Business → API → Webhooks and that the secret saved in Settings is the one Buildxact gave you. Without it, changes still arrive on the regular scheduled refresh.
  • Still stuck? Contact support. They can see the full reason on our side.