PlatformIntegrations & data
A connection is a request, a credential and a signature. Nothing about it is magic.
This page is the mechanism rather than the promise. Below is one request followed from the thing inside continON that needed it, out past the credential your organization registered, across to a system that never moves, and back into the model — followed by exactly what can be reached that way, and exactly what cannot.
The shape of the answer Five stations, then a closed list of what continON reaches, then a list of what it does not do at all. If a mechanism is configured but unproven, it is named as that.
One request, all the way out and back.
Something inside asks
A report, a form, a workflow step or a screen needs information that continON does not hold. The request is made by the application, not by the person using it.
The credential is fetched
The organization has registered this external system under a name, with its address, an application identifier and a key. The key is held encrypted and is never shown to a user.
The request is signed
Before it leaves, the request is signed with the organization’s key, so the system receiving it can establish that it came from this organization and was not altered on the way.
The outside system answers
It stays where it is, keeps its own data and its own rules, and responds to a request like any other. Nothing about it has to move into continON.
The answer lands in the model
The response is read by the thing that asked for it, under the same organization and seat rules as any continON data — so a report on external data is scoped exactly like a report on internal data.
Inside continONThe boundary itself Outside, and staying there
What can be reached, and what each one needs from you.
Databases you already run
SQL Server, PostgreSQL, MySQL, and Access over OleDB — plus shared files. That is the list, not an example from a longer one.
What it needsA connection continON can use, and a saved query written against it in the data-source builder.
The query & data-source builderTransactional email
Outbound email raised by continON — a notification, a request update, a generated document sent on.
What it needsYour own sending credential and sender identity, held per organization.
Calendar and meeting scheduling
Calendar events created from work inside continON, with a joining link generated for the meeting.
What it needsAuthorisation against the calendar account the events should be created in.
An accounting connector
A named accounting service, over its own authorisation flow.
What it needsAuthorisation against that service.
Not yet proven liveConfigured against the vendor’s sandbox. It has not been verified against a live account, so it is listed here as what it is rather than as a working integration.
External systems you register yourself
Any system that answers over HTTP and can verify a signed request — registered by your organization rather than built into continON.
What it needsA name, an address, an application identifier and a key. continON stores the key encrypted and signs on your behalf.
Why a system can stay where it is
What leaves continON.
- Operational data as Excel or CSV
- Documents and reports as PDF, generated from templates your team designs
And the gap, stated Information leaves continON far more readily than it arrives in bulk. There is no general-purpose importer: bringing an existing dataset in means reaching it where it lives with a saved query, not uploading a spreadsheet. If your evaluation depends on a bulk load, raise it early — it is a scoping question rather than a switch.
What is not here at all.
- Webhooks, in either direction. continON does not publish events for another system to subscribe to, and does not accept them.
- A general-purpose inbound file import. Data comes in by being queried where it lives, not by being uploaded in bulk.
- Payment processing, card handling or any financial rail.
- SMS and messaging-platform delivery. Notifications reach people by email and inside continON.
- Electronic signature.
- Chat and meeting platform integrations beyond the calendar scheduling named above.
Where a connection sits in the layers
Point it at something you already run.
On a sanitized copy of one of your data sources: write the query, then use the result in a report, a dashboard and a form — and see it scoped by the same seat rules as everything else.