Integrations

Native Integrations

Connect Kantos with your favorite tools.

Built-in integrations need no code. This page explains the ones with settings worth knowing about; the Integrations overview lists everything you can connect.

Your sending domain

Email you send from Kantos (automation emails, manual sends and test sends) goes out through SendGrid, Kantos's email provider, so you don't need a SendGrid account. Sending from your own domain gives you reliable delivery, open and click tracking, and bounce handling. If you connect a Gmail mailbox under Communications → Email, emails can go out from that mailbox instead.

Features

  • Email delivery for automation actions and manual sends
  • Event tracking — opens, clicks, bounces, and deliveries are logged per email
  • Domain authentication — verify your sending domain with DNS records for better deliverability
  • Sender management — configure verified sender addresses per organization
  • Inbound email processing via webhook for conversation threading

Setup

  1. Open Communications → Domains and add a domain
  2. Enter the domain you send from (for example company.com). Kantos sends through a subdomain such as mail.company.com, so your existing email keeps working
  3. Add the DNS records shown at your DNS host: three for sending (required), plus MX for replies and DMARC (both recommended)
  4. DNS changes usually show up within minutes, but can take up to 48 hours. Kantos checks while the domain's page is open, and every 15 minutes in the background during a new domain's first week; after that, open the domain and click Check now
  5. Once sending is verified, create your first sender on the same page and send yourself a test email

Deliverability

Authenticating your domain significantly improves email deliverability and prevents your messages from landing in spam folders.

Stripe — payments for bookings

Take payment when customers book. Set up the payment account under Scheduling → Settings: the money collects in your Kantos balance, or goes straight to your own Stripe account. Separately, the Stripe integration under Integrations keeps your Stripe customers in sync with your records.

Your own Kantos subscription is billed through Stripe too. See Billing & Pricing for plans and usage limits.

Supabase auth emails — for your own Supabase project

If your own product runs on Supabase, you can route your end-users' Supabase auth emails through Kantos's branded sending instead of Supabase's default unbranded mailer.

How it works

This is separate from the auth Kantos itself uses to sign you in — it's a feature for customers who also have their own Supabase project and want its signup confirmation, password recovery, magic link, email change, invite, and reauthentication emails sent with Kantos branding and deliverability instead of Supabase's default mailer. Requires a paid plan.

Step

Enable the Feature

Go to Organisation → Supabase Auth Emails, choose a sender, and provide your app’s auth-callback URL.

Step

Copy the Webhook Details

You’re shown a webhook URL and a secret — the secret is shown only this once.

Step

Configure Your Supabase Project

In your OWN Supabase project’s dashboard, go to Authentication → Hooks → Send Email and paste both values in.

Step

Customize & Verify

Adjust branding under the same settings page, then trigger a signup on your app to confirm the email arrives branded.

The webhook secret is shown once

If you lose it, you have to regenerate it (invalidating the old one immediately) rather than retrieve it again.

Setting This Up With an AI Agent

supabase_auth_enable, supabase_auth_get_config, supabase_auth_update_config, supabase_auth_regenerate_templates, and supabase_auth_regenerate_webhook_secret cover this whole flow for an MCP-connected agent — except one thing: pasting the webhook URL and secret into your own Supabase project's dashboard. That's a different product Kantos can't reach into, so it stays a human step; the agent will hand you both values and pick up again once you confirm they're in place.

To change the logo, the agent uploads it with assets_upload, passes the returned id as logo_asset_id to supabase_auth_update_config, then runs supabase_auth_regenerate_templates with logo_only: true, which swaps the logo and keeps any edits you made to the templates. The same uploaded image can go into your other templates in one call with email_templates_replace_image.

Smart Intake — Form Capture

The Smart Intake system automatically captures form submissions from any website. Add a single script tag to your site and Kantos detects, classifies, and routes submissions into your CRM.

See the full Smart Intake documentation for platform-specific guides (WordPress, Wix, Squarespace, Webflow, Shopify, and custom HTML).

Live Chat Widget

Embed a real-time chat widget on your website to engage visitors, capture leads with pre-chat forms, and manage conversations alongside emails in your unified inbox.

See the full Live Chat documentation for installation, customization, and agent management guides.

Slack — Notifications & AI Copilot

Connect a Slack workspace to receive live chat and automation notifications directly in a channel, reply to conversations from a thread, and let your team ask about or update the CRM from Slack itself — via DM, an @mention, or the /kantos slash command.

Features

  • Notifications — route new conversations, assignments, status changes, and automation failures to a channel
  • Thread replies — respond to a live chat conversation directly from its Slack thread
  • AI Copilot — ask questions and make CRM changes from Slack, scoped to each user's own linked Kantos account and role, with every write gated by an explicit confirmation card

Connect and configure Slack under Org → Integrations → Slack. Setting up the AI Copilot (Slack app scopes, environment variables, and the per-user account-linking flow) is covered separately in docs/slack-copilot-setup.md.

Next Steps

Previous
Integrations Overview
Next
Custom Integrations