Create an entry

To create an entry, open the collection, add a new entry, give it a name, and fill in its required fields. It saves as a draft unless the collection defaults to published, and it goes through the same checks whether a person, an agent, an import, or your website creates it.

Requirements

• A role that can create entries in this collection.
• The collection exists and has its fields. If not, start with Create a collection.
• Any entries you want to point at already exist. A reference can only point at an entry that is already there.

Steps

1. Open the collection and add a new entry. An entry is one row in the collection (elsewhere: record, item). See Collections and entries for the model.
2. Give it a name. Every collection requires a name of at least three characters. The entry's slug is created from the name unless you set one. Status is required too, but it starts filled in with the collection's default.
3. Fill in the required fields. A published entry needs every required field. A draft can be saved with required fields still empty, so you can finish it later.
4. Connect it to other entries. For each reference field, pick the existing entry it belongs to: the client of a placement, the listing of a showing. See Reference vs multi-reference.
5. Set the location, if the collection uses it. Choose the location and, inside it, the departments the entry belongs to.
6. Leave computed fields alone. Rollups and lookups fill themselves in from related entries. See Rollup vs lookup.
7. Decide on status. Keep it as draft, or set it to published. To schedule it, set a published start date and timezone. See Status and publishing.
8. Save. If a check fails, the field that failed is named along with what it expects. Fix that field and save again.

What gets checked on save

• Permissions: whether your role may create entries here.
• Required and unique fields: a missing value on a published entry, or a value another entry already holds in a unique field, stops the save. See Duplicate value on a unique field.
• Field rules: a rule can limit which values a field accepts, and can fill in or clear a field for you.
• Booking capacity: in a bookable collection, an entry that would overbook a slot is refused.

Other ways to create an entry

The same entry can be created without a form. Ask the agent inside Sonta to create it, or have an agent connected over MCP do it. It can also come from a form on your website, a CSV import, or an automation step. Each way runs the same checks and produces the same kind of entry.

Notes and limitations

• Default status. New entries start as draft in most collections. Collections installed with the CRM blueprint default to published instead, so their required fields must be filled in from the start.
• Owner. If the collection has a field that says who owns an entry, an entry you create is assigned to you unless you choose someone else. Entries from your website, imports, and integrations start without an owner.
• Slug. If the slug is already taken, a numbered suffix is added automatically.
• Stages. In a collection with stages, a new entry lands on the first open stage of the collection's default pipeline unless you choose another.
• Read-only fields. A read-only field accepts a value when the entry is created. After that, only automations can change it.
• Automations on new entries. An automation that runs when an entry is created fires only for the sources it is set to listen to. By default that is the website. An entry you create by hand does not start the automation unless manual entries are included. See Automation triggers.

Related

If an entry refuses to save, see My entry will not save. If it saved but does not show on your site, see My entry does not appear on the site. For a guided first run, try Build your first collection.