Connections, with honest status

Bring the work together.
Connect it properly.

Principal starts with a capable private workspace and connects to more of your business as the workflow requires it. Some connections are ready now, some are configured during onboarding, and others remain planned product work.

Available nowSet up with youPlanned
PPrincipalPrivate workspace
Telegram
Web & browser
Email
Calendar
LINE
CRM & records
Available now

A useful foundation before the first extra login.

Every Principal tenant begins with these capabilities. They do not require a customer to grant access to Gmail, a CRM, or another third-party account.

TGAvailable

Telegram

A private owner channel restricted to the numeric Telegram account supplied during onboarding.

Customer channel
WBAvailable

Browser and web

Search, read websites, compare sources, and complete approved browser or form steps in an isolated customer session.

Research & browser tasks
DFAvailable

Documents and files

Read, extract, organise, create, and work with files inside the customer workspace.

Document work
BMAvailable

Business memory

Keep onboarding context, managed instructions, daily memory, tasks, and customer-created project files together.

Private workspace context
VNAvailable

Voice notes and media

Capture voice notes, media, and other inputs through the runtime when the selected customer channel supports them.

Capture & processing
APAvailable

APIs and code

Use customer-approved APIs, shell tools, code, and internet access inside the isolated tenant boundary.

Custom connection foundation
Connected during setup

Add a system because the workflow needs it.

These connections require customer authorisation, credentials, API access, or a managed integration decision. They are not automatically active just because the name appears here.

EMSetup

Business email

Connect a customer-owned mailbox or provide a separately managed tenant inbox with its own credentials and audit state.

GmailOutlookIMAP/API
CASetup

Calendars and meetings

Use customer-authorised calendars and meeting systems for preparation, scheduling, notes, reminders, and follow-up.

Google CalendarMicrosoft 365ZoomMeet
CRSetup

CRM and lead records

Read and update the records selected for the workflow, with approval policy around important changes.

HubSpotCustom CRMProperty CRM
DSSetup

Documents and spreadsheets

Work with shared business documents when the customer grants the right file and account access.

DriveSheetsMicrosoft filesNotion
BFSetup

Forms and websites

Turn website enquiries, booking forms, portal updates, and structured pages into a controlled workflow.

Website formsBooking toolsPortals
BISetup

Business systems

Connect the software your business already depends on when a safe API, export, browser flow, or vendor route exists.

ListingsEventsAccountingOperations
Planned product connections

Keep the important future channels visible.

These remain good product ideas and are expected to matter—especially for businesses in Thailand. They are shown as planned until the connection, permissions, audit trail, and failure handling are ready for customer use.

Tell us what to prioritise
LI

LINE

Owner and customer-facing messaging for the Thai market.

Planned
WA

WhatsApp

Approved conversations and business messaging workflows.

Planned
WC

Website chat

Move qualified conversations into the same business context.

Planned
ST

Slack & Teams

Internal team requests, summaries, and approval prompts.

Planned
GM

Native Google & Microsoft

Broader one-click account connections and permissions.

Planned
AC

App catalogue

Reusable connectors for popular CRM, support, and operations tools.

Planned
How a connection earns its place

A login is not an integration.

A reliable connection needs a clear job, the minimum useful permission, an approval policy, and a failure path.

1

Name the job

Define exactly what the workflow should read, prepare, change, or send.

2

Choose access

Use the smallest account, credential, and data scope that can do the job.

3

Set approvals

Decide which actions can proceed and which must wait for a person.

4

Test failure

Verify expired credentials, missing data, retries, and partial results before launch.

Custom does not have to mean fragile

If your system is not listed, start with the workflow.

We can assess an API, webhook, structured export, browser process, or vendor integration route. If the connection is not safe or reliable enough yet, it stays out of production until the missing control is built.

Describe the system and the job
Start with the bottleneck

Which connection would remove the most manual work?

Tell us the app, the data, and the action you want completed. We will separate what is ready now from what needs integration work.

Request a connectionExplore use cases