Sonta AI Academy
Everything you need to run Sonta AI — from first principles to reference. Start with a guide, or jump straight to what you're looking for.
Browse the docs
- Start HereWhat Sonta AI is, who it is for, and how to get your first business running.
- Core SystemThe model everything is built on — businesses, collections, fields, and how they relate.
- ConfigurationShape your model and control access: collections and fields, views and layouts, users and roles, media.
- OperationsRun the work day to day: automations, booking, email, and reports.
- Site & IntegrationsUse Sonta as the backend for your own site, and connect it to the tools around it.
- DevelopersWork with Sonta programmatically — connect an AI agent or your own code to the same records.
- HelpAnswers to common questions and fixes for what commonly goes wrong.
Recently published
- My automation did not runWork through it in this order: the automation is not active, the trigger is not listening to where your change came from, the trigger does not match what actually happened, a condition stopped the run, or it started and is stuck. The run history tells you which — whether a run exists at all is the first thing to look at.
- What the tools coverThe connection offers purpose-built tools for the work that comes up constantly — reading a collection's shape, finding entries, writing them with validation, checking booking readiness, looking up automation options, inspecting a run, and installing a blueprint — plus step-by-step recipes for multi-step tasks. Prefer them over improvising: they validate input and explain failures.
- Adapt a blueprint to your businessEverything a blueprint installs is ordinary configuration afterwards — rename stages, add or remove fields, adjust its automations, delete what you do not use. Adapt it to your language and process rather than bending your process to its defaults, and change one thing at a time so you can tell what broke if something does.
- Webhooks in and outWebhooks connect Sonta to systems that have no ready-made integration. Incoming: an outside system posts to a private address and starts an automation. Outgoing: an automation step calls another service, optionally with its own headers and body. Between the two, most tools can be wired up.
- SEO fields and metadataSonta gives every entry a URL-safe identifier, and everything else about SEO is fields you add yourself — a search title, a description, a social image — which your site reads and puts in the page's metadata. There is no hidden SEO feature: model the fields, and let the site use them.
- Build a dashboardA dashboard is a screen of panels. Each panel is either a saved report or a pipeline panel showing funnel, velocity, or time in stage. Save the reports you check often, arrange them on one dashboard, and decide whether it is yours alone or shared with the team.
- Create an email templateA template is a reusable message with placeholders that fill themselves in from the record it is sent about — a name, an amount, an appointment time. Write the message once, mark the parts that vary, and every send reads specific rather than generic.
- Make a collection bookableA collection becomes bookable when it has a date-and-time field marked as the bookable one, and a capacity profile saying which location and department the bookings belong to, how slots are offered, and how long each runs. A readiness checklist tells you exactly which piece is still missing.