Integrations

What it is#

A grid of 38 connectors across ten categories — AI, finance and ERP, communication, code, project tracking, storage, calendar, design, analytics and email. Connecting collects your own credential, spends it against the vendor before saving anything, and spends it again whenever an automation sends something. A bad token comes back as the provider's own words in the form, not as a green tick and silence.

Underneath the grid, a read-only strip lists any third-party applications an outside vendor registered and somebody here authorised.

How to get there#

Work → Integrations in the admin console. Reading the grid needs integration.view. Connecting, testing and disconnecting need integration.manage. The finance cards additionally show ERP connections only to somebody who holds the ERP permission. There is no plan gate on the page.

The API tokens button in the header goes to Security — tokens are a credential and the Security Center owns them, so this page links there rather than growing a second screen over the same table.

How to use it#

Find a tool#

1. Search by name or description, or filter by Category.
2. Filter by Status to see how finished each connector is:

- Live — connected end to end, and features read it. - Verified connection — the handshake is real; the feature that reads it is not built yet. - API only — usable through the API. - No OAuth yet — modelled, no handshake. - Planned.

1. The four counters at the top say how many are connected, how many exist, how many are Live, and how many need attention.

Connect a tool that takes a token#

1. Press Connect on the card. The fields it asks for are declared by that provider's own adapter.
2. Optionally name the account, so two connections of the same vendor are distinguishable.
3. Saving spends the credential against the vendor. A failure shows the provider's message.
4. Re-opening the form never pre-fills a stored secret — an empty box means "keep what is on file", not "the token was lost".

Connect a tool that uses OAuth#

1. Press Connect. Save your app registration, and the browser is handed to the vendor.
2. The vendor sends you back to this page, and the result arrives as a message at the top — connected and verified, or the reason it was not.
3. The card lists the redirect URI and scopes your app registration has to allow.

Connect a finance system#

1. A finance card opens a different form, because connecting one is structural.
2. Set the direction and base URL, then the four ownership switches:

- Invoices & payments — client invoices, payments and write-offs come from there; Projectri mirrors them and will not let anyone edit one here. - Project expenses — imported rather than entered here. - Bill & cost rates — rate cards become read-only in Projectri. - Exchange rates — FX arrives with each sync. Recommended if you invoice in more than one currency.

1. The switches are pre-ticked from what that vendor conventionally owns — a general ledger owns invoices and usually expenses, a bookkeeping tool owns invoices and little else, a CSV drop owns nothing until you say so.

Check a connection is still working#

1. Test re-checks the stored credential and reports what the provider answered.
2. Send test message is a separate, explicitly labelled button on the connectors that can send, because it posts a real message into your own channel.

Review third-party applications#

The Third-party applications section appears only when one has been authorised. It states the vendor's name, whether Projectri has reviewed it, who authorised it and when it was last used. Everything actionable — the scope list and disconnecting — is on Security Center → Connected apps, which owns the credential; two buttons over one revocation is how one of them ends up wrong.

Remove a connection whose provider is gone#

An Unrecognised connections card appears when a stored connection's provider has left the catalogue. Remove revokes it.

What it affects#

• Automation. A connected, sendable provider becomes a target for the automation action "Send to a connected tool". Disconnecting it stops those rules working.
• Finance. Turning on an ERP ownership switch makes a whole class of record read-only across the workspace — nobody can edit an invoice here once the finance system owns invoices.
• Notifications. Slack, Teams and Discord connections here are for integrations. Notification delivery over WhatsApp, SMS and Teams is configured separately on Notification channels.
• Security. Every third-party application listed here is a credential in the same table as your API tokens, revocable from Security.

On mobile#

This screen is web only. Connecting a tool means pasting credentials copied out of another vendor's console, which is a laptop job.

Limits and gotchas#

• A stored credential is never returned. The forms show whether one is on file and offer to replace it; nothing reveals it.
• The readiness label is the honest one. Verified connection means the handshake works and the feature that would use it does not exist yet — it is not a synonym for Live.
• A connected finance system is not a passive mirror. Ticking an ownership switch is what makes records read-only, and untangling that afterwards means changing the switch, not editing the records.
• The grid is not the complete list of software that can reach this workspace. Third-party applications registered by outside vendors can read it without appearing in the grid at all — which is why that strip exists.
• An OAuth connection is not made in the modal: the modal saves the registration, and the vendor's callback makes the connection. If the page never reports back, the callback did not complete.

Related#

• MCP servers — outbound tool servers this workspace calls.
• Webhooks — pushing events out to an address you own.
• Notification channels — WhatsApp, SMS and Teams for notifications.
• Security — API tokens and disconnecting a third-party app.
• Automation — the rules that spend these connections.
• Finance and ERP — what an ownership switch does downstream.