Integrations

Works with the tools
your team already uses.

Sign-in, directory sync, alerts and payments connect to these services, through open standards where there are any. Only connections that work in the product today are listed, each with what it shares and where you set it up.

  • 10 integrations available today
  • Updated 23 October 2026

Works with

Services you can connect. Names and logos belong to their owners; showing them is not an endorsement.

Sign-in & directory

People sign in with the work accounts they already have, and joiners and leavers flow in from your directory.

Microsoft Entra ID

Your admins connect it

  • Sign-in
  • Account sync

People sign in with their Microsoft work account, and Entra ID can create, update and deactivate their accounts here automatically.

How it connects
Single sign-onOpenID ConnectSAML 2.0SCIM 2.0
What is shared
At sign-in: the person’s work email and name. With SCIM: each person’s work email, name, department, directory ID and whether the account is active.
Where you set it up
Settings → Security → Single sign-on and Directory provisioning (SCIM) (company administrators)

Okta

Your admins connect it

  • Sign-in
  • Account sync

Sign in through Okta, and let Okta push new starters, changes and leavers to their accounts here.

How it connects
Single sign-onOpenID ConnectSAML 2.0SCIM 2.0
What is shared
At sign-in: the person’s work email and name. With SCIM: each person’s work email, name, department, directory ID and whether the account is active.
Where you set it up
Settings → Security → Single sign-on and Directory provisioning (SCIM) (company administrators)

Google Workspace

Your admins connect it

  • Sign-in

People sign in with their Google Workspace account instead of a separate password.

How it connects
Single sign-onOpenID ConnectSAML 2.0
What is shared
At sign-in: the person’s work email and name.
Where you set it up
Settings → Security → Single sign-on (company administrators)

OneLogin

Your admins connect it

  • Account sync

OneLogin can push new starters, changes and leavers to their accounts here, so access ends when someone leaves.

How it connects
SCIM 2.0
What is shared
Each person’s work email, name, department, directory ID and whether the account is active.
Where you set it up
Settings → Security → Directory provisioning (SCIM) (company administrators)

Alerts & messages

Alerts, reminders and approvals reach the channels your team already watches.

Microsoft Teams

Your admins connect it

  • Alerts

Posts the alerts you choose to a Teams channel, one card each, through a Workflows webhook.

How it connects
Channel alertsIncoming webhook
What is shared
Only the alerts you send there: each one’s title, details and an Open link.
Where you set it up
Settings → Notifications → Delivery channels (Advanced routing), then tick Teams for each event in Events & routing; or Alert emails & Teams on Basic routing (company administrators)

Slack

Your admins connect it

  • Alerts

Posts the alerts you choose to a Slack channel, one message each, through an incoming webhook.

How it connects
Channel alertsIncoming webhook
What is shared
Only the alerts you send there: each one’s title, details and an Open link.
Where you set it up
Settings → Notifications → Delivery channels (Advanced routing: turn Slack on and add the webhook address), then tick Slack for each event in Events & routing (company administrators)

Telegram

Your admins connect it

  • Alerts

Sends the alerts you choose to a Telegram chat or channel, one message each, from your own bot.

How it connects
Chat alertsBot API
What is shared
Only the alerts you send there: each one’s title, details and an Open link.
Where you set it up
Settings → Notifications: in Delivery channels choose Advanced routing, turn Telegram on and add your bot token and chat ID, then tick Telegram for each event in Events & routing (company administrators)

Browser notifications (Web Push)

Each person turns it on

  • Browser alerts

Alerts and reminders show up as notifications in Chrome, Edge, Firefox or Safari on a computer, and a click opens the item in the console. Each message is encrypted so only that browser can read it.

How it connects
Web PushChromeEdgeFirefoxSafari on Mac
What is shared
Each alert, encrypted for that browser alone, passed on by the browser maker’s push service (Google, Mozilla, Microsoft or Apple).
Where you set it up
Each person, once in each browser: Notifications → Settings → Browser push on this device → Turn on

Payments

Pay for your plan online, in rupees, the way you already pay.

Razorpay

Connected by the platform operator

  • Payments

Pay for your plan in Razorpay’s checkout. Your plan or renewal starts only after Razorpay confirms the full amount was paid.

How it connects
Online checkout
What is shared
The amount, your company’s name, the plan and how many licences or PCs it covers, and order references. Card and bank details are typed into Razorpay’s checkout, never into our pages.
Where you set it up
Connected once by the platform operator; then Plan & Billing → Pay & switch, Renew now or Pay now → Card / Netbanking (company administrators)

UPI

Built in

  • Payments

Scan the QR code at checkout with GPay or any UPI app, or pay to the UPI ID shown. The plan activates once the payment is verified against its bank reference.

How it connects
QR codeAny UPI app
What is shared
We send nothing to anyone: the QR code itself carries our UPI ID and account name, the amount, and a note with the plan’s name and the order reference.
Where you set it up
Plan & Billing → Pay & switch on a plan, or Renew now / Pay now → Pay by UPI (company administrators)

How connections are protected

  • Secrets stay secret

    Sign-in client secrets are stored encrypted (AES-256-GCM). A directory token is shown once; only its fingerprint is kept.

  • Alerts go only where you point them

    Webhook addresses must use https, and can’t point at private or internal network addresses.

  • Payments are checked, not assumed

    A plan starts only once its payment is verified, never on a “paid” click alone.

  • Every change is on record

    Connecting, changing or removing sign-in, directory sync or alert channels is written to the audit log your administrators can read.

How we protect your data

Built on open standards

The same connection works with any provider that follows the standard, not only the names above.

  • OpenID ConnectSign-in with a work account
  • SAML 2.0Sign-in with an identity provider
  • SCIM 2.0Accounts created and closed from your directory
  • WebhooksAny system that accepts a JSON post per alert

Product names and logos are trademarks of their owners. They appear here only to say that RobotAiTechnology can connect to their services; it does not mean any of these companies endorses or partners with us.

Need a connection that is not listed?

Tell us what your team uses. We will tell you straight whether it works today.

Book a demo Free trial