Octolane is built around a small set of core objects. Everything you do. Every email, meeting, AI field, custom field. Extends them.Documentation Index
Fetch the complete documentation index at: https://docs.octolane.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Core objects
| Object | What it is | How it’s created |
|---|---|---|
| Account | A company | Auto-created from every external email and meeting |
| Contact | A person, linked to one or more accounts | Auto-created from email participants and meeting attendees |
| Opportunity | A deal: account + value + stage + close date | Auto-detected from email patterns, or created manually |
| Task | A first-class to-do with owner, due date, completion | Manual, AI-generated from meetings, or via API |
Activities
Activities are the events that happen on a record’s timeline. They attach to Accounts, Contacts, Opportunities, and Tasks.| Activity | What it is |
|---|---|
| Inbound and outbound messages, auto-threaded to the right record | |
| Meeting | Calendar events, with optional recording, transcript, and recap |
| Note | Free-form text written by you or your team |
| AI action | Field updates, draft sends, stage changes. Every AI move logged with citation |
Custom fields
Add any field to any standard object: text, number, date, select, multi-select, URL, currency, formula, lookup. See Custom fields.AI fields
Fields that fill themselves in by reading conversations. Describe what to track in plain English. Octolane keeps the value current. See AI fields.Custom objects
Available on the Team plan.
How everything connects
- A Contact belongs to one or more Accounts.
- An Opportunity belongs to one Account and has one or more Contacts.
- A Task can attach to an Account, Contact, or Opportunity.
- Every Email, Meeting, Note, and AI action attaches to the relevant Account, Contact, and Opportunity automatically.
- Custom objects can relate to standard objects through lookup fields.