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
- Remove a blueprint installationRemoving a blueprint installation archives every component it created in one step: its collections, stages and pipelines, templates, filters, and automations. Do it soon after a mistaken install; once your own work depends on those components, removing them takes that work down with it.
- Integration limits and quotasThe limits that matter when connecting Sonta to other services are few and fixed: incoming webhooks accept 60 requests a minute per address, automated sending is capped at 1 to 50 emails a day per step and per mailbox, an Apollo import takes up to 100 people, and a web image address can be up to 2,048 characters. The rest are set per connection or per field.
- Rebuild your site when entries changeTo rebuild your site when content changes, create an automation that runs when an entry is published, unpublished, or edited, and give it a webhook step that calls your site's rebuild address. To avoid a rebuild for every single edit, have the trigger collect changes into one run every 15, 30, 60, or 240 minutes, or once a day.
- Measures and aggregationsA report's measure is the number it calculates: a count of entries, or the sum, average, minimum, or maximum of one field. Only number, price, currency, and rollup fields can be summed or averaged, so a value you want to total has to be stored as one of those types.
- Unsubscribes and consentEvery email an automation sends can carry a personal unsubscribe link. When a recipient uses it, their address is added to the business's suppression list, and automated emails to that address stop across the whole business, whatever collection it sits in. Email apps that offer one-click unsubscribe use the same mechanism.
- The booking modelBooking in Sonta is a chain: a business has locations, a location has departments, a department keeps working hours and exceptions, and a bookable collection has a profile that points at one location and department and turns their hours into slots. A booking is an ordinary entry in that collection whose start time sits on a free slot.
- Inspect an automation runTo see what an automation did, open its recent runs, pick one, and read each step's status and, for a failed step, its error. A run can look successful and still have done nothing, such as sending zero emails, so read the skip reasons too. Fix the cause, check it with a dry run of the step, then replay the run.
- Reuse an asset across entriesTo use the same image or file on several entries, pick the existing asset from the Asset Library in each entry's media field instead of uploading it again. Every entry points at the one asset, Sonta keeps track of where it is used, and replacing its file updates every entry at once.