Home › Integrations

Connections that say what they are

A connection is something your workspace authorises, not a logo on a page. Each integration below shows its true state in the product — connected for your company, or not yet — and the Assistant proposes work through it only once it is.

Prices are published at launch; every account starts with a trial. No card to start.

Email and calendar

Gmail

Read the mailbox for review, draft replies in your voice, send only after approval, from your own address. Gmail details

Google Calendar

Check availability, find meetings, and propose scheduling, rescheduling or cancelling — each an approved action. Calendar details

Google Contacts

Contacts synchronised into the CRM so the Assistant knows who a name refers to.

SMTP / IMAP

Any mailbox by protocol: IMAP for review, SMTP for approved sends. Credentials are sealed at rest.

CRM, chat and events

HubSpotPro and above

CRM records in HubSpot, read and updated through approved actions. HubSpot details

SlackPro and above

Notifications and approvals where your team already is. Slack details

WebhooksPro and above

Business events delivered to your systems with signatures and retries.

Stripe ConnectAdvanced and above

Authorise and verify a Stripe account for taking payments and refunds — both financial actions with their own approval level.

How connecting works

Authorise

OAuth for Google, HubSpot, Slack and Stripe; host, port and credentials for SMTP/IMAP. State is checked on every callback.

Scope

The connection is the company's, not the person's. Another workspace's authorisation never carries your work, and vice versa.

Use, with approval

Reads run when authorised; every external send, invite or charge waits for the approval level its risk class requires.

Disconnect

A destructive action in its own right, recorded like every other.

Questions people ask

What happens if a connection is not set up yet?

The Assistant tells you the action needs a connection that is not there, names it, and does nothing. It never pretends the work happened.

Are credentials stored?

Connection settings are sealed at rest and never returned to the browser or written to logs.