Connect Google Drive, Xero, Zapier and Slack

Use Export to Google Drive from a project to send the latest generated RAMS, CPP and COSHH PDFs to your own Drive. The one-click export creates a The Site Book folder and organises files in a project subfolder. It is an on-demand export, not an automatic per-signature sync. If your account uses named document approvals, a document whose latest version has not been approved yet (never requested, still waiting for approval, or sent back) is skipped, and the export tells you how many were left out. Draft previews are never exported.

Three events: New Project Created, Worker Added to Project, and Document Generated. Zapier can also create a project or add a worker in The Site Book. Generate a personal API key under Settings, then Integrations, and use it in your Zapier dashboard to connect 5,000+ apps. When Zapier asks for a New Project sample during setup, it shows up to three of that account's most recent projects through the same key; create a test project and retry if the list is empty. A key is permanently pinned to the account where you generated it: accepting an invitation or changing your primary account does not move that key or open another account's projects. Generate a separate key for each account you automate; Settings labels every key with its account and offers Generate key for current account whenever the selected account has none. It does not raise your plan or role. Owners and admins can Create Project, while a team member can use account reads, Add Worker and the three account event triggers. Site supervisors are field-only and cannot use account-wide Zapier data.

Because you are signed in as a team member, and only an account owner or admin can start a job. The key is still generated and can read that account, add workers and drive its three event triggers — but any Create Project step will be refused. The notice beside a newly generated or replaced key always describes that key's account and role, even when this login has keys for several accounts. Ask an owner or admin to generate the key from their own login and reconnect the Zap. Changing plan makes no difference, because this is about your role, not your plan. Site supervisors are field-only: they cannot generate a key, and a retained key is paused with role_forbidden if the login is later changed to that role.

Read the error field in Zapier — it names the cause. feature_locked means this account no longer includes Zapier, for example after a downgrade from Pro to Starter: the existing key and event subscriptions are paused, not deleted, and resume when the account returns to Pro or above. role_forbidden means the key belongs to a team member or site supervisor, and only an account owner or admin can start a job: generate the key from an owner or admin login instead. Upgrading will not help that role restriction. free_project_limit can apply only when a Starter account has retained grandfathered Integrations access and already has its one project. A read-only message means the account has moved to Starter with a payment still outstanding, or its subscription was cancelled (a card payment that is only being retried never causes it): the account owner can settle the payment or reactivate under Settings → Billing. entitlement_unavailable means we could not confirm the account's access at that moment — run the Zap again shortly.

A connection must finish in the same signed-in login that started it. When you click Connect Google Drive, Connect Xero or Connect Slack (Business plan and above), the approval screen that follows is tied to your login, and the connection is saved only if you come back to The Site Book still signed in as that same person. If someone sends you a Connect or approval link they started themselves, it is refused and nothing is connected, so another account can never be linked to your Drive, Xero or Slack. The message then reads "this connection was started from a different login". If you were signed out along the way it reads "you were signed out before the connection finished", and a link that is too old or damaged reads "the connection link was invalid or has expired". In each case, sign in as yourself, open Settings → Integrations and click the app's Connect button again. Procore is not yet publicly launched. For Site Control accounts invited to early access, the same login rule applies: on Settings → Integrations click Manage Procore, then Connect Procore, and a refused connection shows the same messages on that Procore page.

Connecting Google Drive, Xero, Slack or Procore saves a new connection. While a card payment is only being retried your plan keeps working, Connect included. Once the account is read-only — its plan has moved to Starter because a payment is still outstanding, or its subscription was cancelled — Connect is refused even though you can still view your existing records and reach Settings → Billing. If the payment state changes while you're approving access with the app, The Site Book checks again before saving and explains that the account is read-only. For Site Control accounts invited to Procore early access, a project, worker, RFI or inspection import also checks the account again before saving fetched changes, so an import already in progress stops if billing makes the account read-only. The account owner can settle the payment or reactivate under Settings → Billing. Once an invited Site Control account is writable again, open Settings → Integrations → Manage Procore and use Import or Re-import for projects, or Sync RFIs or Sync inspections for those records. For another app, use its Connect button under Settings → Integrations.

The Site Book creates client contacts in one Xero organisation, which you choose on Xero's permission screen after clicking Connect Xero on Settings → Integrations. If Xero comes back without an organisation, nothing is connected and the message reads "no Xero organisation was chosen": click Connect Xero again and pick the organisation you invoice from. Your Xero login needs access to that organisation, so if it has none, ask whoever runs your Xero to invite you first. If your Xero login has several organisations, choose only the one you want contacts created in. Sync with Xero is on each project's Overview, in the Export & share card (or inside Documents, export & share). An existing connection that is missing its organisation picks it up from Xero automatically the first time you sync. If Sync with Xero says "No Xero organisation is connected" — for example because the organisation was removed from The Site Book in Xero — click Go to Integrations on that message, then Connect Xero on the Xero card and choose your organisation.

On Business and above: ask "Site Ready" from Slack and it combines the project's compliance state with recent site-channel context into a red/amber/green digest — with the blockers and one-click actions like sending sign-off links. It's on-demand, not a notification feed.

Google Drive, Xero and Zapier come with Pro and above. Slack Site Ready is Business and above. SSO, the read-only REST API and webhooks are Site Control only — see the Enterprise integrations article.