Skip to main content

Set Up the Causeway Connector

The Causeway Connector lets you connect your Causeway account to Airia and ingest documents stored in your Causeway workgroups. Causeway is a construction document management system; once connected, Airia retrieves the files from the workgroup folders you select and makes them searchable inside your project. Connecting Causeway involves two parts:
  1. A one-time OAuth setup performed by an admin, which registers Causeway as an OAuth connector in Airia.
  2. Creating a Causeway data source, where each user authenticates with their Causeway credentials and selects the folders to ingest.

Prerequisites

To use the Causeway Connector, ensure you have the following:
  • A Causeway account with access to the workgroup folders you want to ingest.
  • Your Causeway connection details:
    • Instance URL — the base URL of your Causeway tenant.
    • Username
    • Password
  • A registered Causeway OAuth connector in your Airia tenant (see Set Up the Causeway OAuth Connector below). This is a one-time setup performed by an admin.

Set Up the Causeway OAuth Connector

This one-time setup is performed by an Airia admin (or any user with permission to manage OAuth connectors). Once registered, the Causeway OAuth connector is available to every user in your tenant who creates a Causeway data source.

1. Register an OAuth 2.0 client with Causeway

Before Airia can authenticate users, you need an OAuth client registered with Causeway.
  1. Contact your Causeway administrator (or Causeway support) and request an OAuth 2.0 client registration for Airia. You will need to provide:
    • Application name — for example, Airia Knowledge.
    • Redirect URI — your Airia OAuth callback URL: https://<your-airia-api-host>/v2/OAuth/callback. You can find this in Airia under Settings → OAuth Connectors → New → Callback URL.
    • Grant types — Authorization Code (plus Refresh Token, if your Causeway tenant offers it).
    • Scopesopenid and offline_access. offline_access lets Airia refresh the access token automatically during long folder browsing and ingestion runs, so users don’t have to re-authenticate.
  2. After registration, Causeway returns:
    • Client ID
    • Client Secret — copy and store it securely; Causeway typically shows the secret only once.
    • Authorization endpoint — usually https://<causeway-oauth-host>/oauth/authorize.
    • Token endpoint — usually https://<causeway-oauth-host>/oauth/token.
  3. Confirm with Causeway that the token endpoint accepts Client Secret Post authentication (client credentials sent in the request body). Airia uses this method by default for Causeway. If your Causeway instance only supports Client Secret Basic, note it for the next step.

2. Register Causeway as an OAuth connector in Airia

You can register the connector through the Airia UI or through the Platform API.

Option A — Airia UI

  1. In the Airia platform, navigate to Settings → OAuth Connectors → New.
  2. Choose the Generic OAuth provider type.
  3. Enter the details you collected from Causeway:
    • Name — a recognizable display name, e.g. Causeway or Causeway (Production).
    • Client ID and Client Secret — from Step 1. The secret is encrypted at rest.
    • Authorization endpoint and Token endpoint — the exact URLs Causeway provided.
    • Scopesopenid and offline_access.
    • Token Endpoint Auth Method — select Client Secret Post. (Select Client Secret Basic only if your Causeway instance requires Basic auth on the token endpoint.)
    💡 Important: Setting Token Endpoint Auth Method to Client Secret Post is the most common cause of setup issues if missed. Make sure it is selected.
  4. Click Create. The new Causeway connector appears under Settings → OAuth Connectors → Connected, where it can be edited or deleted later.

Option B — Platform API

If you prefer to register the connector programmatically, POST the connector definition to /v2/OAuth/providers. Replace every <...> placeholder with the values you collected in Step 1 and your Airia API host:
curl --request POST \
  --url https://<your-airia-api-host>/v2/OAuth/providers \
  --header 'Authorization: Bearer <YOUR_TOKEN>' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Causeway",
    "provider": "GenericOAuth",
    "authenticationType": "StaticUserOauth",
    "clientId": "<CAUSEWAY_CLIENT_ID>",
    "clientSecret": "<CAUSEWAY_CLIENT_SECRET>",
    "authorizationEndpoint": "https://<causeway-oauth-host>/oauth/authorize",
    "tokenEndpoint": "https://<causeway-oauth-host>/oauth/token",
    "revokeEndpoint": "",
    "supportedScopes": ["openid", "offline_access"],
    "behaviour": {
        "tokenEndpointAuthMethod": "CLIENT_SECRET_POST"
    }
}'
Field reference:
FieldRequiredNotes
nameYesDisplay name shown in Airia, e.g. Causeway or Causeway (Production).
providerYesMust be GenericOAuth for Causeway.
authenticationTypeYesUse StaticUserOauth — Causeway uses a per-user OAuth flow.
clientId / clientSecretYesFrom Step 1. The secret is encrypted at rest.
authorizationEndpoint / tokenEndpointYesFrom Step 1. Must be the exact URLs Causeway provided.
revokeEndpointNoCauseway does not currently expose a revoke endpoint; leave as an empty string.
supportedScopesYesAt minimum openid. Include offline_access so Airia can refresh tokens.
behaviour.tokenEndpointAuthMethodNoDefaults to CLIENT_SECRET_POST. Set to CLIENT_SECRET_BASIC if Causeway requires Basic auth on the token endpoint.
A successful response returns the new connector configuration. Airia uses it automatically when users authenticate Causeway data sources — you do not need to copy any ID into the connector form.
💡 Updating credentials later: If the Causeway client secret rotates, an admin can update the connector (UI) or PUT /v2/OAuth/providers/{id} with the new clientSecret. Existing user credentials issued under the old secret keep working until they expire; new authentications use the updated secret.

Register Your Causeway Credentials

Airia uses a Causeway credential — your Instance URL, Username, and Password — to call the Causeway API and retrieve your files. This credential is stored at the tenant level, so each tenant points at its own Causeway instance, and it can be reused across every Causeway data source you create. You can register the credential ahead of time in Settings → Credentials, or create it inline the first time you authenticate a data source (see Authenticate with Causeway below). To register it ahead of time:
  1. In the Airia platform, navigate to Settings → Credentials and click Add Credentials.
  2. Enter a descriptive Name that will help you identify it later (e.g., Causeway – Production).
  3. Select Causeway as the credential type.
  4. Enter your Causeway connection details:
    • Instance URL — the base URL of your Causeway tenant.
    • Username
    • Password
  5. Select the Scope the credential applies to.
  6. Click Create.
The credential is stored encrypted and becomes available to select whenever you create or edit a Causeway data source. For more on creating, editing, and scoping credentials, see Credential Management.

Create a Causeway Data Source

1. Add a New Causeway Data Source

  1. In your project, navigate to Data Sources and click Add data source.
  2. Select Causeway from the Communication & Collaboration category in the connector library.

2. Authenticate with Causeway

  1. Click Authenticate with Causeway.
  2. Choose your credential:
    • Select an existing credential — if you already registered a Causeway credential (see Register Your Causeway Credentials), select it from the list.
    • Create a new credential — enter the three required fields:
      • Causeway Instance URL — the base URL of your Causeway tenant.
      • Causeway Username
      • Password
  3. A credential created here is saved and can be reused across other data sources in your tenant.

3. Select Folders to Ingest

After authenticating, Airia opens the Causeway folder picker. Browse the workgroup tree and select the folders you want to sync.
  • You can select entire folders, individual subfolders, or a mix. A folder appears partially selected when only some of its children are selected.
  • Selecting a folder syncs everything within it, including subfolders and their files.
  • If your access token is refreshed during selection, Airia stores the updated tokens automatically — no re-authentication needed.

4. Finish Setup and Monitor Ingestion

Save the data source. The page refreshes to show the ingestion status. You can revisit the data source at any time to view the current state of synced files — the original Causeway folder hierarchy is preserved in the data source view.

How Sync Works

Causeway syncs incrementally. The initial sync ingests all files in the folders you selected. On subsequent syncs, Airia picks up new and changed files in those folders without re-ingesting everything, keeping the data source up to date with your Causeway workgroups.

Editing Your Folder Selection

To change which folders are synced, open the data source and click Edit. You may need to re-authenticate.
💡 Note: If you re-authenticate with different Causeway credentials, the folder picker will not show your previous selections, and you will need to reselect everything.

Permissions

Access to ingested Causeway files is governed at the Airia data-source level. Any user with access to the Airia data source can retrieve any file that was ingested into it; per-file Causeway permissions are not enforced at retrieval time. Manage who can use the data source accordingly.

Troubleshooting

IssueCauseWhat to do
”Credentials are invalid” error in the folder pickerUsername, password, or instance URL incorrectRe-enter your credentials and verify the instance URL matches your Causeway tenant.
Generic authentication error in the folder pickerOAuth token expired or refresh failedRe-authenticate the connector. If tokens were refreshed mid-session, Airia should have stored them automatically.
Folder picker shows no foldersThe account has no access to any workgroup, or credential validation failed silentlyConfirm in Causeway directly that the account can see workgroup folders.
OAuth popup shows “invalid client” / “redirect_uri mismatch”The redirect URI registered with Causeway doesn’t match the Airia callbackVerify the redirect URI registered with Causeway exactly matches https://<your-airia-api-host>/v2/OAuth/callback (no trailing slash, correct host).
OAuth popup shows “invalid_scope”The Causeway client wasn’t granted openid or offline_accessAsk your Causeway admin to enable those scopes, or remove offline_access from the connector’s scopes (users will then need to re-authenticate when tokens expire).
Token refresh fails after the first houroffline_access scope missing, or token endpoint auth method mismatchEnsure offline_access is included. If Causeway requires Basic auth on the token endpoint, set the Token Endpoint Auth Method to Client Secret Basic.

Next Steps

After your data has been successfully ingested, the Causeway data source is ready to be used with an Agent.