# Octolane > This file is very large and may be truncated. For an index of this content, please refer to https://octolane.com/docs/llms.txt instead. > The self-driving AI CRM built for agents and humans. Product guides, company knowledge, MCP, and REST API documentation. # Account settings Source: https://octolane.com/docs/account/account-settings Profile, notifications, password. Settings → Account. * **Profile**. Name, photo, signature, time zone * **Notifications**. Email, in-app, Slack, mobile push * **Password**. Change, set up MFA * **Sessions**. Sign out of other devices # Billing Source: https://octolane.com/docs/account/billing Billing cadence, payment methods, seat changes, upgrades, and cancellation. Open **Settings → Workspace → Billing** to manage payment details, download invoices and receipts, and review your subscription. ## Billing and payment methods * **Founder** is billed monthly by card at \$99 per user/month, for up to three users. * **Pro**, **Team**, and **Enterprise** are billed annually upfront. Payment is available by card, invoice, or ACH. * Pro and Team each include 10 seats; Enterprise includes 20. Extra seats cost \$149/user/month on Pro, \$199 on Team, and \$249 on Enterprise. See [Plans and pricing](/docs/account/plans-pricing) for base prices, included seats, and usage limits. Annual prices shown as monthly amounts are monthly equivalents, not a monthly billing option. ## Changing plans and seats Upgrade at any time; the difference is prorated. Downgrades take effect at your next renewal. Move from Founder to Pro when you need a fourth user, more sequences, custom dashboards, or AI prospecting. Your data, pipelines, and history carry over. [Book a demo](https://cal.com/octolane/demo) for Pro, Team, or Enterprise. For help with an existing subscription or seat changes, email [help@octolane.com](mailto:help@octolane.com). ## Cancellation and data export You can export your data at any time as CSV or JSON, or through the API. See [Exports](/docs/managing-data/exports). If you cancel, Founder access ends at the close of the billing period. Annual plans run through the end of their term. Data is retained for 30 days after cancellation, then deleted. For the latest terms, see the [pricing page](https://octolane.com/pricing) and its [Markdown version](https://octolane.com/pricing.md). # Plans and pricing Source: https://octolane.com/docs/account/plans-pricing Compare Founder, Pro, Team, and Enterprise pricing, included seats, trials, and usage limits. Choose from four plans: Founder, Pro, Team, and Enterprise. Every plan includes the AI CRM, meeting recording, enrichment, website visitor tracking, company brain, Slack agent, REST API, MCP server, and webhooks. All prices are in USD. Pricing checked on November 15, 2026 against the [pricing page](https://octolane.com/pricing) and its [Markdown version](https://octolane.com/pricing.md). Refer to those pages for the latest terms and full feature comparison. ## Prices and seats | Plan | Price per user/month | Included seats and monthly total | Billing | | - | - | - | - | | Founder | \$99 | Up to 3 users; \$99 per user | Monthly | | Pro | \$149 | 10 seats; \$1,490/month | Annually upfront | | Team | \$199 | 10 seats; \$1,990/month | Annually upfront | | Enterprise | From \$249 | 20 seats; from \$4,980/month | Annually upfront | Annual plan totals are shown as monthly equivalents. Additional seats cost \$149/user/month on Pro, \$199 on Team, and \$249 on Enterprise. Move to Pro when you need a fourth user on Founder. ## Founder For founders selling on their own, with up to three users. * AI CRM with deals created from inbox conversations * LinkedIn and email sequences * Meeting recording and notes * Website visitor tracking * Built-in enrichment and automations * Email support and self-serve imports from Attio, HubSpot, or Salesforce [Try Founder free for 7 days](https://www.octolane.com/auth/sign-up). ## Pro For your first sales team. Includes everything in Founder, plus: * Custom reporting and up to 10 dashboards * AI pipeline building from your ideal customer profile * Unlimited sequences * Up to 10 custom objects and their relationships * Buying signals from your website and product * Advanced enrichment and automation * Email and Slack support, an onboarding call, and migration handled by our team [Book a demo](https://cal.com/octolane/demo). ## Team For teams selling across multiple channels. Includes everything in Pro, plus: * LinkedIn, Slack, and WhatsApp sync * Unlimited custom objects, dashboards, and records * Voice dialer in early access * Advanced roles and permissions * Higher enrichment and automation limits * A shared Slack channel, dedicated account manager, and automations built for you [Book a demo](https://cal.com/octolane/demo). ## Enterprise For security, SSO, and scale. Includes everything in Team, plus: * SSO and SCIM provisioning * Security review, custom DPA, and BAA * Two-way Salesforce sync * Custom integrations and data model * A sandbox environment * Unlimited automation, custom enrichment, and custom data retention with audit log export * Priority support with an SLA, white-glove migration, and a dedicated forward-deployed engineer [Talk to sales](https://cal.com/octolane/demo). ## Usage limits | Feature | Founder | Pro | Team | Enterprise | | - | - | - | - | - | | Records | 50,000 | 250,000 | Unlimited | Unlimited | | Enrichment credits/month | 1,000 | 5,000 | 20,000 | Custom | | Automation runs/month | 100 | 500 | 2,000 | Unlimited | | Custom objects | Not included | Up to 10 | Unlimited | Unlimited | | Sequences | 1 | Unlimited | Unlimited | Unlimited | | Sending accounts | 1 | Up to 10 | Up to 25 | Custom | | Dashboards | Not included | Up to 10 | Unlimited | Unlimited | | Company brain version history | 90 days | 1 year | 2 years | Custom | | Field update history | 90 days | 1 year | 2 years | Custom | | Audit log | 90 days | 1 year | 2 years | Custom + export | AI has no separate AI credit charge. Enrichment credits and automation runs have the plan limits shown above. One enrichment credit enriches one contact or company. If credits run out, enrichment pauses until the next month or a top-up. Founder enrichment includes LinkedIn URL, verified email, funding, employee count, and location. Pro and above add advanced enrichment such as hiring, open roles, recent news, and job changes. ## Trials Founder includes a self-serve **7-day free trial**. Pro, Team, and Enterprise offer a custom trial when you [book a demo](https://cal.com/octolane/demo). There is no ongoing free plan; YC companies get Founder free for one year. ## Managing your plan Use your workspace's billing settings to view your plan and payment details. Upgrades are prorated; downgrades take effect at your next renewal. See [Billing](/docs/account/billing) for payment methods, plan changes, and cancellation terms. # Team & Permissions Source: https://octolane.com/docs/account/team-permissions Invite teammates, assign roles, and control who can access and modify your Octolane workspace. Octolane supports team collaboration with role-based access control. Invite your team and set permissions so everyone has the access they need. ## Inviting teammates Go to **Settings → Team → Invite** and enter your teammates' email addresses. They'll receive an invitation to join your workspace. ## Roles Roles and permissions depend on your plan. Founder includes these two roles: * **Admin** - full access. Can customize the data model, edit pipeline stages, manage agents, configure integrations, manage billing, and invite or remove members. * **Member** - standard access. Can view and interact with deals, contacts, companies, and agents. Can approve agent actions for their own deals. Cannot change workspace-wide settings. Pro adds custom roles. Team and Enterprise include advanced permissions. Enterprise adds SSO and SCIM provisioning. See [Plans and pricing](/docs/account/plans-pricing). MCP and REST integrations use the connected member's current permissions; connecting an agent does not grant additional access. ## What happens when teammates join When a new team member connects their email and calendar: * Their existing contacts and conversations are merged into the shared CRM * Duplicate records are automatically detected and merged * The team gets a unified view of all relationships and activity ## Removing team members Admins can remove members from **Settings → Team**. Review record ownership and ongoing workflows when removing a member. Personal API keys created by that member stop working after they leave the workspace. # Workspace Settings Source: https://octolane.com/docs/account/workspace-settings Configure your Octolane workspace - company details, branding, default settings, and agent behavior. Manage your Octolane workspace from **Settings** in the sidebar. Here's what you can configure. ## General * **Workspace name** - your team's workspace name, displayed in the sidebar and emails * **Workspace URL** - your unique Octolane URL * **Company details** - company name, website, industry, and size (used by agents for context) ## Agent settings * **Agent behavior** - control which agents are active and configure their rules * **Approval settings** - set which actions require approval and which can run automatically * **Communication style** - define your team's tone and voice so agents match it ## Data model * **Custom fields** - add, edit, or remove fields on deals, contacts, and companies * **Custom objects** - create new object types beyond the defaults; up to 10 on Pro, unlimited on Team and Enterprise * **Pipeline stages** - customize your sales pipeline stages ## Integrations * **Connected accounts** - manage Gmail and Google Calendar; LinkedIn, Slack, and WhatsApp conversation sync are included on Team and Enterprise * **Signal** - manage the Signal tracking script and configuration * **API keys** - create personal keys in [Settings → API keys](https://www.octolane.com/settings/api-keys) for API, MCP, and compatible integrations * **Zapier** - manage connected automations # Approvals and human-in-the-loop Source: https://octolane.com/docs/ai/approvals Understand automatic CRM updates, reviewed decisions, and the permissions used by external agents. Octolane maintains your CRM automatically and brings decisions to your team when review is needed. Approval behavior depends on the action and workspace configuration; not every record update requires a separate click. ## Review a proposed action * **Approve:** allow the proposed action. * **Edit:** correct the proposal before approving it. * **Reject:** decline the action and provide context when useful. Review the target record, recipients, and proposed change. Your approvals and edits help Octolane learn how your team works. New [company-brain learnings](/docs/ai/company-brain) wait for review before they are retained. ## Configure automatic work Use workspace agent and approval settings to choose which actions require review and which can run automatically. Routine record updates, enrichment, and configured sequences or automations follow those settings and your plan's limits. Follow-up drafts can be reviewed before sending. An authorized sequence or automation can send on its configured schedule, so an individual approval is not required for every message in every workflow. ## External agents and API calls MCP and REST requests act with the connected member's permissions. A write tool or API request can apply a change directly. The in-app approval queue is not a universal review layer for integrations. Configure the external client's confirmations and keep requests within the user's authorization. Read the target record before an update and verify the result afterward. See [Octolane for AI agents](/docs/get-started/agents). # Auto-detecting deals from email Source: https://octolane.com/docs/ai/auto-detecting-deals From 'looks like a deal' to opportunity record. Octolane scans your sent and received mail for buying-intent patterns. When a thread crosses the threshold, it creates or proposes an opportunity according to workspace settings, with: * Account (auto-created if new) * Primary contact * Estimated stage based on conversation depth * Suggested amount when one has been mentioned Review proposed deals when approval is required; automatic creation follows workspace settings. See [How deals are auto-detected from email](/docs/email-calendar/deal-auto-detection). # Auto-filling fields Source: https://octolane.com/docs/ai/auto-filling-fields Watching AI fields update themselves. Define an [AI field](/docs/introductions/ai-fields). Octolane reads every email, meeting, and note on the record and keeps the value current. Updates appear with a small sparkle icon. Hover to see the source citation. Which message, which sentence. Edit manually anytime; manual edits lock the field until you unlock it. # Auto follow-ups Source: https://octolane.com/docs/ai/auto-follow-ups When and how Octolane drafts follow-up emails. When a deal goes quiet past its expected reply window, Octolane drafts a follow-up that: * References the last conversation specifically * Matches your prior tone and length * Offers a clear next step Review follow-up drafts in your [approval queue](/docs/ai/approvals) when manual approval is enabled. Approve, edit, or skip. Configured sequences and automations follow their own authorized schedule and workspace rules. # AI Chat and slash commands Source: https://octolane.com/docs/ai/chat-slash-commands Skills, slash commands, and the AI Chat composer. Open AI Chat with `Cmd+/`. Type freely, or use slash commands: * `/find`. Search any object * `/create`. Opportunity, task, contact, account, note * `/report`. Generate a report inline * `/email`. Draft an email to a contact or thread * `/forecast`. Pipeline forecast * `/explain`. Explain why an AI field has its current value # Company brain Source: https://octolane.com/docs/ai/company-brain Use Knowledge to review, retain, and query what your team learns from sales conversations and outcomes. Octolane's company brain captures what your team learns as it sells: messages that get replies, recurring objections, and the patterns behind closed deals. It combines shared company knowledge with personal context for each rep and uses that context to recommend next actions. Find it under **Knowledge** in the app. Company brain is included on every plan. ## Review what Octolane learns Automatically extracted learning suggestions wait for review before they become approved knowledge. Explicit edits you make in the app or authorize through MCP can apply directly. Review a proposed learning, correct it when necessary, and approve what should become part of your team's knowledge. Changes are version-controlled so you can inspect what Octolane knows and how it changed. This review of new knowledge is distinct from routine CRM updates and the action-specific [approval settings](/docs/ai/approvals). ## Ask questions Ask questions in plain English, such as: * What objections do we hear most often? * Which follow-up approaches have worked for our team? * What have we learned from recent won and lost deals? AI agents can query the same company brain over [MCP](/docs/mcp/overview), using the connected user's permissions. The client discovers the currently available tools and schemas, lists blocks with `memory_list`, and reads their content with `memory_get`. Use `scope: "org"` for shared knowledge, `"user"` for personal knowledge, or `"both"` for both. Pending suggestions are excluded by default. A block can apply to the workspace or a specific account, contact, or opportunity. External agents must read applicable blocks explicitly; activation tags do not automatically supply knowledge to an MCP client. See the [memory tool reference](/docs/mcp/tools-reference#company-brain). Knowledge writes use `memory_upsert` and `memory_delete`. Shared writes require administrator privileges. A request to answer a question does not authorize editing the company brain. ## History and data use Company brain version history is retained for 90 days on Founder, one year on Pro, two years on Team, and a custom period on Enterprise. See [Plans and pricing](/docs/account/plans-pricing). Your team's information is not pooled into a shared model or used to improve other customers' agents. Learning from your team's approvals, edits, and outcomes is used for your own team. See [Security](/docs/security). # AI-drafted outreach Source: https://octolane.com/docs/ai/drafted-outreach Personalized cold outreach to qualified prospects. Point Octolane at an ICP definition and a list (or a Signal feed). It drafts a personalized opening for each prospect using their company news, role, and your past winning patterns. Review proposed outreach according to your [approval settings](/docs/ai/approvals). Configured sequences can send on a schedule. Agentic prospecting and buying intent signals start on Pro; Founder includes one sequence, while Pro and above include unlimited sequences. See [Plans and pricing](/docs/account/plans-pricing). # AI enrichment Source: https://octolane.com/docs/ai/enrichment Built-in and advanced enrichment, monthly credits, and what happens when credits run out. Octolane enriches contacts and companies using built-in data sources. Every plan includes enrichment; available fields and monthly credits depend on your plan. ## Fields **Founder** includes built-in enrichment such as LinkedIn URL, verified email, funding, employee count, and location. **Pro, Team, and Enterprise** add advanced enrichment such as hiring and open roles, recent news, and job changes. Available values depend on the information found for each record. ## Credits | Plan | Monthly enrichment credits | | - | - | | Founder | 1,000 | | Pro | 5,000 | | Team | 20,000 | | Enterprise | Custom | One credit enriches one contact or company. When credits run out, enrichment pauses until the next month or a top-up. Records created by imports, API calls, or MCP do not bypass these limits. AI itself has no separate AI-credit charge. Enrichment credits and automation-run quotas are distinct. See [Plans and pricing](/docs/account/plans-pricing). # How Octolane's AI works Source: https://octolane.com/docs/ai/how-it-works A self-driving CRM that maintains records, prepares and runs sales workflows, and learns from your team's decisions. Octolane is a self-driving AI CRM built for agents and humans. It captures connected conversations and meetings, maintains records, finds deals, prepares follow-ups, and runs configured outreach and automation workflows. Your team reviews decisions that need its judgment. ## The working loop 1. **Capture and update.** Email, calendar, and meeting context creates and updates contacts, accounts, deals, and fields. 2. **Find the next action.** Octolane identifies follow-ups, pipeline opportunities, and relevant customer context. 3. **Act and review.** Routine work follows workspace settings. Proposed decisions and messages can be reviewed, edited, approved, or rejected; configured workflows can run automatically. 4. **Learn.** Approvals and edits inform the version-controlled [company brain](/docs/ai/company-brain), called Knowledge in the app. New learnings are reviewed before retention. See [Approvals](/docs/ai/approvals) for the distinction between automatic updates, reviewed actions, and external API/MCP writes. ## People and external agents Your team can work directly in Octolane or through Claude, ChatGPT, Grok Bot, Cursor, Slack, and other compatible clients. Every plan includes [MCP](/docs/mcp/overview), the [REST API](/docs/api-reference/introduction), and webhooks. External agents act with the connected person's permissions. ## Usage and plans AI is unlimited on every plan, with no separate AI credits. Enrichment credits, automation runs, sequences, and other capabilities have plan-specific limits. See [Plans and pricing](/docs/account/plans-pricing) and [Enrichment](/docs/ai/enrichment). # Meeting recorder and call intelligence Source: https://octolane.com/docs/ai/meeting-recorder Summaries, action items, and extracted fields from calls. The Octolane bot joins Google Meet, Zoom, and Teams calls. After the call you get: * Full transcript with speaker labels * Short and long summaries * Extracted action items as tasks * AI field updates on the linked opportunity * Highlight reel of key moments # Prospecting and sequences Source: https://octolane.com/docs/ai/prospecting-and-sequences Understand AI pipeline building, email and LinkedIn sequences, sending accounts, and channel sync. Octolane combines prospecting, outreach, and CRM updates. Availability and usage depend on your plan; see the [current pricing comparison](https://www.octolane.com/pricing.md). ## Find prospects On Pro and above, describe your ideal customer profile so agents can find matching companies and people and add them to your pipeline. Pro also adds buying intent signals and advanced enrichment. Enrichment consumes your plan's monthly credits. Founder includes website visitor tracking and built-in enrichment. Those capabilities do not imply access to Pro's agentic prospecting or buying intent signals. ## Run sequences Sequences schedule multiple outreach steps across email and LinkedIn. Founder includes one sequence and one sending account. Pro and above include unlimited sequences, with up to 10 sending accounts on Pro, up to 25 on Team, and custom limits on Enterprise. Review your audience, message content, and sending schedule before enabling a sequence. Once authorized, a sequence can send scheduled steps; it does not require a separate manual approval for every message. See [Approvals](/docs/ai/approvals). ## Distinguish outreach from conversation sync Email and LinkedIn sequences are separate from syncing conversations into CRM records. LinkedIn, Slack, and WhatsApp conversation sync is included on Team and Enterprise. The Slack agent is included on every plan. A Slack agent, Slack conversation sync, and Slack support are different capabilities. See [Slack](/docs/tools/slack) and [Plans and pricing](/docs/account/plans-pricing). ## Verify a workflow Check the matched records, audience, sending account, and schedule before launching. After a run, inspect the actual activity and CRM updates rather than assuming a draft was sent or a record was enriched. Automation runs and enrichment credits have separate quotas even though AI itself has no separate credit charge. # Bulk create account fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-account-fields api-reference/openapi.json post /v1/accounts/fields/bulk Creates account custom field definitions in bulk. # Bulk create or resolve accounts Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-or-resolve-accounts api-reference/openapi.json post /v1/accounts/bulk Creates or resolves up to 100 account records in one request. # Bulk delete account fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-delete-account-fields api-reference/openapi.json delete /v1/accounts/fields/bulk Soft-deletes account custom fields in bulk. Each item identifies one field by `id`, `attribute_id`, or `property_name`. System fields cannot be deleted. # Bulk update account fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-update-account-fields api-reference/openapi.json post /v1/accounts/fields/bulk/update Updates account field definitions in bulk. Identify each field by `id` or `property_name`. `property_name` is a stable identifier and cannot be renamed; if you include it with `id`, it must match the stored field `property_name` exactly. # Create or resolve a contact Source: https://octolane.com/docs/api-reference/endpoints/crm/create-or-resolve-a-contact api-reference/openapi.json post /v1/contacts Creates a contact from an email address, or returns the existing contact when the email is already present. Optional profile fields are persisted as attributes when supported. A new contact is linked to the account for its work-email domain before the response returns (`account_id`); the account is created if the workspace has none for that domain. Personal email domains (gmail.com, outlook.com, ...) never get an account. Re-posting an existing contact retries the link. # Create or resolve an account Source: https://octolane.com/docs/api-reference/endpoints/crm/create-or-resolve-an-account api-reference/openapi.json post /v1/accounts Creates an account from a domain, or returns the existing account when the domain is already present. Additional account fields are persisted as system or custom attributes when supported. > [!NOTE] > > **Also use this to look up an account by domain.** This endpoint is idempotent. If an account with the given `domain` already exists, it returns that existing account instead of creating a duplicate. So sending a `POST` with just a `domain` is a safe way to *resolve or fetch* an account by its domain. > > Need to find accounts by other criteria, or match many at once? Use [Search accounts](/docs/api-reference/endpoints/crm/search-accounts) for filtered search. # Cursor-list accounts Source: https://octolane.com/docs/api-reference/endpoints/crm/cursor-list-accounts api-reference/openapi.json get /v1/accounts Returns accounts using cursor pagination with optional search and field projection. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each account's `custom_fields` object. # Cursor-list contacts Source: https://octolane.com/docs/api-reference/endpoints/crm/cursor-list-contacts api-reference/openapi.json get /v1/contacts Returns contacts using cursor pagination with optional search and field projection. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each contact's `custom_fields` object. # List account fields Source: https://octolane.com/docs/api-reference/endpoints/crm/list-account-fields api-reference/openapi.json get /v1/accounts/fields Returns account field definitions, including system fields and custom fields. Use `property_name` as the stable key for custom field values. # Search accounts Source: https://octolane.com/docs/api-reference/endpoints/crm/search-accounts api-reference/openapi.json post /v1/accounts/search Search accounts with structured filters, sort, cursor pagination, and field projection. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each account's `custom_fields` object. # API Reference Source: https://octolane.com/docs/api-reference/introduction Read and update your Octolane CRM with a personal API key. The Octolane API lets you read and update CRM data from outbound tools, marketing platforms, custom scripts, and internal systems. Work with opportunities, accounts, contacts, notes, activities, pipelines, stages, and custom fields through JSON REST endpoints. Every plan includes API access and webhooks. Create a personal key in [Settings → API keys](https://www.octolane.com/settings/api-keys). For machine-readable discovery, use the [OpenAPI specification](https://www.octolane.com/openapi.json) and [API catalog](https://www.octolane.com/.well-known/api-catalog). See [Octolane for AI agents](/docs/get-started/agents) for MCP and documentation indexes. ## Base URL ``` https://api.octolane.com/v1 ``` ## Authentication Include your API key in every request as a header: ``` x-api-key: your-api-key ``` Use a personal API key created in [Settings → API keys](https://www.octolane.com/settings/api-keys). Requests act as the workspace member who created the key and use that member's current access. A key stops working if it is disabled or its creator leaves the workspace. ## Core objects The primary CRM records are: | Object | What it does | | - | - | | **Opportunity** | A deal or potential deal in your pipeline | | **Account** | A company, identified by domain (e.g., `acme.com`) | | **Contact** | A person, identified by email | | **Note** | A text note attached to accounts and/or contacts | > [!TIP] > > Accounts and contacts are created automatically when you create an opportunity - you don't need to create them separately unless you want to. ## Key behaviors **Create or resolve.** Account creation resolves existing domains and contact creation resolves existing emails. Opportunity duplicate rules are endpoint-specific and can return `409`; inspect the operation schema before retrying a create request. **Auto-creation.** When you create an opportunity with a domain and email, Octolane automatically creates the associated account and contact for you. **Multiple contacts per company.** You can link multiple email contacts under one account. They'll all be associated with the same company domain. **Dates.** Date formats are endpoint-specific. Opportunity `close_date` and `next_action_date` inputs accept Unix timestamps in seconds or milliseconds between 2000-01-01 and 2100-01-01 UTC. Activity `created_at` uses an ISO 8601 date-time and cannot be in the future. Search filters use ISO 8601 date or date-time strings, not Unix timestamps. ## Rate limits Read and search routes allow 300 requests per minute and 100,000 requests per 30-day window. A request that exceeds a route limit returns `429 Too Many Requests`. ## Error handling If something goes wrong, you'll get a clear error response: | Status Code | What it means | | - | - | | `400` | Bad request - check your input fields | | `401` | Invalid or missing API key | | `404` | Resource not found (e.g., wrong `pipeline_id`) | | `409` | A matching opportunity already exists | | `422` | The request is valid JSON but contains rejected values | | `429` | Too many requests - slow down and retry | | `500` | Something went wrong on our end - contact support | Error responses follow this format: ```json theme={"system"} { "success": false, "statusCode": 400, "message": "Validation error", "errors": { "pipeline_id": "Pipeline id must be a valid uuid" } } ``` ## Endpoints > [card] [Create Opportunity](/docs/api-reference/endpoints/crm/create-an-opportunity) > > Create a deal with associated account and contacts in one call. > [card] [Create Account](/docs/api-reference/endpoints/crm/create-or-resolve-an-account) > > Create a company record by domain. > [card] [Create Contact](/docs/api-reference/endpoints/crm/create-or-resolve-a-contact) > > Create a person record by email. > [card] [Create Note](/docs/api-reference/endpoints/crm/create-a-note) > > Attach notes to accounts and contacts. ## Interface coverage The published OpenAPI schema defines the REST operations documented here. Do not infer REST endpoints from MCP tool names: tasks, knowledge, custom objects, and webhook configuration may not have corresponding operations in this schema. Every plan includes webhooks; contact support for event, payload, and delivery details that are not published here. ## Need help? Reach out at [help@octolane.com](mailto:help@octolane.com) for integration questions or operations not covered by the published schema. # Filters Source: https://octolane.com/docs/api-reference/v2/filters Operator reference and aliases for search endpoints. Filters are supported on every `POST .../search` endpoint: * `POST /v2/accounts/search` * `POST /v2/contacts/search` * `POST /v2/opportunities/search` The `/v1` compatibility routes support the same filters. ## Filter shape Each filter is an object with `field`, `operator`, and `value`. ```json theme={"system"} { "filters": [ { "field": "customer_tier", "operator": "eq", "value": "enterprise" }, { "field": "amount", "operator": "gte", "value": 50000 } ] } ``` Multiple filters in the array combine with **AND**. For date and timestamp fields, pass an ISO 8601 date or date-time string. Unix timestamps are not accepted in search filters. ## Supported operators | Operator | Use | | - | - | | `eq` | Equal | | `neq` | Not equal | | `contains` | String contains substring | | `not_contains` | String does not contain substring | | `starts_with` | String starts with | | `ends_with` | String ends with | | `in` | Value is in array | | `not_in` | Value is not in array | | `gt` | Greater than | | `gte` | Greater than or equal | | `lt` | Less than | | `lte` | Less than or equal | | `between` | Between two values (inclusive). Pass `value` as `[min, max]` | | `empty` | Field has no value | | `not_empty` | Field has any value | | `contains_all` | Array field contains all of the given values | | `contains_none` | Array field contains none of the given values | For select, multi-select, and team-member fields, values can match an option's `value` or `label`. The option object returned by the read API is also accepted. `eq` and `in` match any supplied value, while `contains` and `contains_all` require every supplied value. ## Operator aliases These read more naturally and resolve to the same operator under the hood. | Alias | Resolves to | | - | - | | `is` | `eq` | | `is_not` | `neq` | | `contain` | `contains` | | `not_contain` | `not_contains` | | `is_any_of` | `in` | | `greater_than` | `gt` | | `less_than` | `lt` | | `before` | `lt` | | `after` | `gt` | | `include_all` | `contains_all` | | `exclude_all` | `contains_none` | ## Custom field filters Custom fields are filtered by their slug (the same key returned in `custom_fields`). ```json theme={"system"} { "filters": [ { "field": "customer_tier", "operator": "eq", "value": "enterprise" } ] } ``` Look up slugs in the `custom_field_definitions` block of any response. ## Examples ### Range filter ```json theme={"system"} { "field": "amount", "operator": "between", "value": [10000, 50000] } ``` ### Array membership ```json theme={"system"} { "field": "industry", "operator": "in", "value": ["Software", "Fintech"] } ``` ### Date after ```json theme={"system"} { "field": "close_date", "operator": "after", "value": "2026-06-01" } ``` ### Empty check ```json theme={"system"} { "field": "next_action_date", "operator": "empty" } ``` # Read and search Source: https://octolane.com/docs/api-reference/v2/overview Read APIs for Accounts, Contacts, and Opportunities with filters, sorting, field selection, and cursor pagination. The v2 API provides read access to accounts, contacts, and opportunities. Each object has two endpoints: * A **simple list endpoint** (`GET`) with basic text search and cursor pagination. * A **search endpoint** (`POST`) with full filtering, sorting, field selection, and cursor pagination. ## Base URL ``` https://api.octolane.com/v2 ``` ## Authentication Create a personal key in [Settings → API keys](https://www.octolane.com/settings/api-keys). Every request must include it in the `x-api-key` header. ``` x-api-key: your-api-key ``` Requests use the current access of the workspace member who created the personal API key. ## Endpoints | Object | List | Search | | - | - | - | | Accounts | `GET /v2/accounts` | `POST /v2/accounts/search` | | Contacts | `GET /v2/contacts` | `POST /v2/contacts/search` | | Opportunities | `GET /v2/opportunities` | `POST /v2/opportunities/search` | The `/v1` list and search endpoints remain available as compatibility routes and return the same v2 response shape. ## Rate limits The v2 read and search endpoints allow 300 requests per minute and 100,000 requests per 30-day window. ## Shared concepts > [card] [Filters](/docs/api-reference/v2/filters) > > Operator reference and aliases used in every `POST .../search` endpoint. > [card] [Cursor pagination](/docs/api-reference/v2/pagination) > > How to paginate `GET` and `POST` endpoints safely. ## Field selection Every list and search endpoint accepts a `fields` parameter to return only the fields you need. Pass a comma-separated string (for `GET`) or a JSON array (for `POST`). ``` GET /v2/accounts?fields=id,name,domain,custom_fields POST /v2/accounts/search { "fields": ["id", "name", "domain", "custom_fields"] } ``` ## Custom fields Every response includes a `custom_fields` object on each record and a top-level `custom_field_definitions` object describing those fields. ```json theme={"system"} { "custom_fields": { "customer_tier": "enterprise", "renewal_date": "2026-06-01T00:00:00.000Z" }, "custom_field_definitions": { "customer_tier": { "current_name": "Customer Tier", "property_name": "select_530", "attribute_type": "select", "metadata": { "select_options": [] } } } } ``` The keys in `custom_field_definitions` match the keys in `custom_fields`, so clients can resolve slug/value mappings dynamically. ## Need help? Email [help@octolane.com](mailto:help@octolane.com) for API support. # Cursor pagination Source: https://octolane.com/docs/api-reference/v2/pagination How to paginate list and search endpoints. Every list and search response includes: ```json theme={"system"} { "has_more": true, "next_cursor": "opaque_cursor_token", "limit": 10 } ``` Continue paginating until: ```json theme={"system"} { "has_more": false, "next_cursor": null } ``` ## GET endpoints Pass `cursor` as a query parameter. ### First request ```bash theme={"system"} curl "https://api.octolane.com/v2/accounts?limit=10" \ -H "x-api-key: your-api-key" ``` ### Next request ```bash theme={"system"} curl "https://api.octolane.com/v2/accounts?limit=10&cursor=" \ -H "x-api-key: your-api-key" ``` ## POST search endpoints Pass `cursor` in the request body. Keep `filters`, `sort`, `limit`, and (for opportunities) `pipeline_id`/`stage_id` identical between pages. ### First request ```json theme={"system"} { "pipeline_id": "pipeline_uuid", "limit": 10, "sort": { "field": "updated_at", "direction": "desc" } } ``` ### Next request ```json theme={"system"} { "pipeline_id": "pipeline_uuid", "limit": 10, "sort": { "field": "updated_at", "direction": "desc" }, "cursor": "next_cursor_from_previous_response" } ``` > [!WARNING] > > Cursors are valid only when paired with the **same query**: `query`, `filters`, `sort`, `limit`, and (for opportunities) `pipeline_id` / `stage_id`. Changing any of these invalidates the cursor. # Take action with AI Chat Source: https://octolane.com/docs/course/ai-chat Ask Octolane a question, request a change, and review the result before it runs. AI Chat can answer questions about your CRM and prepare actions using the same records you reviewed earlier in the course. **Time:** 3 minutes **Outcome:** One useful answer and one reviewed action. ## Try one question Start with a request that is easy to verify: ```text Ask about your pipeline theme={"system"} Which open opportunities have no next step? ``` Follow the cited records to confirm the answer matches your data. ## Try one action ```text Create a task theme={"system"} Create a task for me to review the Acme opportunity tomorrow. ``` **1. Review the proposed change** When review is required, check the record, owner, due date, and wording before approving it. **2. Approve or edit** Approve the action as written or edit the proposal first. If workspace settings allow direct execution, inspect the completed action instead. **3. Verify the result** Open the linked record and confirm the task appears where you expect it. > [!NOTE] > > Approval behavior depends on workspace settings and action type. Keep consequential actions reviewable until your team trusts the workflow. ## Up next Finish the course by [choosing your next workflow](/docs/course/next-steps). # Connect your workspace Source: https://octolane.com/docs/course/connect Connect Gmail and Calendar and confirm that Octolane can begin assembling your CRM. Connect the conversations and meetings that should become the foundation of your CRM. **Time:** 2–5 minutes **Before you begin:** Sign in with the Google account you use for customer conversations. ## Connect Gmail and Calendar **1. Create or open your workspace** [Sign up](https://www.octolane.com/auth/sign-up) or sign in to your existing workspace. A person completes account setup and Google authorization. Founder has a 7-day trial; see [Plans and pricing](/docs/account/plans-pricing). **2. Connect Gmail** Choose the inbox that contains your customer conversations and complete Google authorization. **3. Connect Google Calendar** Connect the calendar that contains your customer meetings. Octolane uses attendees and meeting history to connect people with the correct records. **4. Let the first sync begin** You can continue using Octolane while records are assembled in the background. ## Check your work Open **Accounts** or **Contacts**. A successful connection begins populating records from external conversations and meetings. > [accordion] I connected the wrong Google account > > Open workspace settings, disconnect the account, and reconnect with the correct address before inviting teammates. > [accordion] No records have appeared yet > > Confirm that the connected inbox contains external conversations. Initial processing time varies with inbox size. If nothing appears after the sync finishes, [contact support](/docs/support/contact). ## Up next Learn [how Octolane organizes your records](/docs/course/records). # Record your first meeting Source: https://octolane.com/docs/course/meeting-recorder Choose recording defaults and verify the transcript, recap, tasks, and opportunity updates. Octo can join supported meetings, create a transcript and recap, extract action items, and connect the result to the relevant records. **Time:** 3 minutes to configure **Before you begin:** Connect the calendar that contains your customer meetings. ## Choose your recording default Open **Settings → Meeting Intelligence** and choose: * **External meetings** for the safest default for most sales teams * **All meetings** if internal pipeline and strategy calls should also be captured * **Manual invite** if you want to decide meeting by meeting **1. Select a default** Choose the option that matches what your team is comfortable recording. **2. Review the next eligible meeting** Confirm the meeting has a supported conference link and appears in Octolane. **3. After the meeting, open its recap** Review the transcript, summary, decisions, action items, and linked records. **4. Correct anything that is wrong** Reassign a speaker, edit a task, or adjust a linked record while the context is still fresh. > [!WARNING] > > Recording expectations vary by company and location. Make sure your team follows its consent and privacy requirements. ## Check your work The meeting should appear on the correct record timeline, with its recap and action items available to the team. ## Up next Use [AI Chat to ask a question and request an action](/docs/course/ai-chat). # Choose your next workflow Source: https://octolane.com/docs/course/next-steps Choose the next Octolane workflow based on how your team sells. You now know the core loop: conversations create context, records organize it, and Octolane performs routine work while surfacing decisions for review. ## Choose a path > [card] [Founder-led sales](/docs/playbooks/founder-led-sales) > > Run a focused sales motion without adding CRM administration. > [card] [Never miss a follow-up](/docs/playbooks/never-miss-followup) > > Find conversations that need attention and prepare the next message. > [card] [Run 50 demos in 30 days](/docs/playbooks/run-50-demos) > > Keep a high-volume meeting motion organized. > [card] [Migrate your existing CRM](/docs/managing-data/importing) > > Bring over the history and structure your team still needs. ## Keep learning * Browse [focused tutorials](/docs/tutorials/overview) * Review your team's [company brain](/docs/ai/company-brain) * Learn [how AI actions and approvals work](/docs/ai/approvals) * Connect Octolane to [Claude, ChatGPT, or Cursor through MCP](/docs/mcp/overview) * [Contact the Octolane team](/docs/support/contact) for migration or setup help > [!TIP] > > The best next step is a real workflow with a clear result. Pick one playbook, run it with live data, and adjust the workspace only when the workflow exposes a need. # Octolane 101 Source: https://octolane.com/docs/course/overview A six-part guided introduction to setting up and using Octolane. Octolane 101 takes you from an empty workspace to a working sales motion. Complete the lessons in order or jump to the part you need. **Time:** About 20 minutes **You will finish with:** A connected workspace, a clear data model, a pipeline, meeting capture, and your first verified AI action. ## Course goals By the end of this course, you will understand: * How Octolane creates and updates CRM records * Which setup choices matter before inviting your team * How meetings, pipelines, AI Chat, and approvals work together * Where to go next for migrations, playbooks, and advanced workflows ## Lessons > [card] [1. Connect your workspace](/docs/course/connect) > > Connect Gmail and Calendar and confirm the first sync. > [card] [2. Understand your records](/docs/course/records) > > Learn accounts, contacts, opportunities, and activities. > [card] [3. Build your pipeline](/docs/course/pipeline) > > Create a simple pipeline your team can use immediately. > [card] [4. Record your first meeting](/docs/course/meeting-recorder) > > Choose recording defaults and verify the recap workflow. > [card] [5. Take action with AI Chat](/docs/course/ai-chat) > > Ask a question, request a change, and approve it. > [card] [6. Choose your next workflow](/docs/course/next-steps) > > Pick the playbook that matches how your team sells. > [!NOTE] > > You can safely explore during this course. Approval behavior depends on the action and workspace settings. Review requests that need approval and verify completed actions. External API and MCP writes may apply directly; see [Approvals](/docs/ai/approvals). ## Up next Continue to [Connect your workspace](/docs/course/connect). # Build your pipeline Source: https://octolane.com/docs/course/pipeline Create a simple sales pipeline with stages your team can use immediately. Create a pipeline that reflects decisions in your sales process, not every small activity your team performs. **Time:** 5 minutes **Before you begin:** Write down the major states a deal moves through from first conversation to closed. ## Create the pipeline **1. Open pipeline settings** Go to **Settings → Pipelines** and create a new pipeline. **2. Name the sales motion** Use a name your team already understands, such as **New business**, **Partnerships**, or **Expansion**. **3. Add five to seven stages** Start with a small set such as **Discovery**, **Qualified**, **Evaluation**, **Proposal**, **Closed won**, and **Closed lost**. **4. Set probabilities and criteria** Give each open stage a probability and describe what must be true for a deal to enter or leave it. **5. Create the pipeline and add one opportunity** Move a real or test opportunity through the stages to confirm the flow is clear. > [!TIP] > > If two stages do not change what your team does next, combine them. A shorter pipeline is easier to maintain and forecast. ## Check your work Every stage should answer two questions: **Why is this deal here?** and **What must happen next?** ## Up next Set up [the meeting recorder](/docs/course/meeting-recorder) so calls update the same opportunity context. # Understand your records Source: https://octolane.com/docs/course/records Learn how accounts, contacts, opportunities, and activities fit together in Octolane. Octolane uses a small set of connected records so conversation history, tasks, and deal context stay in one place. **Time:** 3 minutes **Outcome:** You can open any record and understand what you are looking at. ## The four records to know | Record | Represents | Usually created from | | - | - | - | | **Account** | A company or organization | An external email domain, meeting, import, or manual creation | | **Contact** | A person | An email participant, meeting attendee, import, or manual creation | | **Opportunity** | A potential deal | Conversation signals, an import, AI Chat, or manual creation | | **Task** | Work with an owner and due date | A person, a meeting action item, or AI Chat | Emails, meetings, notes, and AI actions appear as **activities** on the relevant record timeline. ## Follow one relationship **1. Open an account** Choose a company you recognize and review its fields and recent activity. **2. Open a related contact** Confirm that the person, company, email history, and meetings are connected as expected. **3. Open or create an opportunity** Review its account, people, value, stage, close date, and activity timeline. ## Check your work You should be able to move from an opportunity to its account and contacts without searching for the same conversation twice. > [card] [Explore the complete data model](/docs/introductions/data-model) > > Learn about activities, custom objects, fields, and relationships. ## Up next Use those records to [build your first pipeline](/docs/course/pipeline). # How deals are auto-detected from email Source: https://octolane.com/docs/email-calendar/deal-auto-detection The logic behind deal detection. Octolane reads your outbound and inbound email and flags conversations that look like deals based on: * Buying-intent language ("pricing", "demo", "trial", "contract") * New external contacts at a target-profile company * Related calendar invites * Reply cadence consistent with sales motion Octolane creates or proposes detected deals according to workspace settings. Review items that require a decision in the [approval queue](/docs/ai/approvals). See [Auto-detecting deals from email](/docs/ai/auto-detecting-deals). # Setting up Gmail Source: https://octolane.com/docs/email-calendar/gmail-setup Connect, permissions, and what Octolane reads. ## Connect Settings → Integrations → Gmail → Connect. Sign in with your Google Workspace account. ## Permissions Review the Google authorization screen for the permissions requested by the features you enable. Octolane reads connected conversation context and can send through Gmail for authorized outreach workflows. Follow-up drafts can be reviewed individually; configured sequences and automations can send on a schedule. See [Approvals](/docs/ai/approvals). ## Conversation context Octolane uses connected email history to build and update accounts, contacts, deals, and follow-ups. Connect the account you intend to use for customer work. See [Security](/docs/security) for access and data-use information; contact support for questions about mailbox scope or retention. # Setting up Google Calendar Source: https://octolane.com/docs/email-calendar/google-calendar-setup Connect, permissions, and meeting capture. ## Connect Settings → Integrations → Google Calendar → Connect. ## Permissions Review the Google authorization screen for the requested calendar permissions. Octolane uses event attendees and meeting history to link records; configure recording separately in meeting settings. ## Meeting capture When enabled, the Octolane bot joins external meetings, records, transcribes, and writes the summary to the linked opportunity. See [Meeting recorder](/docs/introductions/meeting-recorder). # Email templates and snippets Source: https://octolane.com/docs/email-calendar/templates Save reusable email blocks. Save full templates or short snippets you reuse. Insert with `/` in the email composer. Variables auto-fill from the linked record: `{{contact.first_name}}`, `{{account.name}}`, `{{opportunity.amount}}`. # Threading and conversation linking Source: https://octolane.com/docs/email-calendar/threading How emails get attached to the right opportunity. Octolane links emails to opportunities using: 1. Thread participants and domain 2. References to the opportunity by name, project, or product line 3. Calendar invites cross-referenced with the thread 4. Manual override when needed (move once. Octolane remembers) When a thread spans multiple opportunities, you can split it. # Octolane for AI agents Source: https://octolane.com/docs/get-started/agents Discover the docs, connect through MCP or REST, and work with CRM records and company knowledge using the connected user's permissions. Octolane is a self-driving AI CRM built for agents and humans. Its own agents maintain records, find deals, and prepare follow-ups. External agents can read and update CRM data and query the company brain through MCP. Every plan includes MCP, the REST API, and webhooks; feature and usage limits still depend on the [plan](/docs/account/plans-pricing). ## Discover the right source | Resource | Use it for | | - | - | | [Product summary](https://www.octolane.com/llms.txt) | Product positioning, capabilities, pricing links, and agent entry points | | [Docs index](https://www.octolane.com/docs/llms.txt) | Find individual documentation pages | | [Full docs text](https://www.octolane.com/docs/llms-full.txt) | Read the documentation as one text resource | | [Pricing Markdown](https://www.octolane.com/pricing.md) | Current prices, seats, limits, and feature entitlements | | [FAQ Markdown](https://www.octolane.com/faq.md) | Current product and buyer questions | | [OpenAPI schema](https://www.octolane.com/openapi.json) | REST operations, inputs, responses, and authentication | | [API catalog](https://www.octolane.com/.well-known/api-catalog) | Discover API descriptions and service documentation | | [MCP discovery](https://www.octolane.com/.well-known/mcp.json) | MCP endpoint, transport, and authentication metadata | The website's [content index](https://www.octolane.com/llms-full.txt) lists published articles and case studies. It is separate from the full documentation text under `/docs/llms-full.txt`. Individual docs pages also have Markdown versions; for example, [MCP authentication](https://www.octolane.com/docs/mcp/authentication.md). ## Connect to a workspace A person [signs up](https://www.octolane.com/auth/sign-up), starts the 7-day Founder trial or arranges a demo-led plan, and connects Gmail and Google Calendar. An agent uses the workspace after the person authorizes access. * **MCP:** connect to `https://mcp.octolane.com/mcp` over Streamable HTTP. Use OAuth, or an API key in `Authorization: Bearer YOUR_OCTOLANE_API_KEY` if your client supports custom headers. Follow the [MCP quickstart](/docs/mcp/quickstart). * **REST:** use `https://api.octolane.com` with the paths in the OpenAPI schema and an API key in `x-api-key`. Follow the [API reference](/docs/api-reference/introduction). * **API keys:** create a personal key in [Settings → API keys](https://www.octolane.com/settings/api-keys). Requests use its creator's current workspace access. ## Work with the available tools 1. Discover the current MCP tools and input schemas with `tools/list`. Use the [tools reference](/docs/mcp/tools-reference) to understand common workflows; the connected server determines which tools are available. 2. Check the connected identity and workspace before working with customer records. Use `get_current_user` when available. 3. Search for existing records, then reuse the IDs returned by the service. Resolve ambiguous names before changing records. 4. Read the current record before an update. Keep writes within the person's request and workspace permissions. API and MCP writes can change records directly; do not assume they all enter the in-app approval queue. 5. Follow response pagination and use field selection where supported. Verify the resulting record after a write and report failures or partial results accurately. For REST, use each operation's schema rather than translating MCP tool arguments directly: identifiers, dates, and record-resolution behavior can differ. See [filters](/docs/api-reference/v2/filters) and [pagination](/docs/api-reference/v2/pagination). ## Query the company brain The company brain is called **Knowledge** in Octolane. It is available on every plan and can be queried by people and agents through MCP. Discover the schemas for `memory_list` and `memory_get`, then list and read the applicable shared and personal knowledge. Pending suggestions are excluded by default; distinguish them from approved knowledge if explicitly requested. Example request: “What objections come up in our sales conversations, and which responses have worked? Cite the available knowledge and distinguish it from your own suggestions.” See [Company brain](/docs/ai/company-brain) for review and version-history behavior. ## Limits and unavailable capabilities Unlimited AI does not mean unlimited enrichment or automation runs. Check [usage limits](/docs/account/plans-pricing#usage-limits). Honor rate-limit responses and retry guidance. If a capability or schema is unavailable, report that limitation rather than inventing an API route, tool name, or successful result. Webhooks are included on all plans. For event types, payloads, delivery guarantees, and signing configuration not covered by the published schema, contact [help@octolane.com](mailto:help@octolane.com). # Common questions Source: https://octolane.com/docs/get-started/common-questions Answers about Octolane's agentic CRM, company brain, setup, migration, pricing, and access for AI agents. > [accordion] What is Octolane? > > A self-driving AI CRM built for agents and humans. It captures connected email and meetings, updates records, finds deals, prepares follow-ups, and runs configured sales workflows. Your team reviews decisions that need its judgment. > [accordion] Can AI agents use it? > > Yes. Every plan includes the MCP server, REST API, and webhooks. External agents can read and update CRM data and query company knowledge with the connected person's permissions. Start with [Octolane for AI agents](/docs/get-started/agents). > [accordion] Does Octolane send emails on my behalf? > > Octolane drafts follow-ups for review and can run authorized email and LinkedIn sequences on a schedule. Sending depends on your workspace settings and the workflow you enable. See [Approvals](/docs/ai/approvals). > [accordion] What is the company brain? > > Knowledge in the app stores what your team learns from conversations, decisions, and outcomes. New learnings wait for review, changes are version-controlled, and people and AI agents can query the same knowledge. See [Company brain](/docs/ai/company-brain). > [accordion] How long does setup take? > > Connect Gmail and Google Calendar to start building records within minutes. Initial processing depends on your history and configuration; the website describes most teams as running within an hour. Follow the [Quickstart](/docs/get-started/quickstart) and verify the first records. > [accordion] Is my data used to train other teams' agents? > > No. Your information is not pooled into a shared model or used to improve other customers' agents. Octolane learns from your team's decisions for your own team. See [Security](/docs/security). > [accordion] Can I use it solo? > > Yes. Founder is built for individual founders and supports up to three users. Move to Pro when you need a fourth user or additional capabilities. > [accordion] Can I import from another CRM? > > Yes. Upload Attio, HubSpot, or Salesforce exports and ask Octolane to migrate. Exodus 1 maps fields, links records, merges duplicates, and enriches data. Pro and above include migration run by our team. CSV imports are also available. See [Importing data](/docs/managing-data/importing). > [accordion] What does it cost? > > Founder is \$99/user/month, billed monthly. Pro is \$149/user/month with 10 seats (\$1,490/month), Team is \$199/user/month with 10 seats (\$1,990/month), and Enterprise starts at \$249/user/month with 20 seats (from \$4,980/month). Pro, Team, and Enterprise are billed annually upfront. See [Plans and pricing](/docs/account/plans-pricing). > [accordion] Is there a free plan or trial? > > There is no ongoing free plan. Founder includes a 7-day free trial; Pro, Team, and Enterprise offer custom trials when you book a demo. YC companies get Founder free for one year. > [accordion] Does unlimited AI mean unlimited enrichment? > > No. AI has no separate AI credits. Enrichment uses monthly credits: 1,000 on Founder, 5,000 on Pro, 20,000 on Team, and custom on Enterprise. Automation runs also have separate plan limits. See [Enrichment](/docs/ai/enrichment). > [accordion] Where do I create an API key? > > Open [Settings → API keys](https://www.octolane.com/settings/api-keys). Personal keys use their creator's current workspace access. MCP also supports OAuth. See [Authentication](/docs/mcp/authentication). > [accordion] How do I get help? > > Email [help@octolane.com](mailto:help@octolane.com) or see [Support](/docs/support/contact). For current commercial terms, consult the [pricing page](https://www.octolane.com/pricing) and its [Markdown version](https://www.octolane.com/pricing.md). # Glossary Source: https://octolane.com/docs/get-started/glossary Octolane terms defined. Quick reference for the terminology used across Octolane. * **Company brain (Knowledge)**. Version-controlled knowledge learned from your team's conversations, decisions, and outcomes, queryable by people and agents. * **Exodus 1**. Octolane's migration model for mapping, linking, deduplicating, and enriching uploaded CRM exports. * **MCP**. Model Context Protocol, the interface external AI clients use to discover tools and work with Octolane under the connected user's permissions. * **Account**. A company record. Auto-created from emails, meetings, and form submissions. * **Contact**. A person record, linked to an Account. * **Opportunity**. A deal record with a stage, amount, and close date. Auto-detected from email. * **Task**. A first-class to-do with an owner, due date, and completion state. * **Pipeline**. An ordered set of stages a deal moves through. * **Stage**. A step in a pipeline with entry/exit criteria and a probability. * **AI field**. A custom field that fills itself in by reading your conversations. * **Signal**. A real-time identification of a company visiting your website. * **View**. A saved filter + columns + sort across any object. * **Activity**. Any email, meeting, note, or AI action on a record's timeline. * **Approval queue**. Where AI-drafted actions wait for your review. * **Custom object**. A new record type beyond Accounts, Contacts, and Opportunities. Pro includes up to 10; Team and Enterprise include unlimited custom objects. See [Plans and pricing](/docs/account/plans-pricing). # Quickstart Source: https://octolane.com/docs/get-started/quickstart Connect Octolane and complete your first useful CRM action in about 10 minutes. After you complete this guide, you will have a connected workspace, familiar customer records, and one verified action created with AI Chat. ## Before you begin You need an Octolane account and a Google account that contains customer email or calendar activity. Use the account where real customer conversations already happen. A person creates the account and authorizes Gmail and Calendar. Founder includes a 7-day trial; Pro, Team, and Enterprise start with a demo. See [Plans and pricing](/docs/account/plans-pricing). If you are connecting an external agent to an existing workspace, use [Octolane for AI agents](/docs/get-started/agents). Octolane begins organizing your customer data after you connect Gmail and Calendar. The initial sync continues in the background while you complete the rest of this guide. ## Connect Gmail and Calendar [Create an Octolane account](https://www.octolane.com/auth/sign-up) or open the workspace you want to configure. In Octolane, open **Settings → Integrations → Gmail & Calendar** and choose the Google account you use for customer conversations. Complete the authorization flow for both Gmail and Calendar. Octolane uses those conversations and meetings to connect people, companies, and opportunities. Review [Security](/docs/security) for details about permissions, data handling, and compliance. ## View the CRM Octolane builds Open **Accounts** or **Contacts** and choose a person or company you recognize. Confirm that its email and meeting activity belongs to the correct record. Then open **Opportunities**. If Octolane has detected a deal, review its account, contacts, stage, and recent activity. ## Complete your first action Open **AI Chat** and ask a question that is easy to verify: ```text Find an opportunity theme={"system"} Which open opportunity has the most recent activity? ``` Then request a small action: ```text Create a task theme={"system"} Create a task for me to review that opportunity tomorrow. ``` If the action requires review, inspect and approve the proposed task. If your settings allow it to run directly, inspect the completed task. Confirm that it appears on the intended opportunity. ## Check your work You are ready to continue when all of the following are true: * At least one familiar account or contact appears * Its conversation history is attached to the correct record * AI Chat can answer a question using that data * Your test task appears on the expected opportunity > [accordion] No records have appeared > > Confirm that you connected the inbox containing external customer conversations. Initial processing time varies with inbox size. If the sync has finished and the workspace is still empty, [contact support](/docs/support/contact). > [accordion] A conversation is attached to the wrong record > > Correct the relationship from the record and review [merging duplicates](/docs/managing-data/merging-duplicates) if two records represent the same person or company. > [accordion] AI Chat cannot find the record > > Open the record directly to confirm it exists and use its full name in your request. See [AI Chat and slash commands](/docs/ai/chat-slash-commands) for more examples. ## Next steps > [card] [Learn Octolane](/docs/course/overview) > > Understand the product through six short lessons. > [card] [Set up the meeting recorder](/docs/course/meeting-recorder) > > Choose what Octo records and verify the recap workflow. > [card] [Build your pipeline](/docs/course/pipeline) > > Create stages, probabilities, and clear movement criteria. > [card] [Browse tutorials](/docs/tutorials/overview) > > Follow a focused workflow from start to finish. # What's new Source: https://octolane.com/docs/get-started/whats-new Latest releases from the Octolane changelog. For the full release history, see the [Changelog](/docs/changelog). > [card] [Changelog](/docs/changelog) > > Every shipped feature, fix, and improvement. # Octolane documentation Source: https://octolane.com/docs/index The self-driving AI CRM built for agents and humans. Learn about records, company knowledge, workflows, MCP, and the REST API. # Octolane is a self-driving AI CRM Built for agents and humans. It keeps records current, works your pipeline, and learns from your team’s decisions in a shared company brain. ## [Quickstart](/docs/get-started/quickstart) Connect your workspace and see your first customer records in about 10 minutes. ## [Octolane 101](/docs/course/overview) Learn how records, pipelines, meetings, AI Chat, and approvals work. ## [Switch to Octolane](/docs/managing-data/importing) Move from HubSpot, Salesforce, Pipedrive, Attio, or a spreadsheet. ## [For AI agents](/docs/get-started/agents) Find machine-readable docs and connect through MCP or REST. Included on every plan. # Accounts Source: https://octolane.com/docs/introductions/accounts Company records. How they're created, enriched, and merged. An Account is a company in Octolane. ## How accounts are created * Auto-created from any outbound or inbound email with a new domain. * Auto-created from a calendar invite with external attendees. * Created manually, via CSV import, the API, or Zapier. ## Enrichment Account enrichment depends on your plan, remaining credits, and available data. Built-in enrichment includes LinkedIn URL, funding, employee count, and location; Pro and above add advanced data such as hiring and news. See [Enrichment](/docs/ai/enrichment). ## Merging Duplicates surface automatically when we detect the same legal entity across domains or names. See [Merging duplicates](/docs/managing-data/merging-duplicates). # AI Chat Source: https://octolane.com/docs/introductions/ai-chat Talk to your CRM. Ask questions, give commands, generate reports. AI Chat is the front door to your CRM. * **Ask**. "How many deals closed last quarter over \$20k?" * **Command**. "Create a task for me to follow up with Acme tomorrow." * **Report**. "Show pipeline by stage, grouped by rep." See [AI Chat and slash commands](/docs/ai/chat-slash-commands). # AI fields Source: https://octolane.com/docs/introductions/ai-fields Fields that fill themselves in. Describe what to track, Octolane extracts it from conversations. The killer feature. Define an AI field in plain English: "Decision maker title", "Budget mentioned", "Competitor named", "Next step", "Blocker". Octolane reads every email, meeting, and note on the record and keeps the value current. ## Examples | Field | Prompt | | - | - | | Decision maker | "Who has final sign-off on this deal?" | | Budget | "What dollar amount has been mentioned?" | | Timeline | "When do they want to start?" | | Blocker | "What is blocking this deal right now?" | See [Auto-filling fields](/docs/ai/auto-filling-fields). # Contacts Source: https://octolane.com/docs/introductions/contacts People records. Auto-creation from email, enrichment, dedupe. A Contact is a person, linked to one or more Accounts. ## Auto-creation Every external participant in your emails and meetings becomes a Contact. No manual entry. ## Enrichment Built-in enrichment includes LinkedIn URL, verified email, and location when available. Advanced enrichment on Pro and above adds signals such as job changes. Enrichment uses monthly credits; see [Enrichment](/docs/ai/enrichment). ## Dedupe Same email always merges. Same name + same company merges with a confidence check. Conflicts go to your [approval queue](/docs/ai/approvals). # Custom fields Source: https://octolane.com/docs/introductions/custom-fields Add fields to any standard object. Add any field to Accounts, Contacts, Opportunities, or Tasks: text, number, date, select, multi-select, URL, currency, formula, lookup. For fields you want filled automatically from conversations, use an [AI field](/docs/introductions/ai-fields) instead. # Custom objects Source: https://octolane.com/docs/introductions/custom-objects Model anything beyond Accounts, Contacts, and Opportunities. > [!NOTE] > > **Pro** includes up to 10 custom objects. **Team** and **Enterprise** include unlimited custom objects. See [Plans and pricing](/docs/account/plans-pricing). Custom objects let you model anything that doesn't fit into the standard Account / Contact / Opportunity / Task shape. They get the full Octolane treatment. AI fields, views, automation, API, and human-in-the-loop approval. ## What you can model Custom objects are useful when your business has first-class entities that aren't deals. | Object | Common use | | - | - | | **Partners** | Resellers, integrators, referral sources you track outside of customers | | **Investors** | Funds and angels you're raising from, with stage and check size | | **Projects** | Implementation projects, with milestones and timelines | | **Properties** | Real estate or physical assets, with location and status | | **Loans** | Lending deals with principal, term, and payment schedule | | **Locations** | Physical sites for retail, healthcare, or logistics | | **Inventory** | SKUs or units tied to opportunities | | **Vendors** | Suppliers and contractors | ## How custom objects work Every custom object gets: * **Standard fields**. Name, owner, created/updated, tags * **Custom fields**. Text, number, date, select, multi-select, URL, currency, formula, lookup * **AI fields**. Define in plain English, Octolane fills them in from related conversations * **Relationships**. Lookup fields to Accounts, Contacts, Opportunities, or other custom objects * **Views**. Filter, sort, group, save, share * **Activity timeline**. Emails, meetings, notes, and AI actions linked through related Accounts and Contacts * **API access**. Full REST API and MCP tool support * **Approval queue**. AI actions follow workspace approval settings, as they do for standard objects ## Creating a custom object 1. Open **Settings → Data Model → Custom Objects**. 2. Name the object (singular and plural). 3. Pick an icon and color. 4. Add custom fields and AI fields. 5. Define relationships to standard or other custom objects. 6. Save. The object appears in your sidebar. ## Relationships Custom objects connect to the rest of your data through **lookup fields**. * A **Partner** has a lookup to an Account (the partner's company). * A **Project** has a lookup to an Opportunity (the deal it implements) and an Account. * An **Investor** has a lookup to multiple Contacts (people at the fund). Relationships are bidirectional. Open an Account to see all Projects, Partners, or Loans linked to it. ## AI fields on custom objects AI fields work the same as on standard objects. For a **Project** custom object, you might define: * *"Current milestone the team is working on"* * *"Blocker mentioned in the last status update"* * *"Expected go-live date based on recent emails"* Octolane reads every email, meeting, and note related to the Project and keeps the values current. ## API and MCP Use the published [API reference](/docs/api-reference/introduction) and the connected [MCP tool schemas](/docs/mcp/overview) to determine supported operations. Custom-object plan access does not imply that every object operation is exposed by every interface. Contact [help@octolane.com](mailto:help@octolane.com) for custom-object integration requirements. ## Next > [card] [Custom fields](/docs/introductions/custom-fields) > > Add fields to any standard object. > [card] [AI fields](/docs/introductions/ai-fields) > > Fields that fill themselves in from conversations. # The Octolane data model Source: https://octolane.com/docs/introductions/data-model How Accounts, Contacts, Opportunities, Tasks, Meetings, and Activities relate. Octolane is built around a small set of core objects. Everything you do. Every email, meeting, AI field, custom field. Extends them. ## 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 | | - | - | | **Email** | 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 | Every record has a unified timeline showing every activity in order. ## Custom fields Add any field to any standard object: text, number, date, select, multi-select, URL, currency, formula, lookup. See [Custom fields](/docs/introductions/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](/docs/introductions/ai-fields). ## Custom objects > [!NOTE] > > **Pro** includes up to 10 custom objects. **Team** and **Enterprise** include unlimited custom objects. See [Plans and pricing](/docs/account/plans-pricing). Model anything beyond Accounts, Contacts, and Opportunities. Partners, Investors, Projects, Properties, Loans, Locations. Custom objects support fields, views, relationships, and automation. Check the published API and connected MCP schemas for the operations exposed to integrations. See [Custom objects](/docs/introductions/custom-objects). ## 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. # Email and calendar sync Source: https://octolane.com/docs/introductions/email-calendar-sync How Gmail and Calendar power the entire system. Gmail and Calendar are the fuel for Octolane. Connect them once and every account, contact, opportunity, and AI field stays current automatically. See [Setting up Gmail](/docs/email-calendar/gmail-setup) and [Setting up Google Calendar](/docs/email-calendar/google-calendar-setup). # Meeting recorder Source: https://octolane.com/docs/introductions/meeting-recorder Auto-joins your Zoom, Meet, and Teams calls. Records, transcribes, summarizes, and updates the linked opportunity. The Octolane notetaker joins your calls automatically, records them, generates a structured recap, and pushes everything. Transcript, action items, AI field updates. Onto the linked account, contact, and opportunity. ## How it works 1. The bot accepts every calendar invite that matches your auto-record rules. 2. It joins the call at start time and records the full session. 3. After the call, you get a transcript, a recap (TL;DR, key discussion points, decisions, action items), and speaker analytics. Usually within a few minutes. 4. Action items become tasks. AI fields on the opportunity update from what was said. Everything attaches to the timeline. ## Auto-record rules Pick one mode in [Settings → Meeting Intelligence](https://www.octolane.com/settings/meeting-intelligence): * **All meetings**. Record every meeting with a conference link. * **External meetings**. Record only meetings with at least one outside attendee. (Most common for founder-led sales.) * **Meetings I manually invite**. The bot only joins when you explicitly add the notetaker to the invite. You can override per-meeting at any time. ## The meetings view Every recorded call shows up in the Meetings view with: * Meeting title and duration * Linked accounts * Participants (color-coded badges) * Date Filter, search, and sort like any other Octolane view. Open any meeting to see the full recap. ## What you get for every call > [accordion] Video playback with speaker timeline > > Full recording with a visual speaker timeline. See who talked when, and what percentage of the call each person held. Click any segment to jump to that moment. > [accordion] Recap > > A structured summary, regenerated on demand: > > * **TL;DR**. The call in 3–4 sentences > * **Key discussion points**. Bulleted, organized by topic > * **Decisions made**. Concrete outcomes > * **Action items**. Pushed into Tasks, assigned to the right people > * **Next steps**. What happens between now and the next touchpoint > > Hit **Generate** to re-run with updated context. Hit **Copy** to paste the recap anywhere. > [accordion] Full transcript > > Speaker-labeled, timestamped, searchable. Click any line to jump the video to that moment. > [accordion] Contacts and Accounts tabs > > Every participant and company on the call, auto-linked. New people from the call become Contacts; new companies become Accounts. > [accordion] AI field updates on the opportunity > > Any AI field on the linked opportunity refreshes from what was said. Decision maker, budget, timeline, blockers, next step. Updates show up in the [approval queue](/docs/ai/approvals) (or apply automatically if auto-approve is on). > [accordion] Ask anything about the call > > Hit **Ask** to query the transcript in plain English: *"What objection did they raise about pricing?"* or *"What did Tiffany commit to send by Friday?"* > [accordion] Share > > Share recap or full recording with teammates, or generate a public link for an external prospect. ## Prompts to try with Ask Click any meeting, hit **Ask**, and try these. Copy and paste: ```text Pull objections theme={"system"} What objections did they raise, and how did we respond? ``` ```text Surface commitments theme={"system"} List everything I committed to send or do, with deadlines. ``` ```text Surface their commitments theme={"system"} List everything they committed to, and by when. ``` ```text Draft the follow-up theme={"system"} Draft a follow-up email summarizing this call and the next steps. ``` ```text Score the call theme={"system"} On a scale of 1–10, how likely is this deal to close? Cite specific moments from the call. ``` ```text Compare to last call theme={"system"} Compare this call to the previous one with the same account. What's changed? ``` ```text Extract decision criteria theme={"system"} What criteria did they say will drive their decision? ``` ```text Find competitors mentioned theme={"system"} Did they mention any competitors? What did they say about each? ``` ## Supported platforms Google Meet, Zoom, and Microsoft Teams. ## Setup See [Setting up Google Calendar](/docs/email-calendar/google-calendar-setup) for the calendar permissions the bot needs. Configure recording rules in [Settings → Meeting Intelligence](https://www.octolane.com/settings/meeting-intelligence). # Notes and activities Source: https://octolane.com/docs/introductions/notes-activities Every email, meeting, note, and AI action on a single timeline. Every record in Octolane has a unified timeline. Open any Account, Contact, or Opportunity and you see the available activity history in order. Field history and audit-log retention depend on your [plan](/docs/account/plans-pricing). ## What's on the timeline | Type | Source | Notes | | - | - | - | | **Email** | Gmail (inbound + outbound) | Auto-threaded to the right record | | **Meeting** | Google Calendar | With optional recording, transcript, and recap | | **Meeting recap** | Octolane notetaker | TL;DR, decisions, action items, AI field updates | | **Note** | You or your team | Free-form text, Markdown supported | | **Comment** | You or your team | Threaded discussion on the record | | **AI action** | Octolane | Field updates, draft sends, stage changes, enrichment. Every move logged with citation | | **Task** | Manual, MCP, or AI-generated | Shows when created, assigned, and completed | | **Stage change** | Manual or auto-advanced | Shows old stage, new stage, and trigger | | **Field update** | Any source | Old value → new value with timestamp and author | ## Filtering and searching * **Filter by type**. Show only emails, only meetings, only AI actions, etc. * **Filter by person**. Show only what one teammate (or one external contact) did. * **Date range**. Last 7 days, last 30 days, custom. * **Search**. Full-text search across every email body, meeting transcript, and note. ## Notes Drop notes on any record. Notes support: * **Markdown**. Headings, lists, code blocks, links * **@mentions**. Notify a teammate or link to another record * **Pinning**. Keep important context at the top of the timeline * **Editing and version history**. Every edit logged ## @mentions Type `@` anywhere in a note or comment to: * **Tag a teammate**. They get notified in-app, by email, and optionally in Slack * **Link a record**. `@Acme` inserts a clickable link to that Account, Contact, or Opportunity ## Comments Comments live on a separate thread from notes. Use them for back-and-forth discussion you don't want polluting the activity timeline: * Threaded replies * Resolve when done * Notification routing to the assigned owner ## AI actions on the timeline Every consequential AI action is logged with: * **What changed**. Field name, old value, new value * **Why it changed**. The source (specific email, meeting moment, or web enrichment hit) * **Confidence**. Octolane's confidence in the update * **Who approved it**. You, a teammate, or auto-approve threshold Click any AI action to see the citation. If it's wrong, revert in one click. Octolane learns from the correction. ## Next > [card] [Notes and mentions](/docs/productivity/notes-mentions) > > Day-to-day note-taking and @mentioning. > [card] [Comments](/docs/productivity/comments) > > Discuss a deal inside the record. # Opportunities Source: https://octolane.com/docs/introductions/opportunities Deal records. Fields, lifecycle, and how AI updates them. An Opportunity is a deal: an account, a value, a stage, a close date, and the people working it. ## Lifecycle 1. **Detected**. Surfaced from a real conversation (see [Auto-detecting deals](/docs/ai/auto-detecting-deals)). 2. **Qualified**. Moved into your pipeline. 3. **Working**. Stage advances as conversations progress. 4. **Won / Lost**. Closed with reason and notes. ## AI updates Stage, next step, blockers, decision criteria, and amount. Kept current from every email and call. See [Auto-filling fields](/docs/ai/auto-filling-fields). # Pipelines and stages Source: https://octolane.com/docs/introductions/pipelines-stages Build a pipeline, define stages, set entry and exit criteria. Run one pipeline or many. Each stage has: * A name and color * A probability * Entry criteria (auto-advance rules) * Exit criteria (what must be true to leave) See [Building your pipeline](/docs/pipelines/building) and [Stage automation](/docs/pipelines/stage-automation). # Signal Source: https://octolane.com/docs/introductions/signal Identify which companies visit your website, what they read, and how to reach out. In real time. Install the Signal script to identify companies visiting your website and see the pages they read. Visitor tracking is included on every plan. Intent signals and advanced enrichment start on Pro; enrichment depends on remaining credits. See [Plans and pricing](/docs/account/plans-pricing). Signal provides company-level context rather than identifying the individual visitor. ## How it works 1. Install the Signal script on your marketing site (one ` ``` Grab your workspace-specific key from the [Leads view](https://www.octolane.com/leads). Verify the script loads and check for identified company traffic; timing depends on site activity. ## What it does for your CRM * **Auto-creates accounts** for high-intent visitors that match your ICP * **Updates existing accounts** with web activity on their timeline * **Drafts outreach**. AI-drafted personalized openers referencing the pages they read (queued in your [approval queue](/docs/ai/approvals)) * **Pipeline alerts**. Review company activity associated with an open opportunity ## Interpreting results A company match does not identify the person who visited, and not every visit will resolve to a company. For data handling and tracking configuration details, see [Security](/docs/security) or contact [help@octolane.com](mailto:help@octolane.com). ## Next > [card] [Inbound from website playbook](/docs/playbooks/inbound-website) > > Signal → AI scoring → outreach → deal. > [card] [Open Leads](https://www.octolane.com/leads) > > See identified visitors and grab your install snippet. # Tasks Source: https://octolane.com/docs/introductions/tasks First-class to-dos. Assign, due dates, completion, and AI-generated tasks from meetings. Tasks are not afterthoughts in Octolane. They have owners, due dates, completion states, and live on any record. ## Sources * Manual creation * AI-extracted from meetings (e.g. "send pricing PDF") * AI-generated follow-ups * MCP or supported integrations See [Tasks workflows](/docs/productivity/tasks). # Views and saved filters Source: https://octolane.com/docs/introductions/views-filters Slice your data, save the view, share with your team. A view is a saved combination of filter + columns + sort + grouping on any object. * Personal views are private. * Workspace views are shared with the team. * Pin views to your sidebar. Common views: "My open deals", "Deals closing this quarter", "No activity in 14 days", "New accounts this week". # Bulk edits Source: https://octolane.com/docs/managing-data/bulk-edits Update many records at once. Select rows in any view, then update a field, assign owner, change stage, add tags, or delete. Review the selection and intended changes before applying them. Recovery depends on the operation; do not assume a bulk API write has an undo window. # Deleting and archiving Source: https://octolane.com/docs/managing-data/deleting-archiving Review record changes and distinguish record recovery from subscription cancellation. Archiving hides records from active views while retaining their history. Deleting records changes the stored CRM data and may affect related workflows. Before a bulk deletion, verify the selected records and keep any export you need. Follow the application's confirmation and recovery options; contact [help@octolane.com](mailto:help@octolane.com) if you need to restore data. Do not assume that every UI or API deletion has the same undo window. For API deletions, use the [operation reference](/docs/api-reference/endpoints/crm/bulk-delete-accounts-contacts-or-opportunities). A name-based opportunity deletion can match multiple records, so use IDs when you need to target a specific record. The 30-day retention period described in [Billing](/docs/account/billing) concerns subscription cancellation. It is not a promise of 30-day recovery for every individual record deletion. # Exports Source: https://octolane.com/docs/managing-data/exports Pull your data out as CSV. Export your data at any time as CSV or JSON, or through the API. Every plan includes API access. See [API reference](/docs/api-reference/introduction). For scheduled exports or a full workspace dump, contact [help@octolane.com](mailto:help@octolane.com) to confirm availability for your workspace. Before cancelling, export any data you need to keep. See [Billing](/docs/account/billing) for cancellation and data retention terms. # Importing data Source: https://octolane.com/docs/managing-data/importing Migrate CRM exports with Exodus 1, or import CSV data into Octolane. Octolane's migration model, **Exodus 1**, moves data from Attio, HubSpot, or Salesforce exports. Upload your deals, contacts, and accounts and ask Octolane to migrate. Exodus maps fields, links related records, merges duplicates, and enriches records as it goes. ## Migrate an existing CRM 1. Export the records you need from your source CRM and keep the original files. 2. Open your Octolane workspace and upload the exports. 3. Ask Octolane to migrate from the named CRM, such as “Migrate me from HubSpot.” 4. Review the resulting record counts, field values, relationships, and pipeline stages against representative source records. 5. Check important records and workflows before switching your team over. The published migration estimates are under five minutes from Attio, under 20 minutes from HubSpot, and under an hour from Salesforce. Use these as estimates, not a guarantee for every dataset or integration. ## CSV and spreadsheet imports For a spreadsheet or another source, save the data as CSV and use the import workflow. Review detected fields and related records. Custom-object imports require an eligible plan: Pro includes up to 10 custom objects; Team and Enterprise include unlimited custom objects. See [spreadsheet migration](/docs/managing-data/migrate-spreadsheet) or [Pipedrive migration](/docs/managing-data/migrate-pipedrive). The published Exodus migration estimates above apply to Attio, HubSpot, and Salesforce. ## Migration support and usage Founder includes self-serve migration. On Pro and above, the Octolane team can run the migration for you. Enterprise includes white-glove migration from any CRM and two-way Salesforce sync during a transition. Enrichment remains subject to your plan's credits. Keep source exports until you have verified the migration; contact [help@octolane.com](mailto:help@octolane.com) for help with custom data, recovery, or migration scope. # Merging duplicates Source: https://octolane.com/docs/managing-data/merging-duplicates Find and merge duplicate accounts and contacts. Octolane surfaces duplicates automatically based on email, domain, and entity name. Review candidates, pick the surviving record, and merge. All history and activity rolls up. # Migrating from Attio Source: https://octolane.com/docs/managing-data/migrate-attio Move Attio exports into Octolane with Exodus 1, automatic field mapping, relationship linking, and deduplication. Use **Exodus 1**, Octolane's migration model, to move Attio data without manually mapping every field. 1. Export your companies, people, and deals from Attio. Keep the original exports for comparison. 2. Open your Octolane workspace and upload the files. 3. Ask Octolane: “Migrate me from Attio.” Exodus maps fields, links contacts to accounts and deals, merges duplicates, and enriches records. 4. Review record counts, important fields, relationships, and pipeline stages against the source data. 5. Have each person connect Gmail and Google Calendar for ongoing conversation and meeting updates. The website estimates migration from Attio in under five minutes. Timing and coverage depend on the dataset; confirm custom objects, history, attachments, and integrations with the team before cutover. Founder includes self-serve migration. Pro and Team include migration run by the Octolane team, and Enterprise includes white-glove migration. See [Importing data](/docs/managing-data/importing) and [Plans and pricing](/docs/account/plans-pricing). For help, email [help@octolane.com](mailto:help@octolane.com). # Migrating from HubSpot Source: https://octolane.com/docs/managing-data/migrate-hubspot Move HubSpot exports into Octolane with Exodus 1, automatic field mapping, relationship linking, and deduplication. Use **Exodus 1**, Octolane's migration model, to move HubSpot data without manually mapping every field. 1. Export your companies, contacts, and deals from HubSpot. Keep the original exports for comparison. 2. Open your Octolane workspace and upload the files. 3. Ask Octolane: “Migrate me from HubSpot.” Exodus maps fields, links contacts to accounts and deals, merges duplicates, and enriches records. 4. Review record counts, important fields, relationships, and pipeline stages against the source data. 5. Have each person connect Gmail and Google Calendar for ongoing conversation and meeting updates. The website estimates migration from HubSpot in under 20 minutes. Timing and coverage depend on the dataset; confirm custom objects, history, attachments, and integrations with the team before cutover. Founder includes self-serve migration. Pro and Team include migration run by the Octolane team, and Enterprise includes white-glove migration. See [Importing data](/docs/managing-data/importing) and [Plans and pricing](/docs/account/plans-pricing). For help, email [help@octolane.com](mailto:help@octolane.com). # Migrating from Pipedrive Source: https://octolane.com/docs/managing-data/migrate-pipedrive Step-by-step switch from Pipedrive. 1. Export Organizations, People, Deals, Activities, and Notes as CSV from Pipedrive. 2. Connect Gmail and Calendar. 3. [Import each CSV](/docs/managing-data/importing). Review the resulting pipeline stages and relationships. 4. Re-create any custom fields. Confirm migration scope and timing with [help@octolane.com](mailto:help@octolane.com), especially for custom fields, activities, and notes. # Migrating from Salesforce Source: https://octolane.com/docs/managing-data/migrate-salesforce Move Salesforce exports into Octolane with Exodus 1, automatic field mapping, relationship linking, and deduplication. Use **Exodus 1**, Octolane's migration model, to move Salesforce data without manually mapping every field. 1. Export your accounts, contacts, and opportunities from Salesforce. Keep the original exports for comparison. 2. Open your Octolane workspace and upload the files. 3. Ask Octolane: “Migrate me from Salesforce.” Exodus maps fields, links contacts to accounts and deals, merges duplicates, and enriches records. 4. Review record counts, important fields, relationships, and pipeline stages against the source data. 5. Have each person connect Gmail and Google Calendar for ongoing conversation and meeting updates. The website estimates migration from Salesforce in under an hour. Timing and coverage depend on the dataset; confirm custom objects, history, attachments, and integrations with the team before cutover. Enterprise includes two-way Salesforce sync to keep the systems in step during a transition. Confirm integration scope with the Octolane team. Founder includes self-serve migration. Pro and Team include migration run by the Octolane team, and Enterprise includes white-glove migration. See [Importing data](/docs/managing-data/importing) and [Plans and pricing](/docs/account/plans-pricing). For help, email [help@octolane.com](mailto:help@octolane.com). # Migrating from a spreadsheet Source: https://octolane.com/docs/managing-data/migrate-spreadsheet Import spreadsheet data and verify your CRM records. Import a CSV, then check the resulting records and relationships before using them in workflows. 1. Save your sheet as CSV. 2. [Import](/docs/managing-data/importing). Even messy column names map well. 3. Connect Gmail and Calendar. Octolane builds conversation context from your history; enrichment follows your plan and remaining credits. 4. Run [Merging duplicates](/docs/managing-data/merging-duplicates) once. Compare representative records and counts against your source sheet before completing the migration. # Building your pipeline Source: https://octolane.com/docs/pipelines/building Stages, criteria, and probability. Settings → Pipelines → New. For each stage define: * **Name** and color * **Probability** (used by AI Chat forecasts) * **Entry criteria**. Conditions that auto-advance a deal in * **Exit criteria**. What must be true before moving on Keep it to 5–7 stages for founder-led motions. # Multiple pipelines Source: https://octolane.com/docs/pipelines/multiple Run sales, CS, and partnerships in separate pipelines. Create as many pipelines as you need: New Business, Expansion, Partnerships, Customer Success renewals. Each opportunity lives in exactly one pipeline at a time, but can be cloned across. # Stage automation Source: https://octolane.com/docs/pipelines/stage-automation Auto-advance deals based on real conversation signals. Stage automation watches conversations and meetings for stage-advancement signals. E.g. "demo booked" → Demo Scheduled, "pricing sent" → Proposal Sent, "agreement signed" → Closed Won. Stage changes follow workspace agent and approval settings. Review proposed changes when required and verify automatic changes on the record timeline. Automation-run limits depend on your [plan](/docs/account/plans-pricing). See [Approvals](/docs/ai/approvals). # Working with opportunities Source: https://octolane.com/docs/pipelines/working-with-opportunities Day-to-day deal management. * Open an opportunity to see the full timeline, AI fields, tasks, and people. * Drag across stages on the board view. * Bulk-update from list view. * Snooze a deal until a specific date. It disappears from your active view until then. * @mention a teammate inline to loop them in. # Working through your approval queue Source: https://octolane.com/docs/playbooks/approval-queue How to run the approval queue without it piling up. ## Rules 1. **Same time, every day.** 15 minutes morning, 15 minutes evening. Calendar block it. 2. **Decide every item.** Approve, edit, or reject. Never leave it. 3. **Use `A` / `R`.** Approve-next and reject-next keyboard shortcuts. 4. **Tune thresholds weekly.** Items you almost always approve → auto-approve at high confidence. 5. **Reject with reason.** The system learns from your rejection reasons. ## When the queue is overflowing * Filter by action type and review similar proposals together before approving changes. * Move email drafts to a separate dedicated session. * Review automation rules for low-risk items; enable automatic execution only for the changes your team intends to delegate. # Your first 7 days Source: https://octolane.com/docs/playbooks/first-7-days A seven-day setup and workflow checklist. Use the first week to verify your data, build a repeatable workflow, and review the decisions Octolane brings to you. ## Day 1 * Connect Gmail + Calendar * Confirm initial sync completed ## Day 2 * Import any list from your old CRM or spreadsheet * Run merge-duplicates pass ## Day 3 * Define 3 AI fields * Build your pipeline (5 stages max) ## Day 4 * Run your first AI Chat report: *"Pipeline by stage."* * Review the queue; approve, edit, or reject each proposed action ## Day 5 * Install Signal on your site * Turn on meeting bot ## Day 6 * Invite teammates (or don't. Solo works) * Build 3 saved views ## Day 7 * Forecast: *"This quarter, commit and best case."* * Audit AI field accuracy; tune prompts * Review new learnings in [Knowledge](/docs/ai/company-brain) # Founder-led sales with Octolane Source: https://octolane.com/docs/playbooks/founder-led-sales The full motion for solo and two-founder teams. The system that lets one or two founders run hundreds of conversations without dropping balls. 1. **Capture everything automatically**. Gmail + Calendar do the data entry. 2. **Define AI fields for what matters**. Decision maker, budget, timeline, blocker, next step. 3. **One pipeline, five stages**. Keep it simple until volume forces complexity. 4. **Daily approval queue**. 15 minutes morning and evening. 5. **Weekly forecast in AI Chat**. *"Forecast this week, commit and best case."* 6. **Friday cleanup**. *"Deals with no activity in 14 days, sorted by amount."* # Inbound from website Source: https://octolane.com/docs/playbooks/inbound-website Signal → AI scoring → outreach → deal. Use company-level website activity to find relevant accounts. Visitor tracking is included on every plan; agentic prospecting, intent signals, and advanced enrichment start on Pro. See [Plans and pricing](/docs/account/plans-pricing). 1. **Install Signal**. One snippet on your site. 2. **Define ICP filters**. Signal surfaces only companies that match. 3. **AI scoring**. Each visit scored on fit + intent (pages viewed, return visits). 4. **AI-drafted outreach**. Personalized openers referencing what they read. 5. **Approve and send**. Drafts queue for review. 6. **Auto-create deal on reply**. Octolane detects buying intent in the conversation and creates or proposes an opportunity according to workspace settings. # Never miss a follow-up Source: https://octolane.com/docs/playbooks/never-miss-followup A daily workflow for reviewing follow-ups. Use a daily review to keep important conversations moving. ## Setup 1. Turn on auto-follow-up drafts with manual approval 2. Set follow-up windows per stage (e.g. 2 days post-demo, 7 days post-proposal) 3. Save a view: "Drafts awaiting approval" 4. Calendar block 15 minutes daily at the same time ## Daily ritual * Open the approval queue * Approve, edit, or reject. Never skip * Anything genuinely not worth a follow-up: snooze, don't ignore # Playbooks Source: https://octolane.com/docs/playbooks/overview Practical sales workflows for founder-led and B2B teams. Choose a workflow to try this week, then adapt it to your team and [plan limits](/docs/account/plans-pricing). > [card] [Founder-led sales](/docs/playbooks/founder-led-sales) > > The full motion for solo and two-founder teams. > [card] [Never miss a follow-up](/docs/playbooks/never-miss-followup) > > A daily workflow for reviewing follow-ups. > [card] [Run 50 demos in 30 days](/docs/playbooks/run-50-demos) > > The demo sprint playbook. > [card] [Your first 7 days](/docs/playbooks/first-7-days) > > A seven-day setup checklist. > [card] [Inbound from website](/docs/playbooks/inbound-website) > > Signal → AI scoring → outreach → deal. > [card] [Approval queue](/docs/playbooks/approval-queue) > > Run the queue without it piling up. > [card] [YC founders](/docs/playbooks/yc-founders) > > How seed–Series A founder-led teams run sales on Octolane. # Run 50 demos in 30 days Source: https://octolane.com/docs/playbooks/run-50-demos The demo sprint playbook. A four-week plan with a target of 50 qualified demos. Results depend on your audience and execution. AI prospecting starts on Pro; sending-account, sequence, and automation limits depend on your [plan](/docs/account/plans-pricing). ## Week 1: list + ICP * Define ICP precisely (industry, headcount, tech stack, signal) * Build a list of 500 fitting accounts (Signal + import + manual) ## Week 2: outreach * AI-drafted personalized outreach, 100/day * Review each proposed message; track reply rate by message variant ## Week 3: book * Triple-touch sequence on no-reply * Calendar links in every approved follow-up ## Week 4: run * Meeting bot on every call * Approval queue every morning to advance stages and queue next steps # The Octolane playbook for YC founders Source: https://octolane.com/docs/playbooks/yc-founders How seed–Series A founder-led teams run sales on Octolane. You're the founder. You're also the SDR, AE, CS, and product team. This playbook is the minimum-viable sales OS that scales with you to your first 10 reps. YC companies get Founder free for one year. Founder supports up to three users; move to Pro as you add a fourth user or need additional capabilities. See [Plans and pricing](/docs/account/plans-pricing). ## Week 1: foundation * Connect Gmail + Calendar * Import any existing prospects from your sheet * Define 3 AI fields: "decision maker", "next step", "blocker" * Build a 5-stage pipeline: Lead → Qualified → Demo → Proposal → Closed ## Week 2: rhythm * Approval queue every morning, 15 minutes max * All demos recorded; review summaries instead of taking notes * Friday: ask AI Chat for "deals with no activity in 7 days" ## Week 3+: leverage * Install Signal on your site * Turn on auto-follow-up with manual approval * Start drafting outreach to Signal-identified ICP visitors # Comments Source: https://octolane.com/docs/productivity/comments Discuss a deal inside the record. Comments live on the right rail of any record. Threaded, @mentionable, resolvable. Keep deal discussion out of Slack and on the deal. # Email composer Source: https://octolane.com/docs/productivity/email-composer Send from Octolane with AI drafting support. Send emails from within any record. The composer drafts with full context. The thread, the deal, the AI fields, your past replies. Sends through your connected Gmail; lands in your Sent folder. # Keyboard shortcuts Source: https://octolane.com/docs/productivity/keyboard-shortcuts The full list. | Action | Shortcut | | - | - | | Open AI Chat | `Cmd+/` | | Quick create | `C` | | Search | `/` | | Toggle sidebar | `[` | | Next record | `J` | | Previous record | `K` | | Complete task | `X` | | Snooze task | `Z` | | Compose email | `E` | | Approve next item | `A` | | Reject next item | `R` | | Help | `?` | # Notes and mentions Source: https://octolane.com/docs/productivity/notes-mentions @mention teammates, link to records. Drop notes on any record. Use `@` to mention a teammate (they get notified) or to link to another record. Markdown supported. # Tasks workflows Source: https://octolane.com/docs/productivity/tasks Daily task management, snoozing, and task views. * **Today view**. What's due today across all your records. * **Snooze**. Push a task to a specific date and time. * **Recurring tasks**. Daily, weekly, custom cadences. * **Auto-generated**. Meetings and emails create tasks for you. * **Assignment**. Assign to teammates with @mention. # Forecasting Source: https://octolane.com/docs/reports/forecasting How AI Chat builds forecasts from real deal signals, not stage averages. Octolane's forecast doesn't trust your stage assignments alone. It re-scores every deal using: * Recency and depth of conversations * AI-extracted decision criteria, blockers, and timelines * Historical win rate of similar deals in your workspace Ask AI Chat: *"Forecast this quarter, commit and best case."* # Reporting in Octolane Source: https://octolane.com/docs/reports/overview Reporting is conversational. Ask AI Chat for any report and it generates it live. Reports are available on every plan. Open AI Chat and ask: > "Pipeline by stage, this quarter, grouped by rep, exclude churn." Review the returned table or chart against your CRM data. Custom reporting and dashboards start on Pro, which includes up to 10 dashboards. Team and Enterprise include unlimited dashboards. Founder does not include dashboards. See [Plans and pricing](/docs/account/plans-pricing). See [Common report recipes](/docs/reports/recipes). # Common report recipes Source: https://octolane.com/docs/reports/recipes Pipeline health, deal velocity, forecast, win/loss, activity per rep. With exact prompts. Copy these prompts into AI Chat. ## Pipeline health > "Show open pipeline by stage with total amount and deal count. Flag any deal with no activity in the last 14 days." ## Deal velocity > "Average days in each stage for deals closed in the last 90 days." ## Forecast > "Forecast for this quarter based on weighted pipeline and historical close rate per stage." ## Win/loss > "Win rate by source over the last two quarters. Break down lost deals by reason." ## Activity per rep > "Emails sent, meetings held, and deals advanced by rep this week." # Security & Privacy Source: https://octolane.com/docs/security Security certifications, workspace permissions, company learning, and plan-specific data controls. Octolane protects workspace data and applies access controls to people and connected agents. See the [published security overview](https://www.octolane.com/security) and [pricing comparison](https://www.octolane.com/pricing) for current commitments. ## Certifications and compliance Octolane lists SOC 2 Type I and II and ISO 27001 certification. All plans use HIPAA-ready infrastructure; Enterprise includes HIPAA support and a BAA. Enterprise also adds a security review and custom DPA. Confirm contractual requirements with [sales](mailto:sales@octolane.com). ## Access and agent permissions * Founder includes admin and member roles; Pro includes custom roles; Team and Enterprise include advanced permissions. * SSO and SCIM provisioning are Enterprise features. * Personal API keys act as the member who created them, using that member's current access. Disabled keys and keys belonging to members who leave the workspace stop working. * External agents use the connected person's permissions. API and MCP writes are not automatically routed through the in-app approval queue. See [Team and permissions](/docs/account/team-permissions) and [MCP authentication](/docs/mcp/authentication). ## Learning from your team's work Your data is not pooled into shared models or used to improve other customers' agents. Octolane uses your team's decisions, approvals, edits, and outcomes to improve your own team's context and behavior. The [company brain](/docs/ai/company-brain) is version-controlled, and new learnings wait for review before retention. This distinction matters: learning for your own team is different from training shared models on your data. The [website FAQ](https://www.octolane.com/faq.md) explains the published approach. ## History, exports, and cancellation Field history, audit logs, and company-brain version history have plan-specific retention: 90 days on Founder, one year on Pro, two years on Team, and custom retention on Enterprise. Enterprise also includes audit log export. You can export data as CSV or JSON or through the API. The pricing terms state that data is retained for 30 days after cancellation, then deleted. These cancellation terms are separate from history retention and individual record-deletion behavior. See [Billing](/docs/account/billing). ## Security questions For security documentation, data-handling details, or vulnerability reports, contact [security@octolane.com](mailto:security@octolane.com). See the [privacy policy](https://www.octolane.com/privacy-policy) for published privacy terms. # Talk to us Source: https://octolane.com/docs/support/contact Email the Octolane team, book a call, call us, or start an in-app chat. Choose the channel that works best for you. Product questions, setup help, migrations, and support all reach the Octolane team directly. > [card] [Email us](mailto:help@octolane.com) > > **[help@octolane.com](mailto:help@octolane.com)** > > Email support is included on every plan. Enterprise includes priority support with an SLA. > [card] [Book a call](https://cal.com/octolane/support) > > **Schedule a 15-min call** > > Walk through your issue live with someone on the team. Best for setup help, migration questions, or feature walkthroughs. > [card] [Call us](tel:+16282851600) > > **+1 (628) 285-1600** > > Available during business hours (9am–6pm PT, Mon–Fri). Leave a voicemail outside hours and we'll call you back. > [card] [Chat in app](https://octolane.com/dashboard) > > **In-app chat** > > Click the chat icon in the bottom-right corner of your Octolane dashboard for real-time help. *** ## Talk to the founder Have product feedback, a feature request, or just want to share how things are going? Reach out to One Chowdhury (CEO) directly: * **Email:** [one@octolane.com](mailto:one@octolane.com) * **X (Twitter):** [@coffeewithone](https://x.com/coffeewithone) * **LinkedIn:** [One Chowdhury](https://www.linkedin.com/in/coffeewithone/) We read every message and build based on what our customers need. *** ## Common issues before you reach out > [accordion] My email or calendar shows 'Disconnected' > > This usually happens when not all permissions were granted during setup. Go to **Settings → Integrations → Gmail & Calendar**, click the three-dot menu next to the disconnected account, select **Reconnect**, and make sure you grant all required permissions. > [accordion] Signal isn't detecting visitors > > Check that the Signal script is loading on your site - open your browser's developer tools, go to the Network tab, and filter for "octolane." If the script isn't loading, verify it's in your site's `` tag. If it is loading but you're not seeing data, give it 15-30 minutes for the first visitors to appear. > [accordion] Agents aren't creating deals from my email > > Make sure your email account is connected and showing as active in **Settings → Integrations**. Initial processing time depends on the connected history. If sync has finished and expected sales conversations have not produced records or proposals, email us for help. > [accordion] I need to change my plan or billing info > > Use your workspace billing settings to review payment details and your subscription. Upgrades are prorated and downgrades take effect at renewal. See [Billing](/docs/account/billing), or email [help@octolane.com](mailto:help@octolane.com) for assistance. *** ## Follow us Stay up to date with product updates, tips, and community discussions. * **X (Twitter):** [@octolane](https://x.com/octolane) * **LinkedIn:** [Octolane AI](https://linkedin.com/company/octolane) # Status Source: https://octolane.com/docs/support/status Live system status for Octolane. Live status, incidents, and historical uptime: [status.octolane.com](https://status.octolane.com). Subscribe to incident updates via email, RSS, Slack, or webhook. # Trust Source: https://octolane.com/docs/support/trust Security, privacy, and compliance at Octolane. See [Security](/docs/security) for SOC 2 Type I and II, ISO 27001, HIPAA-ready infrastructure, workspace access controls, team-specific learning, and plan-dependent retention. Enterprise includes SSO/SCIM, a BAA, and a security review. For security disclosures: [security@octolane.com](mailto:security@octolane.com). # Slack (beta) Source: https://octolane.com/docs/tools/slack Octolane in Slack with AI 2.0. Run tasks end-to-end from a thread. > [!NOTE] > > The Slack agent is included on every plan. Slack conversation sync is included on **Team** and **Enterprise**. See [Plans and pricing](/docs/account/plans-pricing). The Slack app is in **beta**; email [help@octolane.com](mailto:help@octolane.com) for help with personalized setup. What you can do from Slack: * Ask AI Chat any question and get the answer in-thread * Create opportunities, tasks, notes, contacts * Get deal alerts and stage advancements * Approve queued actions without leaving Slack * @octolane mentions in any channel # Zapier Source: https://octolane.com/docs/tools/zapier Connect Octolane to other tools with Zapier. Octolane supports integrations through Zapier, the REST API, and webhooks. Every plan includes API access and webhooks. Choose from the triggers and actions available in your connected Zapier app; their availability determines which workflows you can build. For custom API requests, use the [published API schema](/docs/api-reference/introduction). Create personal API keys in [Settings → API keys](https://www.octolane.com/settings/api-keys). Requests use the key creator's workspace permissions. Automations and enrichment remain subject to [plan limits](/docs/account/plans-pricing). # Tutorials Source: https://octolane.com/docs/tutorials/overview Focused Octolane walkthroughs organized by the job you want to complete. Choose a result and follow the shortest path to it. Each tutorial links to the detailed reference when you need more context. ## Start here > [card] [Connect your workspace](/docs/course/connect) > > Gmail, Calendar, and the first sync. > [card] [Understand your CRM](/docs/course/records) > > Accounts, contacts, opportunities, and activities. > [card] [Build a pipeline](/docs/course/pipeline) > > Stages, criteria, probability, and a test opportunity. ## Meetings and follow-ups > [card] [Record and review a meeting](/docs/course/meeting-recorder) > > Configure Octo and verify the recap workflow. > [card] [Never miss a follow-up](/docs/playbooks/never-miss-followup) > > Turn stale conversations into a daily review habit. > [card] [Work through approvals](/docs/playbooks/approval-queue) > > Review AI-prepared changes quickly and safely. > [card] [Draft outreach](/docs/ai/drafted-outreach) > > Use context and enrichment to prepare a message. ## Data and migration > [card] [Import CRM data](/docs/managing-data/importing) > > Let Exodus map and link CRM exports, then verify the imported records. > [card] [Merge duplicates](/docs/managing-data/merging-duplicates) > > Review matches and preserve the right history. > [card] [Migrate from HubSpot](/docs/managing-data/migrate-hubspot) > > Move companies, contacts, deals, and engagement history. > [card] [Migrate from a spreadsheet](/docs/managing-data/migrate-spreadsheet) > > Turn rows and columns into connected CRM records. ## Company knowledge Use [Knowledge](/docs/ai/company-brain) to review what Octolane learns from your team and query that context from the app or MCP. ## Build and extend > [card] [Connect an AI client with MCP](/docs/mcp/quickstart) > > Use Octolane from Claude, ChatGPT, or Cursor. > [card] [Start with the API](/docs/api-reference/introduction) > > Authenticate, make a request, and explore the reference. # Bulk create activities Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-activities api-reference/openapi.json post /v1/activities/bulk Creates up to 100 timeline activities such as email, meeting, call, link click, or other interaction records. `created_at` must not be in the future (a few minutes of clock skew is tolerated); a later value rejects the request with 422. Activities never create accounts or contacts: participants are matched to existing contacts, and any participant email with no contact is listed in that item's `unknown_participants`. # Bulk create contact fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-contact-fields api-reference/openapi.json post /v1/contacts/fields/bulk Creates contact custom field definitions in bulk. # Bulk create notes Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-notes api-reference/openapi.json post /v1/notes/bulk Creates up to 100 notes and links each to existing accounts (by domain) and contacts (by email). Notes never create accounts or contacts: an item naming a domain or email that matches no record is not created and comes back with an empty `note_id` and `unknown_entities`, the same rule as the single-note 404. Domains are matched as their root domain (`https://www.acme.com/x` matches `acme.com`) and automated no-reply emails are ignored. # Bulk create opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-opportunities api-reference/openapi.json post /v1/opportunities/bulk Creates up to 100 opportunities using the standard opportunity payload shape. Duplicate rule, shared by `/v1/opportunities`, `/v1/opportunities/bulk` and `/v1/opportunities/fast-bulk`: within a pipeline, an item duplicates an existing opportunity linked to the same account domain (compared as the root domain, so `https://www.acme.com` matches `acme.com`) or, when the item has no domain, one with the same name (case and whitespace insensitive). An item with neither is matched on the name it will be created with, derived from its primary contact's email domain (`alice@acme.com` becomes `Acme Deal`); an item with no domain, name or contact is always created. A duplicate is never merged into the existing opportunity and none of its fields are applied; use `PATCH /v1/opportunities/bulk` to change the existing one. Concurrent creates of the same key are serialized across all three endpoints, so at most one opportunity is created. Duplicates of an existing opportunity, or of an earlier item in the same request, are skipped and listed in `skipped` with the opportunity they matched; the other items are created. # Bulk create or resolve contacts Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-or-resolve-contacts api-reference/openapi.json post /v1/contacts/bulk Creates or resolves up to 100 contact records in one request. New contacts are linked to the account for their work-email domain before the response returns; the account is created if the workspace has none for that domain. Personal email domains never get an account. # Bulk create pipeline fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-pipeline-fields api-reference/openapi.json post /v1/pipelines/{pipeline_id}/fields/bulk Creates opportunity custom field definitions for a pipeline in bulk. # Bulk create pipeline stages Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-create-pipeline-stages api-reference/openapi.json post /v1/pipelines/{pipeline_id}/stages/bulk Creates stages for a pipeline in bulk. # Bulk delete accounts, contacts, or opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-delete-accounts-contacts-or-opportunities api-reference/openapi.json delete /v1/{object_type}/bulk Deletes up to 500 existing objects. Accounts can be selected by `company_id` or `domain`; account domains accept plain domains or URLs and are normalized before lookup, for example `https://www.qualcomm.com` becomes `qualcomm.com`. Contacts can be selected by `people_id` or `email`; opportunities by `opportunity_id` or exact `name`. Opportunity name matching is exact after trimming and case folding, and all active opportunities matching a supplied name are deleted. # Bulk delete contact fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-delete-contact-fields api-reference/openapi.json delete /v1/contacts/fields/bulk Soft-deletes contact custom fields in bulk. Each item identifies one field by `id`, `attribute_id`, or `property_name`. System fields cannot be deleted. # Bulk delete pipeline fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-delete-pipeline-fields api-reference/openapi.json delete /v1/pipelines/{pipeline_id}/fields/bulk Soft-deletes opportunity custom fields for one pipeline in bulk. Each item identifies one field by `id`, `attribute_id`, or `property_name`. System fields cannot be deleted. Filters, sortings, and display settings referencing deleted fields are removed. # Bulk update accounts, contacts, or opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-update-accounts-contacts-or-opportunities api-reference/openapi.json patch /v1/{object_type}/bulk Updates up to 50 existing objects. The request body is keyed by object UUID, and each value is a patch object of field names to updated values. Field names can be either the names the read endpoints return (for example `name`, `industry`, `first_name`, `stage_id`, `amount`, `close_date`, `next_steps`) or the underlying `property_name` (`company_name`, `people_first_name`, `opportunity_stage`, `opportunity_deal_size`, `opportunity_close_date`, `opportunity_next_step`); see `BulkUpdateInput` for the full mapping. Custom fields are keyed by their `property_name` from `custom_field_definitions`. Sending both names for the same field in one item is rejected. Each item succeeds or fails on its own: the response lists one result per id with `success`, `statusCode` and, on failure, a `message` naming the rejected field and why. The top-level status is 200 when every item succeeded, 207 when some did, and 422 when none did. For opportunity relationship fields, `opportunity_account`, `opportunity_contact`, and `opportunity_other_stakeholders` use replace semantics: supplying the field clears the existing mapping of that type, then writes the supplied UUID or UUID list. Use `null` to clear `opportunity_account` or `opportunity_contact`; use `null` or `[]` to clear `opportunity_other_stakeholders`. Every supplied account or contact UUID must belong to an existing record in the workspace; an unknown UUID fails that item with 404 and nothing is written for it. # Bulk update contact fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-update-contact-fields api-reference/openapi.json post /v1/contacts/fields/bulk/update Updates contact field definitions in bulk. Identify each field by `id` or `property_name`. `property_name` is a stable identifier and cannot be renamed; if you include it with `id`, it must match the stored field `property_name` exactly. # Bulk update pipeline fields Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-update-pipeline-fields api-reference/openapi.json post /v1/pipelines/{pipeline_id}/fields/bulk/update Updates opportunity field definitions for a pipeline in bulk. Identify each field by `id`/`attribute_id` or `property_name`. Opportunity fields are pipeline-scoped, so use this pipeline endpoint. `property_name` is a stable identifier and cannot be renamed; if you include it with `id`/`attribute_id`, it must match the stored field `property_name` exactly. # Bulk update pipeline stages Source: https://octolane.com/docs/api-reference/endpoints/crm/bulk-update-pipeline-stages api-reference/openapi.json post /v1/pipelines/{pipeline_id}/stages/bulk/update Updates stages for a pipeline in bulk. # Create a note Source: https://octolane.com/docs/api-reference/endpoints/crm/create-a-note api-reference/openapi.json post /v1/notes Creates a note and optionally links it to existing accounts by domain and existing contacts by email. Notes never create accounts or contacts: if any `account_domains` or `contact_emails` entry matches no record in the workspace, the request is rejected with 404, the response lists the unknown entries in `errors.unknown_entities`, and no note is created. # Create an opportunity Source: https://octolane.com/docs/api-reference/endpoints/crm/create-an-opportunity api-reference/openapi.json post /v1/opportunities Creates an opportunity in a pipeline and resolves related account, primary contact, additional contacts, owner, and stage from the supplied identifiers. Duplicate rule, shared by `/v1/opportunities`, `/v1/opportunities/bulk` and `/v1/opportunities/fast-bulk`: within a pipeline, an item duplicates an existing opportunity linked to the same account domain (compared as the root domain, so `https://www.acme.com` matches `acme.com`) or, when the item has no domain, one with the same name (case and whitespace insensitive). An item with neither is matched on the name it will be created with, derived from its primary contact's email domain (`alice@acme.com` becomes `Acme Deal`); an item with no domain, name or contact is always created. A duplicate is never merged into the existing opportunity and none of its fields are applied; use `PATCH /v1/opportunities/bulk` to change the existing one. Concurrent creates of the same key are serialized across all three endpoints, so at most one opportunity is created. A duplicate answers 409. # Cursor-list opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/cursor-list-opportunities api-reference/openapi.json get /v1/opportunities Returns opportunities in a required pipeline using cursor pagination with optional stage, search, and field projection. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each opportunity's `custom_fields` object. # Fast bulk create opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/fast-bulk-create-opportunities api-reference/openapi.json post /v1/opportunities/fast-bulk Creates up to 100 opportunities with nested account and contact payloads. This optimized endpoint batch-resolves accounts, contacts, owners, and stages before inserting opportunities. An item whose `owner_id` / `owner_email` is not a workspace member rejects the request with 422 before anything is created. Duplicate rule, shared by `/v1/opportunities`, `/v1/opportunities/bulk` and `/v1/opportunities/fast-bulk`: within a pipeline, an item duplicates an existing opportunity linked to the same account domain (compared as the root domain, so `https://www.acme.com` matches `acme.com`) or, when the item has no domain, one with the same name (case and whitespace insensitive). An item with neither is matched on the name it will be created with, derived from its primary contact's email domain (`alice@acme.com` becomes `Acme Deal`); an item with no domain, name or contact is always created. A duplicate is never merged into the existing opportunity and none of its fields are applied; use `PATCH /v1/opportunities/bulk` to change the existing one. Concurrent creates of the same key are serialized across all three endpoints, so at most one opportunity is created. The domain is `related_objects.account.domain`. Duplicates are skipped and reported exactly as in `/v1/opportunities/bulk`. # Get record field history Source: https://octolane.com/docs/api-reference/endpoints/crm/get-record-field-history api-reference/openapi.json get /v1/{object_type}/{object_id}/history Returns the field-change history for a record, newest first. Each entry includes the field (`property_name` plus a display `property_label`), the previous and new values (with `old_value_label`/`new_value_label` resolved for reference values such as deal stages and accounts), the author (`user` is the person when one was involved; it is null when no person wrote the row; a write made through this API is authored by the member who created the API key), the `source` naming which surface made the change (`user_web`, `public_api`, `mcp`, `chat`, `workflow`, `enrichment`, `integration_sync`, `csv_import`, `system`, or null for entries predating the field) plus `source_api_key_id` identifying which API key wrote when `source` is `public_api`, `change_kind` (`created` for a value the record was created with, `updated`, or `linked`/`unlinked` for a single deal stakeholder; null for entries predating the field), `metadata` (`tool` and `mcp_key_id` naming the agent tool and connection for `mcp` writes, `defaulted` when the system filled a creation value in), and the change timestamp. Account, contact, stakeholder and owner values on deals are labelled too. Filter to a single field with `property_name`. # List contact fields Source: https://octolane.com/docs/api-reference/endpoints/crm/list-contact-fields api-reference/openapi.json get /v1/contacts/fields Returns contact field definitions, including system fields and custom fields. Use `property_name` as the stable key for custom field values. # List notes Source: https://octolane.com/docs/api-reference/endpoints/crm/list-notes api-reference/openapi.json get /v1/notes Returns notes for the authenticated organization. # List pipeline fields Source: https://octolane.com/docs/api-reference/endpoints/crm/list-pipeline-fields api-reference/openapi.json get /v1/pipelines/{pipeline_id}/fields Returns opportunity field definitions for a pipeline, including system fields and custom fields. # List pipeline stages Source: https://octolane.com/docs/api-reference/endpoints/crm/list-pipeline-stages api-reference/openapi.json get /v1/pipelines/{pipeline_id}/stages Returns active stages for a pipeline ordered by `stage_order`. # List pipelines Source: https://octolane.com/docs/api-reference/endpoints/crm/list-pipelines api-reference/openapi.json get /v1/pipelines Returns opportunity pipelines and their stages for the authenticated organization. # Search contacts Source: https://octolane.com/docs/api-reference/endpoints/crm/search-contacts api-reference/openapi.json post /v1/contacts/search Search contacts with structured filters, sort, cursor pagination, and field projection. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each contact's `custom_fields` object. # Search opportunities Source: https://octolane.com/docs/api-reference/endpoints/crm/search-opportunities api-reference/openapi.json post /v1/opportunities/search Search opportunities with optional pipeline scope, stage, structured filters, sort, cursor pagination, and field projection. `pipeline_id` is optional; when omitted the search spans every pipeline in the org. Custom attribute names and value types are returned in `data.custom_field_definitions`; keys in that map match keys under each opportunity's `custom_fields` object. # Soft delete a pipeline stage Source: https://octolane.com/docs/api-reference/endpoints/crm/soft-delete-a-pipeline-stage api-reference/openapi.json delete /v1/pipelines/{pipeline_id}/stages/{stage_id} Soft deletes a stage in a pipeline. If deals are in that stage, they are reassigned to `destination_stage_id` when supplied, otherwise to the best remaining stage in the pipeline. # Changelog Source: https://octolane.com/docs/changelog What's new in Octolane. Product updates, new features, improvements, and bug fixes. We ship daily. **November 17, 2026** Shared mailboxes ### Share a mailbox with your team * In Settings, Email & calendar, choose whether only you, all members, or selected teammates can send from a mailbox you own. * Mailboxes shared with you appear under Shared accounts, and you can make one your default sender. * Your profile and the workspace name and logo now save as you change them, with no Save button. * Fixed links in update emails opening a Page not found error. **November 16, 2026** Pricing * Plan cards now lead with the per-seat price, with included seats and billing totals shown alongside it. **November 15, 2026** Plans * Compare plan features, usage limits, and support options in the updated pricing cards. * Hover over underlined features for an explanation of what is included. **November 14, 2026** Workspace members * Manage members and pending invitations from a consistent list in Settings. * Change roles from each member's menu, with the current role marked. * Removing a member or canceling an invitation now asks you to type their name or email to confirm. **November 13, 2026** API keys * Give API keys recognizable names and rename them from Settings. * Manage a key's active status and delete keys you no longer need from its row menu. **November 12, 2026** Meeting Recorder * Fixed live meetings showing the recording indicator when recording was turned off. **November 11, 2026** Interface * Updated outline icons across records, meetings, Review, and Knowledge to use a consistent visual weight. **November 10, 2026** Meetings * Choose your notetaker's name and appearance in Meeting Recorder settings. * Fixed the meeting page crashing while AI-generated preparation or summaries streamed in. **November 9, 2026** Tasks and notes ### Work through tasks and notes with fewer steps * Group tasks by due date and complete or reschedule them from the list. * Ask AI to edit selected text in a note. * Copy or download notes from the note menu. **November 6, 2026** Tasks * Fixed opening a task that ends with a record mention causing an error. * Saved mentions keep their record link when you reopen and edit a task. **November 5, 2026** Meeting Recorder * Settings now show the invited-meetings rule when you have not chosen an automatic recording rule. **November 4, 2026** CSV imports ### Review your account import before it runs * Map CSV columns to existing or new fields before approving an account import. * Preview the mapped records and see which accounts will be added or updated. * Follow progress in the import card and open the accounts when it finishes. **November 3, 2026** ChatGPT ### Use Octolane from ChatGPT * Search contacts, deals, emails, and meetings from a ChatGPT conversation. * Update records or add a deal through the Octolane connection. * Access follows your Octolane account permissions. [Connect Octolane to ChatGPT](/docs/mcp/use-with-chatgpt). **November 2, 2026** Text editing * Fixed some text disappearing in the text editor. * Preserved leading indentation when loading Markdown, so indented text keeps its intended formatting. **November 1, 2026** Pipelines * Choose a pipeline stage from a simpler picker, with open stages grouped before closed stages. **October 31, 2026** Meetings * Next Meeting fields on accounts, contacts, and deals stop showing a meeting once its start time has passed. **October 30, 2026** MCP connections * Find assistant connections through the connector cards in MCP settings. * Revoking an MCP key now opens a confirmation dialog, and revoked keys no longer offer reactivation in Settings. **October 29, 2026** Bug fixes * Fixed Create contact errors triggered by Chrome autofill * Fixed email, number, and date fields throwing an error when they received focus **October 28, 2026** Activities * Fixed the New activity form crashing when dictation or text-expander tools inserted text rapidly * Long dictated activity descriptions now remain responsive and save normally **October 27, 2026** Pipelines ### Set up a pipeline in one step Create a complete pipeline from one form, with its stages and fields visible before you save it. * Describe what you sell in one sentence and let Octolane draft the pipeline * Start from a CSV and turn its columns into typed fields and its stages into a board * Add, rename, remove, and reorder stages before creating the pipeline * Customize fields alongside the eight fields included with every deal * Clear the form back to its original state after making changes * Fixed the form opening at partial height and growing after it appeared * Fixed the Support link in Octolane emails * Kept AI Chat available when a transient session check fails * Made Reporting use one consistent configured data source for cards, drilldowns, and exports **October 26, 2026** Reliability * Kept next-meeting data current in workspaces with very large activity histories * Failed search updates now retain enough state to repair themselves safely * Fixed filtered bulk account deletion failing for empty and non-empty field filters * Fixed new teammates receiving a Forbidden error when accepting an invitation from the workspace chooser **October 21, 2026** Search ### Find the right record fast Command bar search now gives you enough context to choose the right record before opening it. * Contacts show their email and accounts show their domain * Results are grouped into accounts, contacts, and deals * Hover or use the arrow keys to preview a record's important fields * Field icons are consistent across search previews, tables, and pipeline forms **October 20, 2026** Tasks ### A new way to write tasks * Set a due date and time from the task form without opening another window * Format task text and add links to documents, meetings, email addresses, and phone numbers * Unsaved task drafts survive an accidental Escape or click outside the form * Mark tasks done or not done directly while editing * Select several assignees and linked records without reopening their lists **October 13, 2026** Home ### Your day in four cards The new session page opens with a focused view of your day. * See your next meetings and join calls that are about to start * Work through tasks or Review items that need your attention * Open your busiest pipelines and see their open deal value * Track win rate, closed value, and average sales cycle over the last 30 days **October 5, 2026** Meeting Recorder ### Meet Octo, your AI notetaker * Octo introduces itself when it joins a call and explains that it is taking notes * Its tile shows who is speaking as the conversation moves around the room * When the call is quiet, Octo says whose notes it is taking * A personalized Octolane mark keeps the notetaker recognizable in every meeting **June 27, 2026** API ### Search opportunities across all pipelines `pipeline_id` is now optional on [`POST /v1/opportunities/search`](/docs/api-reference/endpoints/crm/search-opportunities). * Omit `pipeline_id` to search opportunities across every pipeline in the org * Pass `pipeline_id` to scope the search to a single pipeline, as before **June 15, 2026** AI Chat ### AI Chat: pinned conversations Keep your most important threads one click away. * Pin any AI Chat thread to the top of the history panel * Resume a pinned conversation with full context restored * Share a pinned thread with a teammate via link **June 14, 2026** Bug fixes * Fixed Signal occasionally double-counting sessions from the same visitor within a minute * Fixed AI field re-runs queuing twice when triggered from a bulk edit * Fixed the "last activity" column showing the wrong time for UTC+13 workspaces **June 13, 2026** Performance * Cut median search latency from 220ms to 90ms on workspaces with 50K+ records * Reduced MCP server cold-start time by 35% **June 12, 2026** Pipelines ### Pipeline: weighted forecast snapshots * Daily automatic snapshot of weighted pipeline value for trend charts * Compare any two snapshots side by side * Export snapshot history to CSV **June 11, 2026** Email ### Send-later scheduling Write now, send at the perfect moment. * Schedule any email to send at a specific date and time * Per-recipient timezone awareness so sends land during working hours * Scheduled sends are visible and editable from the composer **June 10, 2026** MCP * New `bulk_update_records` tool exposed over MCP * Tool calls now stream partial results for long-running queries * Clearer error messages when a tool is called with a missing required field **June 9, 2026** Bug fixes * Fixed CSV export dropping custom field columns added within the last hour * Fixed AI Chat losing the active pipeline filter after a page refresh * Fixed Slack notifications missing the deal amount for multi-currency workspaces **June 8, 2026** Polish * Refreshed the approval queue with a denser, faster-loading layout * New keyboard shortcut `G` then `A` to jump straight to Approvals * Subtle loading skeletons replace spinners across list views **June 7, 2026** Signal * Signal now resolves company identity for an additional 12% of anonymous traffic * Added "first seen" and "last seen" timestamps to every identified company * New filter: companies that viewed pricing in the last 7 days **June 6, 2026** Reports ### Scheduled report digests * Bundle multiple saved reports into a single scheduled email * Choose a daily, weekly, or monthly cadence per digest * Slack delivery option for any digest **June 5, 2026** Meeting Recorder * Recaps now open with a one-line "deal impact" summary * Correct a speaker label once and it applies retroactively across the transcript * Faster recap generation. Median time from call end to recap down to 90s **June 4, 2026** API ### Bulk update endpoint * New `PATCH /v1/{object_type}/bulk` to update accounts, contacts, or opportunities in one call * Up to 1,000 records per request * Partial-success reporting. Each record returns its own status **June 3, 2026** Bug fixes * Fixed enrichment occasionally overwriting manually edited company names * Fixed pipeline board scroll position jumping after an inline edit * Fixed `/forecast` excluding deals with a close date set to today **June 2, 2026** AI Fields * AI fields can now reference other AI fields in their prompt * Added a confidence badge so you can see how sure Octolane is about each value * Bulk re-run AI fields across any filtered view **June 1, 2026** Tasks ### Task dependencies * Mark a task as blocked by another. The blocked task stays hidden until its dependency is done * Dependency chains are visualized on the deal record * AI Chat understands dependencies: "What's blocking the Acme renewal?" **May 31, 2026** Performance * 50% faster initial load for the Reports tab * Reduced webhook delivery p99 from 1.2s to 0.5s **May 30, 2026** Polish * New empty-state illustrations for Signal, Tasks, and Reports * Improved contrast on AI-generated field highlights in dark mode * Consistent date formatting across every view **May 29, 2026** Approvals * Group approval queue items by agent or by record * "Approve and next" now preloads the following item for instant review * Added a daily summary of everything auto-approved overnight **May 28, 2026** Integrations ### HubSpot two-way sync (beta) Keep Octolane and HubSpot in lockstep, not just a one-time import. * Continuous sync with field-level mapping and conflict-resolution rules * Sync status dashboard with per-object counts * Pause or resync any object at any time **May 27, 2026** Bug fixes * Fixed Meeting Recorder bot occasionally staying in a call after it ended * Fixed contact merge not combining LinkedIn URLs * Fixed search highlighting persisting after the query was cleared **May 26, 2026** Mobile * Pipeline board is now fully usable on mobile with horizontal swipe between stages * Approve or reject queued actions from the mobile app * Offline mode caches your most recent views for read access **May 25, 2026** AI Memory ### AI Memory: teach Octolane about your business once Personalize every AI draft, field update, and report with workspace-wide memory. * New Settings , AI Memory page. Add facts about your ICP, tone, abbreviations, and product names * Memory blocks are referenced in every AI Chat answer and approval draft * Per-user memory layered on top of workspace memory **May 22, 2026** Signal ### Signal: ICP fit scoring v2 Reworked the buying-intent score to weight in account-level firmographics and historical win rates. * Score now factors in industry, headcount, and funding stage against your closed-won pattern * "Why this score" breakdown shows the exact signals that contributed **May 21, 2026** Bug fixes * Fixed duplicate contact creation when an email had both `to` and `cc` overlap * Fixed Calendar invites with no title showing as "Untitled" on the timeline * Fixed AI Chat losing context when switching between two records mid-conversation **May 20, 2026** Meeting Recorder ### Meeting recorder: speaker analytics Every recap now includes per-speaker talk time, with a visual timeline of who spoke when. * Click any segment on the timeline to jump to that moment * Talk-time ratio surfaced on the deal record as an AI field **May 19, 2026** Performance * 40% faster initial sync for new workspaces (median time-to-first-deal: 4.2 min , 2.5 min) * Pipeline view load time down from 1.8s to 0.6s on workspaces with 5,000+ opportunities **May 18, 2026** Pipelines * Drag and drop reordering of pipeline stages * Per-stage default probability that AI Chat uses for forecasts * Bulk move deals between stages from any view **May 15, 2026** MCP ### MCP: new tools for custom objects Custom objects are now fully exposed over MCP. Claude and Cursor can read, create, and update any custom object in your workspace. * `list_custom_objects`, `get_custom_object`, `create_custom_object_record`, `update_custom_object_record` * Automatic schema introspection so the AI knows your fields without you describing them **May 14, 2026** Bug fixes * Fixed Stripe integration occasionally double-counting MRR for annual subscriptions * Fixed AI field re-runs not honoring the manual-lock flag * Fixed Slack notifications going to wrong channel after workspace rename **May 13, 2026** AI Chat * AI Chat now streams partial answers for long queries instead of waiting for completion * Added `/forecast` slash command shortcut * Inline citations now show on hover instead of click **May 12, 2026** Approvals * Auto-approve thresholds are now per-action-type (field updates, drafts, stage changes, enrichment) * Bulk approve and bulk reject from any filter * Keyboard shortcuts `A` (approve next) and `R` (reject next) in the queue **May 11, 2026** Email ### Email templates and snippets Save and reuse email blocks across your team. Insert with `/` in the composer. * Variables auto-fill from the linked record: `{{contact.first_name}}`, `{{account.name}}` * Workspace-wide or personal templates **May 8, 2026** Bug fixes * Fixed Meeting Recorder occasionally joining cancelled meetings * Fixed enrichment timing out on companies with very long historical funding rounds * Fixed CSV import preview not respecting custom field order **May 7, 2026** Tasks * Recurring tasks (daily, weekly, custom cadence) * Snooze a task to a specific time of day, not just date * Tasks now surface in AI Chat: "What tasks do I have due today?" **May 6, 2026** Signal * First-party domain support: track traffic across multiple owned domains under one workspace * Better resolution for visitors behind corporate VPNs * New "returning visitors" filter **May 5, 2026** Migration ### Migration tools: HubSpot one-click import Connect HubSpot, pick what to bring, click go. We map Companies, Contacts, Deals, and Engagements into Accounts, Contacts, Opportunities, and Activities. * Pipeline stages map automatically * Custom properties become custom fields * Re-run anytime to pull deltas **May 4, 2026** Bug fixes * Fixed time zone display in meeting recaps for Europe/London users * Fixed Zapier triggers firing twice for stage changes via API * Fixed search not matching across custom field values **May 1, 2026** Reports * "Pin to dashboard" for any AI Chat-generated report * Scheduled email delivery for any saved report * Slack delivery for any saved report **April 30, 2026** Polish * Refreshed empty states across the app with clearer next-step CTAs * Improved color contrast on stage badges for accessibility * New keyboard shortcut hint overlay (`?` to open) **April 29, 2026** API * Added `/v1/opportunities/search` with full filter language support * Bumped default rate limits 5x for paying workspaces * New webhook event: `opportunity.stage_changed` **April 28, 2026** AI Fields * AI fields now show inline source citations on hover (which email / meeting / note) * One-click revert with "this was wrong" feedback. Octolane learns from corrections * Re-run all AI fields on a record from the right rail **April 27, 2026** Bug fixes * Fixed Calendar bot joining personal calendar events when only work account was connected * Fixed @mentions sometimes not notifying the tagged teammate * Fixed export CSV missing the last row on large datasets **April 24, 2026** Slack ### Slack app (beta) for Business plan Bring Octolane into Slack. * Ask AI Chat any question, get the answer in-thread * Create opportunities, tasks, and notes from Slack * Approve queued actions from the channel * `@octolane` mentions in any channel **April 23, 2026** Performance * Reduced AI Chat first-token latency from 1.4s to 0.7s * Cut webhook delivery time p95 from 2.1s to 0.4s **April 22, 2026** Pipelines ### Multiple pipelines Run sales, expansion, partnerships, and customer success in separate pipelines. * Each opportunity lives in exactly one pipeline at a time * Clone deals across pipelines (e.g. New Business , Expansion on renewal) * Per-pipeline forecast in AI Chat **April 21, 2026** Bug fixes * Fixed Gmail signature occasionally getting parsed as the email body * Fixed Signal script not initializing inside iframes * Fixed "no activity" filter excluding deals with only AI-generated activity **April 20, 2026** MCP * One-click install link for Claude Desktop * New `search_meetings` and `get_meeting_transcript` tools * Connection status indicator in workspace settings **April 17, 2026** Activity feed * Filter activity feed by type (email, meeting, note, AI action, stage change) * Pin any activity to keep it at the top * Date range filter on every timeline **April 16, 2026** Imports * CSV import now auto-detects 80% of column mappings, up from 60% * Preview now shows duplicate detection results before commit * Undo any import within 24 hours **April 15, 2026** Bug fixes * Fixed `/forecast` returning stale data after stage changes within the same session * Fixed contact dedupe merging across different domains in rare cases * Fixed CSV exports failing when a cell contained a literal `null` string **April 14, 2026** Meeting Recorder * Three new auto-record modes: All meetings, External only, Manually invite * Bot can be renamed per workspace * Meeting recap now includes a "next steps" section pushed into Tasks **April 13, 2026** Signal * New Leads view replaces the old Signal dashboard * Bulk add to outreach drafts from the Leads view * Visitor enrichment now includes browser, device, country, and tech stack **April 10, 2026** Polish * Sidebar groups now remember their collapsed state across sessions * Faster page transitions across the app * New onboarding tour for first-time workspaces **April 9, 2026** Bug fixes * Fixed AI Chat occasionally hallucinating opportunity amounts that didn't exist * Fixed Calendar permissions prompt looping after granting * Fixed Spanish, French, and German diacritics breaking search **April 8, 2026** API ### Webhooks v2 * 12 new event types covering every object lifecycle * HMAC-signed payloads * Replay any failed delivery from the dashboard **April 7, 2026** Custom Objects ### Custom objects (Team plan) Model anything beyond Accounts, Contacts, and Opportunities. Partners, Investors, Projects, Properties, Loans. * Full AI field support * Lookup relationships to standard or other custom objects * Full API and MCP access **April 3, 2026** Bug fixes * Fixed mobile sidebar getting stuck open after navigation * Fixed AI enrichment occasionally writing LinkedIn URL into the wrong field * Fixed search highlighting carrying over to the wrong record after switching **April 2, 2026** Forecasting ### Forecasting in AI Chat Ask AI Chat for a forecast and it weighs every deal using real conversation signals, not just stage averages. * Commit / best case / pipeline coverage * Per-rep, per-pipeline, per-segment slicing * "Why is this deal in commit?" explanation per row **April 1, 2026** AI Chat * AI Chat can now write to multiple records in one command ("update all deals in negotiation to add a follow-up task for Friday") * Undo any AI Chat action with `Cmd+Z` * History view to replay past AI Chat sessions **March 31, 2026** Performance * 60% reduction in memory usage for the meeting recorder bot * Faster enrichment fan-out (5x more concurrent enrichment jobs) **March 30, 2026** Bug fixes * Fixed AI Chat truncating long answers in the inline preview * Fixed mention notifications repeating after the same person is mentioned twice in a thread * Fixed time-on-page metric in Signal counting tab-out time **March 27, 2026** Views * Group by any field, including AI fields * Save views with a custom icon and color * Share view across the workspace with one click **March 26, 2026** Settings * Reorganized Settings into Profile, Workspace, Members, Integrations, Billing, AI * SAML SSO setup wizard (Business plan) * Audit log for workspace owner actions **March 25, 2026** Bug fixes * Fixed Gmail sync occasionally missing the latest message in a long thread * Fixed PostHog integration mapping events to wrong account when same person at two companies * Fixed account merge keeping the older logo instead of the better one **March 24, 2026** Email * Composer now drafts follow-ups with full conversation context, not just the last message * Send-later from the composer * Email open and reply tracking surfaced on the timeline **March 23, 2026** Notes * Notes now support full Markdown, including code blocks and tables * @mention any record (not just teammates) to link records inline * Edit history visible on hover **March 20, 2026** Bug fixes * Fixed onboarding flow occasionally hanging at the "enrichment" step * Fixed AI fields showing stale values after manual edit * Fixed Slack OAuth redirect failing for workspaces with custom subdomains **March 19, 2026** Polish * New empty states with example data * Streamlined onboarding from 12 steps to 6 * Better error messages across the app **March 18, 2026** Imports ### Salesforce and Pipedrive importers * Step-by-step migration wizard for both * Automatic field mapping with manual override * Idempotent re-runs to pull deltas during a side-by-side period **March 17, 2026** Approvals * "Reject with reason" so Octolane learns from corrections * Filter approval queue by action type and confidence * Daily digest email of queue size and oldest items **March 16, 2026** MCP * Per-tool permission scopes (read-only, read-write, full) * Connection tested every 60s with auto-reconnect * New `list_views` and `run_view` tools **March 13, 2026** Bug fixes * Fixed Calendar sync occasionally missing recurring meetings * Fixed AI Chat citing emails that had been deleted * Fixed search not indexing notes added in the last 60s **March 12, 2026** AI Chat * Faster response times for short queries (median 800ms , 400ms) * Added contextual examples when AI Chat opens on an empty input * Better handling of ambiguous account references ("Acme" when there are two) **March 11, 2026** MCP Server ### MCP Server: Use Octolane from Cursor, Claude & ChatGPT Launched Octolane MCP server. Interact with your CRM from any AI tool that supports MCP. * Supported tools: search deals, create contacts, update pipeline stages, add notes. All via natural language * Works with Cursor, Claude Desktop, and ChatGPT out of the box * Published quickstart guides for each platform **March 10, 2026** AI Chat ### AI Chat: Deep research mode AI Chat can now run multi-step research across your entire CRM before answering. * Ask complex questions like "Which deals have gone silent after a demo but before proposal stage in the last 30 days, and what was the last thing discussed?" * Results include source citations linking back to specific emails, meetings, and notes * 3x improvement in answer accuracy for cross-object queries **March 9, 2026** Pipeline ### Pipeline: Forecast confidence scores Every deal now has an AI-generated forecast confidence score (0–100) based on engagement signals, email sentiment, meeting frequency, and stage velocity. * Aggregate forecast view shows weighted pipeline by confidence band * Configurable thresholds for "at risk," "on track," and "strong" deals * Export forecast data to CSV for board reporting **March 8, 2026** Documentation ### Comparison docs & expanded documentation * Published full comparison pages: Octolane vs HubSpot, Salesforce, Attio, Pipedrive, and Lightfield * Expanded API reference documentation with interactive examples * Added custom `llms.txt` for better AI search discoverability **March 7, 2026** Follow-Up Agent ### Follow-Up Agent: Custom timing rules * You can now set per-pipeline timing rules for when the Follow-Up Agent drafts follow-ups (e.g., 3 days for hot deals, 2 weeks for enterprise) * Added "urgency" indicator to the approval queue so you can prioritize what to review first * Follow-Up Agent now respects timezone preferences. Drafts are timed to land during the recipient's working hours **March 6, 2026** AI Chat ### AI Chat improvements * AI Chat now understands multi-step instructions: "Find all stale deals over \$10K and draft follow-ups for each one" * Faster response times for pipeline queries. 2x speed improvement on large datasets * Added contextual suggestions. AI Chat now proactively suggests follow-up questions based on your query **March 5, 2026** Signal ### Signal: Page-level tracking Signal now shows exactly which pages a visiting company viewed. Not just that they visited your site. * New "Pages Viewed" column in the Signal dashboard with time-on-page data * Session replay links for high-value visitors (requires web analytics integration) * Page-level data feeds into ICP scoring. Pricing page visits boost the score **March 4, 2026** WhatsApp ### WhatsApp integration launched * Sync WhatsApp conversations into your CRM automatically * Deal Finder Agent now detects deals from WhatsApp threads * WhatsApp messages appear in the Activity Feed on contact and deal records * Two-way sync. Reply to WhatsApp messages directly from the deal record **March 3, 2026** Approval Queue ### Approval queue: Bulk actions * Approve, dismiss, or edit multiple agent actions at once from the approval queue * New keyboard shortcuts: `A` to approve, `D` to dismiss, `E` to edit * Added "Select all from this agent" for batch processing * Queue now shows estimated impact: "Approving these 12 follow-ups will re-engage \$340K in pipeline" **March 2, 2026** Outreach Agent ### Outreach Agent: A/B testing * Outreach Agent now supports A/B message variants. Define two approaches and let the agent alternate * Performance tracking per variant: open rates, reply rates, meeting booked rates * Winning variant auto-selected after statistical significance reached (configurable sample size) **March 1, 2026** AI Reporting ### AI Reporting: Ask anything * Ask AI Chat for any report in plain English: "Show me pipeline conversion rates by stage this quarter" * Reports now include visual charts alongside data tables * Save generated reports as dashboard widgets * Schedule recurring reports delivered to your inbox weekly or monthly **February 28, 2026** API ### Inbound API launched New REST API for pushing data into Octolane from any source. * Four endpoints: Create Opportunity, Create Account, Create Contact, Create Note * Automatic deduplication. Safe to call multiple times without creating duplicates * Published full API reference documentation with interactive playground * Rate limits: 1,000 requests/minute on Pro, 10,000 on Enterprise **February 27, 2026** Pipeline ### Pipeline: Deal health dashboard New dashboard showing overall pipeline health at a glance. * Metrics: average deal velocity, stage conversion rates, win rate trends, average deal size * Compare current month vs. previous month with trend indicators * Filterable by pipeline, owner, and time range **February 26, 2026** LinkedIn ### LinkedIn integration * Connect LinkedIn to enrich contacts with profile data, job titles, and company info * LinkedIn data now feeds into the Outreach Agent for more personalized messages * Mutual connections surfaced on contact records. Useful for warm intros * LinkedIn activity (posts, comments) tracked for key contacts **February 25, 2026** AI Fields ### Custom AI Fields Create fields that fill themselves in. Describe what you want to track in plain English and Octolane extracts it from your conversations. * Supports deal, contact, and company objects * Examples: budget range, buying timeline, competitor mentions, decision maker * AI Fields update automatically as new data comes in from emails and meetings **February 24, 2026** Follow-Up Agent ### Follow-Up Agent: Tone matching improvements * Improved voice matching. The Follow-Up Agent now better captures your email style, including greeting patterns, sign-offs, and sentence length * Added "Preview as sent" view in the approval queue * Side-by-side comparison: your original emails vs. agent-drafted follow-ups for calibration **February 23, 2026** Mobile ### Mobile: Push notifications * Push notifications now available on iOS and Android * Configurable notification types: agent actions pending, deal stage changes, Signal alerts, mentions * Deep links take you directly to the relevant record or approval queue item **February 22, 2026** AI Enrichment ### AI Enrichment: Decision maker mapping * Enrichment now identifies the buying committee at target accounts * Maps org chart relationships: who reports to whom, who influences purchase decisions * Automatic role classification: Champion, Decision Maker, Blocker, End User * Data sourced from LinkedIn, company websites, and public filings **February 21, 2026** Signal ### Signal: ICP scoring * Signal now scores every identified company against your ideal customer profile * High-priority visitors are flagged in the dashboard with match percentage * Configurable scoring criteria: company size, industry, location, tech stack * Score breakdown shows exactly why a company scored high or low **February 20, 2026** Onboarding ### Onboarding: Guided setup wizard * New step-by-step setup wizard for first-time users * Connect Gmail → Import contacts → Configure pipeline → Install Signal → Enable agents. All in under 10 minutes * Progress tracker in the sidebar until setup is complete * Contextual tips and sample data to help users understand each feature **February 19, 2026** Activity Feed ### Activity Feed: Agent action labels * Every agent action in the Activity Feed now shows which agent performed it and why * Filter the Activity Feed by agent type to see what each one has been doing * Activity Feed now includes a timeline view with visual markers for key events **February 18, 2026** Pipeline ### Pipeline: Auto-stage advancement * Deals can now automatically advance stages based on real signals. Meeting booked, proposal sent, contract discussed * Configurable per pipeline in Settings → Pipeline → Automation Rules * Audit log shows exactly which signal triggered each stage change * Manual override always available. Automation never blocks human judgment **February 17, 2026** Deal Finder ### Deal Finder: Confidence scoring * Deal Finder now assigns a confidence score to every detected deal * Low-confidence detections go to a "Review" queue instead of auto-creating * Configurable threshold: auto-create deals above 80% confidence, review below * Reduced false positive rate by 60% compared to previous version **February 16, 2026** Workspace ### Workspace: Team activity dashboard * New team dashboard showing activity across all workspace members * Metrics per rep: deals touched, emails sent, meetings held, follow-ups approved * Leaderboard view (optional) for competitive teams * Manager view with coaching insights: "Rep X has 5 deals with no activity in 7+ days" **February 15, 2026** Outreach Agent ### Outreach Agent launched New agent that drafts personalized outreach to qualified prospects identified by Signal or other agents. * Messages are personalized based on company profile, browsing behavior, and any existing interactions * All drafts go through your approval queue before sending * Supports email and LinkedIn InMail (with LinkedIn integration) **February 14, 2026** AI Notes ### AI Notes: Auto-summarize threads * AI Notes can now summarize entire email threads into a concise deal update * One-click "Summarize thread" button on any email conversation * Summaries are saved as notes on the deal record * Supports threads with 50+ messages. Compresses to key decisions and next steps **February 13, 2026** AI Enrichment ### AI Enrichment: Funding data * Contact and company enrichment now includes funding history, investors, and total raised * Data sourced from the live web. Not a static database * Funding stage classification: Pre-seed, Seed, Series A–E, Public * Revenue estimates for private companies based on employee count and funding **February 12, 2026** Email ### Email templates * Create reusable email templates for common outreach scenarios * Variable support: `{{first_name}}`, `{{company}}`, `{{deal_name}}`, and custom fields * Templates available in manual compose and as starting points for Outreach Agent * Shared template library across the workspace **February 11, 2026** Form Submission Agent ### Form Submission Agent launched * Captures every inbound form lead instantly * Qualifies leads against your ICP criteria automatically * Routes qualified leads to the right pipeline stage * Can trigger the Follow-Up Agent or Outreach Agent for immediate response * Supports Octolane forms, Typeform, and any webhook-compatible form tool **February 10, 2026** Search ### Search: Global search overhaul * Completely rebuilt global search. Now searches across deals, contacts, companies, notes, emails, and meetings simultaneously * Fuzzy matching handles typos and partial names * Search results ranked by relevance with context snippets * Keyboard shortcut: `Cmd+K` to open search from anywhere **February 9, 2026** Pricing ### 14-day free trial * Extended free trial from 7 days to 14 days on the Pro plan * No credit card required to start * Full access to all features including agents and Signal during trial * In-app onboarding checklist to help new users get value fast **February 8, 2026** Signal ### Signal: Slack notifications * Get Signal alerts directly in your Slack workspace * Configurable channels: send all alerts to #sales-leads, high-priority only to #hot-leads * Rich notifications include company name, ICP score, pages viewed, and a direct link to Octolane **February 7, 2026** Meeting Recorder ### Meeting Recorder: Action item extraction * Meeting Recorder now extracts specific action items from call transcripts * Action items are linked to the deal record and assigned to participants * Follow-Up Agent can monitor whether action items get addressed * Overdue action items surface in the "At Risk" deals view **February 6, 2026** Custom Data Model ### Custom Data Model: Relationships * Define custom relationships between any objects. Deals to deals, contacts to companies, custom objects to anything * Relationship types: parent-child, related, influenced-by * Relationship data feeds into AI context. Agents understand your full deal graph **February 5, 2026** Custom Data Model ### Custom Data Model: Custom objects * Create custom objects beyond deals, contacts, and companies * Define relationships between objects * Custom objects work with AI Fields and enrichment * Example custom objects: Products, Subscriptions, Support Tickets, Projects **February 4, 2026** Performance ### Performance: 3x faster load times * Complete frontend rewrite for pipeline and list views * Pipeline board loads in under 500ms for workspaces with 10K+ deals * Infinite scroll replaces pagination. Smoother browsing experience * Reduced memory usage by 40% on large datasets **February 3, 2026** Zapier ### Zapier integration expanded * New triggers: Deal stage changed, Signal company identified, Form submission received * New actions: Update deal stage, Add note to record * 12 total triggers and actions now available * Pre-built Zap templates for common workflows: "New Signal visitor → Slack notification" **February 2, 2026** Pipeline ### Pipeline: Multi-pipeline support * Create multiple pipelines for different sales motions (e.g., inbound vs. outbound, SMB vs. enterprise) * Each pipeline has independent stages, automation rules, and agent configurations * Cross-pipeline reporting for unified metrics * Drag deals between pipelines with stage mapping **February 1, 2026** Signal ### Signal: Google Tag Manager support * Install Signal via Google Tag Manager with one-click setup * No code changes needed. Just paste the tag ID * GTM template published in the GTM Community Gallery * Verified data parity with direct script installation **January 31, 2026** API ### API: Webhook events * Subscribe to real-time webhook events from Octolane * Supported events: deal.created, deal.updated, deal.stage_changed, contact.created, signal.company_identified * Retry logic with exponential backoff for failed deliveries * Webhook logs with request/response details for debugging **January 30, 2026** AI Chat ### AI Chat: Instruct agents via chat * You can now give instructions to agents through AI Chat * "Draft outreach to the last 5 companies that visited our pricing page" * "Follow up with everyone who hasn't replied in 2 weeks" * Agent actions from chat go through the same approval queue **January 29, 2026** Signal ### Signal: Industry detection * Signal now detects the industry of visiting companies automatically * Industry data feeds into ICP scoring. Boost scores for your target verticals * Filter Signal dashboard by industry to focus on relevant visitors * 95% accuracy across 150+ industry categories **January 28, 2026** Deal Finder ### Deal Finder: Multi-source detection * Deal Finder now scans connected web analytics, marketing tools, and support platforms. Not just email and calendar * Deals detected from support-to-sales handoffs and marketing engagement signals * Source attribution on every deal: which channel or interaction triggered detection * Consolidated deal view when multiple signals point to the same opportunity **January 27, 2026** Launch ### Never Miss a Deal launch * Major product launch on Product Hunt (#2 Product of the Day) and Bookface * New onboarding flow: connect Gmail + Calendar → see first auto-detected deal in under 5 minutes * Demo environment for prospects to try before signing up * 1,200+ signups in the first 48 hours **January 26, 2026** Import ### Import: Bulk data import * Upload CSV files with up to 100K records per import * Automatic column detection and field mapping * Duplicate detection during import with merge options * Import history with rollback capability for the first 24 hours **January 25, 2026** Meeting Notes ### AI Meeting Notes: Summary improvements * Meeting summaries now include key decisions, open questions, and sentiment indicators * Summaries are shorter and more actionable. Average 60% reduction in length with no loss of detail * New "Key Moments" feature highlights the most important parts of the call with timestamps **January 24, 2026** Outreach Agent ### Outreach Agent: Sequence support * Outreach Agent now supports multi-step sequences. Not just single messages * Define a sequence: Day 1 intro → Day 3 follow-up → Day 7 value-add → Day 14 break-up * Each step is personalized independently based on whether the prospect engaged with previous steps * Sequence performance dashboard with step-by-step conversion metrics **January 23, 2026** Signal ### Signal: Do-not-track list * Exclude specific domains or IP ranges from Signal tracking * Personal email domains (gmail.com, outlook.com) are excluded by default * Competitor domains can be excluded to keep data clean * Bulk import exclusion lists via CSV **January 22, 2026** AI Enrichment ### AI Enrichment: Social profiles * Enrichment now discovers and links social profiles: LinkedIn, Twitter/X, GitHub, personal websites * Social data feeds into contact records and is available to agents for personalization * Profile photos pulled automatically when available **January 21, 2026** Pipeline ### Pipeline: Stale deal indicators * Deals with no activity for a configurable period now show a visual "stale" indicator * Stale deals surface in a dedicated "At Risk" view * Follow-Up Agent can automatically trigger for stale deals * Weekly digest email summarizing all stale deals across your pipeline **January 20, 2026** Workspace ### Workspace: Audit log * Full audit log for workspace admin actions * Track who changed what: record edits, stage changes, agent configurations, user permissions * Filterable by user, action type, and date range * Exportable for compliance reporting **January 19, 2026** AI Enrichment ### AI Enrichment: Tech stack detection * Company enrichment now includes detected technology stack * See which tools your prospects use. CRM, marketing, analytics, etc. * Tech stack data feeds into ICP scoring and outreach personalization * 200+ technologies detected including competitors **January 18, 2026** Email ### Email: Tracking and analytics * Track email opens, link clicks, and reply rates for emails sent through Octolane * Per-email analytics visible on the deal record * Aggregate email performance dashboard for reps and managers * Open tracking pixel is invisible and privacy-respecting (no third-party data sharing) **January 17, 2026** Meeting Recorder ### Meeting Recorder: Zoom and Teams support * Meeting Recorder now supports Zoom and Microsoft Teams in addition to Google Meet * Auto-join works across all three platforms based on calendar events * Consistent transcription quality and summary format across all platforms * Calendar integration detects which platform each meeting uses automatically **January 16, 2026** Contacts ### Contact: Merge duplicates * Detect and merge duplicate contacts with one click * Smart matching based on email, name similarity, and company association * Merge preview shows which fields will be kept from each record * Activity history is combined. No data loss during merge **January 15, 2026** Views ### Views: Saved views * Save custom filtered views and access them from the sidebar * Share views with your team * Pre-built views: "My open deals," "Stale deals," "Hot leads this week" * Pin your most-used views to the top of the sidebar **January 14, 2026** Follow-Up Agent ### Follow-Up Agent: Multi-language support * Follow-Up Agent now drafts follow-ups in the same language as the original conversation * Supports 12 languages: English, Spanish, French, German, Portuguese, Italian, Dutch, Swedish, Danish, Norwegian, Japanese, Korean * Language detection is automatic. No configuration needed **January 13, 2026** Follow-Up Agent ### Follow-Up Agent: Subject line preservation * Follow-Up Agent now preserves the original email subject line when drafting follow-ups * Thread continuity maintained. Replies appear in the same conversation * Smart "Re:" prefix handling. No duplicate "Re: Re: Re:" chains **January 12, 2026** Pipeline ### Pipeline: Drag-and-drop reordering * Reorder deals within a pipeline stage by dragging * Custom sort order is saved per user * Sort by: manual order, deal size, last activity, close date, or AI confidence score **January 11, 2026** Accounts ### Accounts: Automatic merging * Octolane now detects when the same company enters your CRM from multiple sources and merges records automatically * Manual merge option also available for edge cases * Merge log shows history of all automatic merges for auditing * Undo merge available for 7 days after merge **January 10, 2026** Security ### Security: SOC 2 Type II * Achieved SOC 2 Type II compliance * Annual penetration testing by third-party security firm * All data encrypted at rest (AES-256) and in transit (TLS 1.3) * Security whitepaper available on request **January 9, 2026** AI Chat ### AI Chat launched Talk to your CRM in plain English. * Ask questions: "What's the latest with the Acme deal?" * Get summaries: "How many deals did we close this month?" * Available from the sidebar in every view * Supports follow-up questions with conversation memory **January 8, 2026** Pipeline ### Pipeline: Quick-edit from board view * Edit deal name, value, close date, and owner directly from the pipeline board. No need to open the deal page * Inline editing with auto-save * Bulk update deal owner for multiple deals at once **January 7, 2026** Signal ### Signal: Real-time notifications * Get notified instantly when a high-value company visits your website * Notifications via in-app alerts and email * Configurable thresholds: notify for Tier 1 ICP matches only, or all identified visitors * Notification digest option: batch alerts every 30 minutes instead of real-time **January 6, 2026** AI Notes ### AI Notes: Smart tagging * Notes are now automatically tagged with relevant topics: pricing, competition, timeline, technical requirements * Filter notes by tag to quickly find relevant context across all deals * Custom tags supported alongside auto-generated ones **January 5, 2026** Integrations ### Web analytics integration * Connect your web analytics tools to Octolane * See which pages prospects viewed, how they found you, and engagement metrics * Data feeds into Signal scoring and Deal Finder detection * Supports Google Analytics, Plausible, PostHog, and Mixpanel **January 4, 2026** Notifications ### Notifications: Notification center * New unified notification center accessible from the top bar * Categorized notifications: Agent Actions, Deal Updates, Signal Alerts, Team Activity * Mark all read, snooze, or mute notification types * Desktop notifications for time-sensitive alerts **January 3, 2026** Import ### Import: HubSpot and Salesforce field mapping * Improved CSV import with automatic field mapping for HubSpot and Salesforce exports * Custom fields are detected and can be created during import * Migration guide published for switching from HubSpot or Salesforce * Data validation during import catches formatting issues before records are created **January 2, 2026** Performance ### Performance: API response times * Reduced median API response time from 320ms to 95ms * Optimized database queries for pipeline and search endpoints * Added edge caching for frequently accessed resources * Published status page at status.octolane.com **January 1, 2026** Year in Review ### 2025 year in review * Shipped 180+ features in 2025 * Grew from 0 to 2,400+ active workspaces * Processed 12M+ emails and 850K+ calendar events * Agents drafted 420K+ follow-ups and detected 95K+ deals automatically **December 31, 2025** AI Enrichment ### AI Enrichment: Refresh scheduling * Schedule automatic enrichment refreshes. Daily, weekly, or monthly * Only changed data triggers updates. No unnecessary API calls * Enrichment changelog shows what changed and when * Manual refresh available for any record with one click **December 30, 2025** Meeting Recorder ### Meeting Recorder launched * Built-in meeting recorder that joins Google Meet calls automatically * Full transcription with speaker labels * AI-generated meeting summaries with next steps * Recordings stored securely with team-level access controls **December 29, 2025** Pipeline ### Pipeline: Close date tracking * Close date field now tracks history. See how many times a deal's close date was pushed * "Slippage" indicator shows deals that have been pushed 3+ times * Close date change triggers are available as automation inputs **December 28, 2025** AI Chat ### AI Chat: Context-aware responses * AI Chat now considers the page you're on when answering questions * Ask "How is this deal going?" from a deal page. No need to specify which deal * Responses include links to related records for easy navigation **December 27, 2025** Signal ### Signal Agent launched * Identify companies visiting your website in real-time * Company enrichment for every identified visitor * Qualification scoring against your ideal customer profile * One-click "Create Deal" from any identified visitor **December 26, 2025** Contacts ### Contact: Automatic creation from email * Contacts are now created automatically when new email addresses appear in synced conversations * Contacts are linked to the correct company using domain matching * Duplicate prevention checks run before creation * New contacts appear in the Activity Feed with source attribution **December 25, 2025** Deals ### Deal record: Related contacts view * Deal pages now show all related contacts with their role and engagement level * Engagement level is calculated from email and meeting frequency * Add or remove contacts from a deal with one click * Contact roles: Primary, Technical, Executive Sponsor, Procurement **December 24, 2025** Follow-Up Agent ### Follow-Up Agent: Voice learning * Follow-Up Agent now learns your writing style from your sent emails * Matches your tone, greeting patterns, and sign-off style * Better voice matching with every email you send * Voice profile is private to each user. Not shared across the workspace **December 23, 2025** Workspace ### Workspace: Invite teammates * Invite team members by email with role-based access * Roles: Admin, Manager, Member, Viewer * Pending invitations visible in workspace settings * SSO support for Google Workspace accounts **December 22, 2025** Pipeline ### Pipeline: Deal value tracking * Track one-time and recurring revenue (ARR/MRR) per deal * Pipeline totals update in real-time on the board view * Currency support: USD, EUR, GBP, and 20+ currencies * Multi-currency deals with automatic conversion at current rates **December 21, 2025** Pipeline ### Pipeline: Custom stages * Customize your pipeline stages to match how your team actually sells * Drag-and-drop reordering * Default stages provided for quick setup * Stage-level probability settings for forecasting **December 20, 2025** Email ### Email sync: Thread grouping * Emails are now grouped into threads on deal and contact records * Thread view shows the full conversation with newest messages on top * Collapsed view for long threads. Expand individual messages as needed * Thread-level actions: summarize, create note, flag for follow-up **December 19, 2025** Calendar ### Calendar sync: Meeting detection * Calendar events with external participants are automatically detected as meetings * Meeting records include attendees, agenda (from event description), and linked deal * Pre-meeting brief: AI Chat can summarize everything you know about the attendees and their company **December 18, 2025** AI Enrichment ### AI Enrichment launched * Automatic enrichment for every contact and company * Data sourced from the live web. Job titles, company size, social profiles, location * Refreshes periodically to keep records current * 92% fill rate for job title, 88% for company size, 85% for location **December 17, 2025** Gmail ### Gmail sync: Two-way sync * Emails sent from Octolane now appear in your Gmail sent folder * Full two-way sync. No parallel universe of emails * BCC and CC recipients captured on synced emails * Attachment previews visible on deal records **December 16, 2025** Search ### Search: Quick filters * Filter deals, contacts, and companies without leaving the list view * Quick filter chips: stage, owner, value range, created date, last activity * Combine multiple filters with AND/OR logic * Filter state is saved in the URL. Shareable with teammates **December 15, 2025** Deal Finder ### Deal Finder Agent launched * Scans your email and calendar to detect deals automatically * Creates opportunities in your pipeline with associated contacts and context * Deduplication built in. Same deal from multiple signals won't create duplicates * Detection accuracy: 94% precision on real user data during beta **December 14, 2025** Activity Feed ### Activity Feed: Email and meeting timeline * Activity Feed shows all emails and meetings in chronological order * Filter by: emails only, meetings only, agent actions, notes * Expandable email previews. Read the full email without leaving the deal page * Quick reply button to respond to emails directly from the Activity Feed **December 13, 2025** Contacts ### Contacts: Bulk import * Import contacts from CSV with automatic field mapping * Duplicate detection with configurable matching rules (email, name, phone) * Import preview: review matched fields and sample records before confirming * Import history with row-level success/error reporting **December 12, 2025** Follow-Up Agent ### Follow-Up Agent launched * Monitors active conversations for stale threads * Drafts follow-up emails in your voice * One-tap approval from the approval queue * Nothing sends without your permission * Average time saved per user: 45 minutes/day during beta **December 11, 2025** Deals ### Deal page: Activity timeline * Complete timeline of all deal activity. Emails, meetings, notes, stage changes, agent actions * Pinnable events for important milestones * Timeline is the default view when opening a deal **December 10, 2025** Gmail ### Multi-inbox support * Connect multiple Gmail accounts to a single Octolane workspace * All accounts feed into the same unified CRM * Per-account visibility settings * Choose which account to send from when composing **December 9, 2025** Gmail ### Gmail sync launched * Connect your Gmail account with one click via OAuth * Emails are synced in real-time. New messages appear within seconds * Historical sync: imports the last 90 days of email on first connect * Privacy-first: only emails with external participants are synced (internal emails are ignored) **December 8, 2025** Approval Queue ### Approval queue launched * Central queue for reviewing all agent actions * Approve, edit, or dismiss with one tap * Notification badges for pending items * Action preview shows exactly what will happen when you approve Follow us on [X](https://x.com/octolane) and [LinkedIn](https://www.linkedin.com/company/octolane) for real-time announcements. # MCP Authentication Source: https://octolane.com/docs/mcp/authentication Connect with OAuth or a personal API key, using the connected member's workspace permissions. Octolane MCP supports **OAuth 2.0** and **API keys**. The hosted endpoint is `https://mcp.octolane.com/mcp`, using Streamable HTTP. MCP access is included on every [Octolane plan](/docs/account/plans-pricing). ## OAuth Use OAuth for clients that offer an interactive connection flow. Add the server URL, review the requested access, then enter your personal Octolane API key on the Octolane authorization page. Create the key in [Settings → API keys](https://www.octolane.com/settings/api-keys) first. The client handles the authorization-code flow with PKCE and sends the resulting bearer token. Enter credentials only on Octolane’s authorization page, never in the AI conversation. If authorization expires or the key is revoked, reconnect using an active key. The server publishes its current configuration at: * [MCP discovery](https://www.octolane.com/.well-known/mcp.json) * [Protected resource metadata](https://mcp.octolane.com/.well-known/oauth-protected-resource) * [Authorization server metadata](https://mcp.octolane.com/.well-known/oauth-authorization-server) The authorization server advertises these scopes: | Scope | Access | | - | - | | `crm:read` | Read CRM data within the connected member's access | | `crm:write` | Write CRM data within the connected member's access | Use the live metadata for authorization endpoints and supported registration methods. These are advertised scope names, not a documented way to create a read-only API key. Treat a connected key as capable of writes within its member’s access. Scopes do not bypass workspace permissions or plan entitlements. ## Personal API keys Create a key in [Settings → API keys](https://www.octolane.com/settings/api-keys). The same personal key works with the REST API and MCP. For clients that accept custom headers, send: ```http theme={"system"} Authorization: Bearer YOUR_OCTOLANE_API_KEY ``` For example, a client supporting the following remote-server configuration can use: ```json theme={"system"} { "mcpServers": { "octolane": { "url": "https://mcp.octolane.com/mcp", "headers": { "Authorization": "Bearer YOUR_OCTOLANE_API_KEY" } } } } ``` MCP uses the `Authorization` bearer header. The REST API at `api.octolane.com` uses `x-api-key`; the headers are not interchangeable. An MCP request with only `X-API-Key` returns `401` with “Missing Authorization header”. Configuration formats vary by client. Use the [Claude](/docs/mcp/use-with-claude), [ChatGPT](/docs/mcp/use-with-chatgpt), or [Cursor](/docs/mcp/use-with-cursor) guide. ChatGPT uses OAuth for this connection. ## Permissions and revocation Requests act with the connected person's workspace permissions. Personal API keys use their creator's current access and stop working when disabled or when the creator leaves the workspace. They do not grant unrestricted access to every record or administrative action. Store keys in your client's credential settings or supported environment-variable configuration. Do not put real keys in shared source files. Revoke exposed or unused keys from [API-key settings](https://www.octolane.com/settings/api-keys). ## Rate limits Handle `429 Too Many Requests`, following `Retry-After` when supplied and backing off before retrying. MCP-specific numeric limits are not published in the discovery metadata. Do not assume that REST route quotas apply to every MCP tool. Contact [help@octolane.com](mailto:help@octolane.com) for workspace-specific limits. ## Troubleshooting | Symptom | Check | | - | - | | `401 Unauthorized` | Reconnect OAuth or check that the API key is active and supplied without extra whitespace. | | Permission denied | Confirm the connected member can access the record and perform the operation. | | No tools appear | Confirm the endpoint includes `/mcp`, the client supports Streamable HTTP, authentication completed, and the connection is enabled. Refresh the client's tool list. | | `429 Too Many Requests` | Follow the response's retry guidance and reduce request frequency. | Opening the MCP URL in an unauthenticated browser may return `401`; that alone does not indicate an outage. # MCP Examples & Workflows Source: https://octolane.com/docs/mcp/examples Real-world examples of using Octolane MCP to run your sales process from any AI assistant - from morning pipeline reviews to end-of-day follow-up approvals. These illustrative workflows show prompts, possible tool sequences, and sample outputs. Names, amounts, dates, and company details are examples, not live customer data or Octolane pricing. Discover the current tool schemas before use and report only results returned by the connected workspace. External writes use the connected member's permissions and may apply directly. Enrichment and automation depend on plan limits and configuration; sample outputs do not guarantee that those steps run. See [Octolane for AI agents](/docs/get-started/agents). *** ## 1. Morning pipeline review Start your day with a complete picture of your pipeline without opening the Octolane dashboard. **Prompt:** ``` Show me our pipeline overview. Which deals are stale? What's gone quiet in the last 2 weeks? ``` **What Octolane does behind the scenes:** 1. Calls `get_pipeline_overview` to get the pipeline summary with deal counts and values per stage 2. Calls `find_stale_deals` with `days: 14` to find stale deals 3. Presents both in a combined view **What you get back:** > **Pipeline: Sales** > > | Stage | Deals | Total Value | Avg Size | > | - | - | - | - | > | New Lead | 8 | \$156K | \$19.5K | > | Meeting Scheduled | 5 | \$210K | \$42K | > | Proposal | 4 | \$185K | \$46.3K | > | Negotiation | 3 | \$196K | \$65.3K | > | Closed-Won | 3 | \$100K | \$33.3K | > > **Stale deals (no activity in 14+ days):** > > * Notion Annual - \$85K - Proposal - 14 days stale > * Figma Team - \$42K - Meeting Scheduled - 16 days stale > * Vercel Startup Plan - \$11K - New Lead - 18 days stale *** ## 2. Website visitor intelligence See who's checking out your site and act on it immediately. **Prompt:** ``` What companies visited our site recently? Show me the top ones with their details. Do we already have any contacts or deals with them? ``` **What Octolane does behind the scenes:** 1. Calls `get_signal_visitors` to get recent visitors with intent scores 2. For the top matches, calls `search_accounts` and `search_contacts` to check for existing records 3. Compiles a combined view with enrichment data **What you get back:** > **Recent website visitors:** > > **1. Linear** (linear.app) > > * Intent score: 94 | 4 visits this week > * 120 employees, Developer Tools, Series B (\$52M raised) > * No existing contacts or deals > * *High intent - multiple visits* > > **2. Ramp** (ramp.com) > > * Intent score: 87 | 2 visits > * 800 employees, Fintech, Series D (\$750M raised) > * Existing contact: Jake Morrison ([jake@ramp.com](mailto:jake@ramp.com)) - no active deal > > **3. Retool** (retool.com) > > * Intent score: 82 | 3 visits > * 450 employees, Developer Tools, Series C (\$45M raised) > * No existing contacts or deals > > Want me to create accounts and deals for any of these? *** ## 3. Meeting prep Pull up everything you need before a call without clicking through 5 different CRM pages. **Prompt:** ``` I have a call with Stripe tomorrow. Pull up everything we know about them - the deal status, all contacts, recent emails, and any notes or tasks. ``` **What Octolane does behind the scenes:** 1. Calls `search_accounts` with `query: "Stripe"` to find the account 2. Calls `search_deals` with `account_name: "Stripe"` to get active deals 3. Calls `get_deal_details` on the active deal for full context 4. Calls `search_emails` with `account_domain: "stripe.com"` for recent correspondence 5. Calls `get_notes` with `account_name: "Stripe"` for logged notes 6. Calls `get_tasks` for open tasks linked to the deal **What you get back:** > **Stripe - Enterprise Plan** > > * **Stage:** Negotiation | **Value:** \$120K | **Close date:** April 15 > * **Owner:** Sarah (you) | **Next steps:** Send SOC 2 report > > **Contacts:** > > * Sarah Chen, VP of Sales ([sarah@stripe.com](mailto:sarah@stripe.com)) - primary contact > * David Park, Head of RevOps ([david@stripe.com](mailto:david@stripe.com)) - technical evaluator > * Lisa Wu, Procurement ([lisa@stripe.com](mailto:lisa@stripe.com)) - CC'd on contract thread > > **Recent emails:** > > * Mar 6: From Sarah Chen - "Need SOC 2 report before procurement can sign off" > * Mar 4: To Sarah Chen - Pricing follow-up after meeting > * Mar 1: To Sarah Chen - Proposal sent (\$120K/yr for 50 seats) > > **Notes:** > > * Mar 4: "Meeting notes - discussed custom pricing, David wants SSO included" > * Feb 27: "Demo call - David asked about API access and webhooks" > > **Open tasks:** > > * Send SOC 2 report to Lisa Wu (High priority, due Apr 10) > * Share API docs with David Park (Medium priority) *** ## 4. Deal creation flow Create a deal with all the linked records in one conversation. **Prompt:** ``` Just had a great call with the CTO of Linear. Create a deal - $65K annual contract, meeting scheduled stage. Main contact is karri@linear.app. Add a note with the call summary. ``` **What Octolane does behind the scenes:** 1. Calls `create_account` with `domain: "linear.app"` if needed 2. Calls `create_contact` with `email: "karri@linear.app"` if needed 3. Calls `get_pipeline_overview` to get the pipeline ID 4. Calls `list_pipeline_stages` to find the "Meeting Scheduled" stage ID 5. Calls `create_deal` with all the details 6. Calls `create_note` linked to the new deal **What you get back:** > **Created:** > > * Account: Linear (linear.app) > * Contact: [karri@linear.app](mailto:karri@linear.app) > * Deal: "Linear - Annual Contract" - \$65K - Meeting Scheduled > * Note: Call summary logged on the deal > > Verify the linked records and any configured follow-up workflow. Report enrichment only if its result is available. *** ## 5. Email and meeting history Look up your communication history with any contact or company. **Prompt:** ``` Show me all emails and meetings with Notion in the last month. What was the last thing we discussed? ``` **What Octolane does behind the scenes:** 1. Calls `search_emails` with `account_domain: "notion.so"` to find email threads 2. Calls `search_meetings` with `query: "Notion"` to find meeting records 3. Combines and sorts by date **What you get back:** > **Emails with Notion (last 30 days):** > > * Mar 6: To [sarah@notion.so](mailto:sarah@notion.so) - Proposal follow-up (no reply) > * Feb 22: From [sarah@notion.so](mailto:sarah@notion.so) - "Looks good, let me loop in procurement" > * Feb 20: To [sarah@notion.so](mailto:sarah@notion.so) - Proposal sent (\$85K annual) > > **Meetings:** > > * Feb 18: Discovery call with Sarah - 30 min > Summary: Discussed pain points with current CRM, interested in AI features > > **Last interaction:** Proposal follow-up email on Mar 6 - no reply in 8 days. This deal may need attention. *** ## 6. Task management Manage your follow-ups and action items from your AI assistant. **Prompt:** ``` What tasks do I have open? Show me what's overdue and what's coming up this week. Mark the Stripe SOC 2 task as done. ``` **What Octolane does behind the scenes:** 1. Calls `get_tasks` to get all open tasks 2. Filters by due date for overdue and this-week buckets 3. Calls `update_task` with `completed: true` on the SOC 2 task **What you get back:** > **Overdue (2):** > > * Share API docs with David Park (Stripe) - due Apr 8 - Medium > * Follow up with Notion on proposal - due Apr 10 - High > > **This week (3):** > > * Schedule demo with Linear - due Apr 16 - Medium > * Send case study to Ramp - due Apr 17 - Low > * Review Retool pricing proposal - due Apr 18 - High > > **Done:** Marked "Send SOC 2 report to Stripe" as complete. *** ## 7. Stale deal sweep Find deals that need attention and take action. **Prompt:** ``` Show me all deals that haven't had any activity in 2 weeks. For each one, show the last email and create a follow-up task. ``` **What Octolane does behind the scenes:** 1. Calls `find_stale_deals` with `days: 14` 2. For each stale deal, calls `search_emails` with the account domain to find the last email 3. Calls `create_task` for each stale deal with a follow-up reminder **What you get back:** > **3 stale deals (no activity in 14+ days):** > > **1. Notion Annual - \$85K - Proposal** > > * Last email: Mar 6 - Proposal follow-up (no reply, 38 days ago) > * Task created: "Follow up with Notion on proposal" - due tomorrow - High > > **2. Figma Team - \$42K - Meeting Scheduled** > > * Last email: Mar 2 - Meeting confirmation (cancelled, never rescheduled) > * Task created: "Reschedule meeting with Figma" - due tomorrow - High > > **3. Vercel Startup - \$11K - New Lead** > > * Last email: Feb 25 - Intro email (no reply, 47 days ago) > * Task created: "Re-engage Vercel or close as lost" - due tomorrow - Medium # Octolane MCP Server Source: https://octolane.com/docs/mcp/overview Let AI agents read and update your CRM and query company knowledge through Octolane's hosted MCP server. Octolane is a self-driving AI CRM built for agents and humans. Its hosted MCP server lets external assistants work with CRM records, conversations, tasks, pipeline data, website visitor signals, and the company brain using the connected person's workspace permissions. MCP, the REST API, and webhooks are included on every plan. [Feature entitlements and usage limits](/docs/account/plans-pricing) still apply. ## Connection | Setting | Value | | - | - | | Server URL | `https://mcp.octolane.com/mcp` | | Transport | Streamable HTTP | | Authentication | OAuth 2.0, or `Authorization: Bearer YOUR_OCTOLANE_API_KEY` in clients that support custom headers | | Personal API keys | [Settings → API keys](https://www.octolane.com/settings/api-keys) | | Discovery | [MCP metadata](https://www.octolane.com/.well-known/mcp.json) | Start with the [quickstart](/docs/mcp/quickstart) and [authentication guide](/docs/mcp/authentication). No local Octolane server is required. ## Workflows * Search accounts, contacts, deals, emails, and meetings to understand customer context. * Create or update records, notes, and tasks within the connected user's access. * Review pipeline stages and opportunity values. * Inspect company-level website visitor signals. * Query the [company brain](/docs/ai/company-brain) for what your team has learned. Enrichment and automation follow workspace configuration, plan entitlements, and remaining usage. Creating a record does not bypass those limits. ## Tool discovery Use MCP `tools/list` for the current tool names and input schemas. The [tools reference](/docs/mcp/tools-reference) describes common tools and examples; do not assume a fixed tool count or infer undocumented names for company-knowledge queries. MCP and REST are separate interfaces. Their parameter names, supported operations, and date formats may differ. Use the connected MCP schema for tools and the [OpenAPI specification](https://www.octolane.com/openapi.json) for REST calls. ## Clients | Client | Setup | | - | - | | Claude web and Desktop | [Use with Claude](/docs/mcp/use-with-claude) | | ChatGPT | [Use with ChatGPT](/docs/mcp/use-with-chatgpt) | | Cursor | [Use with Cursor](/docs/mcp/use-with-cursor) | | Grok Bot, Slack, and other MCP clients | [Connection details](/docs/mcp/quickstart); use the client's supported remote-MCP settings | Client availability and administrator policies can differ. Octolane's built-in [Slack agent](/docs/tools/slack) is also available on every plan; Slack conversation sync is a separate Team/Enterprise capability. ## Read the docs as an agent See [Octolane for AI agents](/docs/get-started/agents) for the documentation index, full text, API catalog, and a workflow for discovering tools and verifying results. # MCP Quickstart Source: https://octolane.com/docs/mcp/quickstart Connect an authorized AI client to Octolane over Streamable HTTP using OAuth or an API key. Use Octolane from Claude, ChatGPT, Cursor, Grok Bot, Slack, or another compatible MCP client. Every Octolane plan includes MCP; the client's own availability and workspace policies also apply. ## Before you begin A person must have an Octolane workspace and authorize the connection. New users can [start the 7-day Founder trial](https://www.octolane.com/auth/sign-up). Connect Gmail and Google Calendar in Octolane to populate conversation history. See [human setup](/docs/get-started/quickstart) or the [agent guide](/docs/get-started/agents). **1. Add the hosted server** Use `https://mcp.octolane.com/mcp` with **Streamable HTTP**. No local Octolane server is required. Follow your client's setup guide: [Claude](/docs/mcp/use-with-claude), [ChatGPT](/docs/mcp/use-with-chatgpt), or [Cursor](/docs/mcp/use-with-cursor). For other clients, use their supported remote-MCP connection settings. **2. Authenticate** Choose **OAuth** and enter your personal API key on Octolane’s authorization page, or send the key directly from [Settings → API keys](https://www.octolane.com/settings/api-keys) in the `Authorization` header as `Bearer YOUR_OCTOLANE_API_KEY` if your client supports it. See [Authentication](/docs/mcp/authentication). **3. Discover and verify** Enable the connection and refresh its tools. Ask: “What Octolane tools are available, and which workspace am I connected to?” A custom MCP client uses `tools/list` to discover the current schemas. Use `get_current_user` when available to check identity. **4. Read your first records** Ask: “Show my open deals and their next steps.” Verify one result against the record in Octolane. An empty result can mean the workspace has no matching records or your account lacks access. ## Try a workflow * “Summarize pipeline value by stage.” * “Find my open tasks for this week.” * “Draft a follow-up for Acme using our last meeting.” * “What does our company brain say about common buyer objections?” Before requesting writes, check the target record and desired change. API and MCP tools can apply changes directly; the in-app approval queue is not a blanket confirmation step for external tools. Verify completed changes in Octolane. Records created through MCP participate in workspace workflows. Enrichment depends on your plan and remaining credits, and automations depend on configuration and run limits. ## Next steps * [Tools reference](/docs/mcp/tools-reference): documented tools and examples; discover the live schema when connecting. * [Examples and workflows](/docs/mcp/examples): pipeline reviews, meeting preparation, and record updates. * [Company brain](/docs/ai/company-brain): shared knowledge for your team and agents. # MCP Tools Reference Source: https://octolane.com/docs/mcp/tools-reference Reference for documented Octolane MCP tools, with parameters, examples, and guidance for discovering the current server schema. This reference describes common Octolane MCP tools by category. On connection, use `tools/list` to discover the current tools and input schemas. Tool availability can depend on your access and the server version. Company-brain queries use `memory_list` and `memory_get`; confirm their schemas with the connected server. See [Company brain](/docs/ai/company-brain). > [!NOTE] > > Connect to `https://mcp.octolane.com/mcp` over Streamable HTTP using OAuth or a personal API key in `Authorization: Bearer YOUR_OCTOLANE_API_KEY`. Requests use the connected member's permissions. See [Authentication](/docs/mcp/authentication). *** Examples use illustrative names, dates, and IDs. Replace IDs with values returned by your workspace and follow the discovered tool schema; MCP arguments can differ from REST inputs. ## Search & Query Tools for finding and retrieving data from your CRM. ### `search_deals` Search deals with filters for pipeline, stage, account, contact, deal size, and close date. Use `find_stale_deals` for activity or stage staleness. **Parameters** **keywords** `string[]` Up to 10 name terms, matched with OR. Use for several records in one call. **search_query** `string` Search by deal/opportunity name. **pipeline_name** `string` Filter by pipeline name (e.g., "Sales"). **stage_name** `string` Filter by stage name (e.g., "Negotiation", "Won"). **account_name** `string` Filter by associated company/account name. **contact_name** `string` Filter by associated contact name. **min_amount** `number` Minimum deal value. **max_amount** `number` Maximum deal value. **close_date_from** `string` First included calendar date, `YYYY-MM-DD`, in the user’s calendar. **close_date_to** `string` Last included calendar date, `YYYY-MM-DD`, in the user’s calendar. **limit** `integer` Maximum results to return. Defaults to 10, max 50. **offset** `integer` Zero-based row offset, default 0. Increase by the number returned until the reported total is reached. **Example** **Prompt:** "Show deals worth at least \$50K" **Tool call:** ```json theme={"system"} { "tool": "search_deals", "arguments": { "min_amount": 50000 } } ``` *** ### `search_contacts` Search contacts by name, email, company, or job title. **Parameters** **keywords** `string[]` Up to 10 name terms, matched with OR. Use for several records in one call. **query** `string` Search by contact name or email. **company_name** `string` Filter by company name. **job_title** `string` Filter by job title. **limit** `integer` Maximum results to return. Defaults to 10, max 50. **offset** `integer` Zero-based row offset, default 0. Increase by the number returned until the reported total is reached. **Example** **Prompt:** "Find all contacts at Stripe" **Tool call:** ```json theme={"system"} { "tool": "search_contacts", "arguments": { "company_name": "Stripe" } } ``` *** ### `search_accounts` Search accounts (companies) by name, domain, or industry. **Parameters** **keywords** `string[]` Up to 10 name terms, matched with OR. Use for several records in one call. **query** `string` Search by company name or domain. **domain** `string` Filter by company domain. **industry** `string` Filter by industry. **limit** `integer` Maximum results to return. Defaults to 10, max 50. **offset** `integer` Zero-based row offset, default 0. Increase by the number returned until the reported total is reached. **Example** **Prompt:** "Find SaaS companies in our CRM" **Tool call:** ```json theme={"system"} { "tool": "search_accounts", "arguments": { "industry": "SaaS" } } ``` *** ### `search_emails` Search email conversations by contact, company domain, keyword, or direction. **Parameters** **contact_email** `string` Search emails involving this email address. **account_domain** `string` Search emails involving this company domain. **search_query** `string` Search by email subject or content. **label** `string` Filter by direction: `sent`, `inbox`, or `all`. Defaults to `all`. **limit** `integer` Maximum results to return. Defaults to 10, max 25. **Example** **Prompt:** "Show me all emails we've sent to Stripe" **Tool call:** ```json theme={"system"} { "tool": "search_emails", "arguments": { "account_domain": "stripe.com", "label": "sent" } } ``` *** ### `search_meetings` Search past and upcoming meetings by keyword, attendee, or date range. **Parameters** **query** `string` Search keywords for meeting title, summary, transcript, or attendee. Omit for purely temporal queries like "my next meeting". **start_date** `string` Start of date range (ISO 8601). **end_date** `string` End of date range (ISO 8601). **sort** `string` Sort order for start_time: `asc` for upcoming, `desc` for recent. Defaults to `desc`. **limit** `integer` Maximum results to return. Defaults to 10, max 25. **Example** **Prompt:** "What meetings do I have this week?" **Tool call:** ```json theme={"system"} { "tool": "search_meetings", "arguments": { "start_date": "2026-11-16T00:00:00-08:00", "end_date": "2026-11-23T00:00:00-08:00", "sort": "asc" } } ``` *** ### `get_deal_details` Get full details of a specific deal including associated contacts, account, notes, tasks, and next steps. **Parameters** **opportunity_id** `string` *required* The deal/opportunity ID. Use `search_deals` to find it. **Example** **Prompt:** "Pull up the Stripe deal" First call `search_deals` with `search_query: "Stripe"` to get the ID, then: ```json theme={"system"} { "tool": "get_deal_details", "arguments": { "opportunity_id": "11111111-1111-4111-8111-111111111111" } } ``` Returns deal details, current stage, value, close date, all associated contacts, notes, tasks, and next steps. *** ### `get_pipeline_overview` Get a summary of your sales pipeline(s) showing deal counts, total values, and average deal size by stage. **Parameters** **pipeline_name** `string` Filter by pipeline name. Omit to see all pipelines. **Example** **Prompt:** "What's our pipeline look like?" **Tool call:** ```json theme={"system"} { "tool": "get_pipeline_overview", "arguments": {} } ``` Returns pipeline ID, name, and breakdown by stage with deal counts, total values, and average deal size. *** ### `get_signal_visitors` Retrieve website visitors identified by Octolane Signal with visit counts, intent scores, and activity dates. **Parameters** **search_query** `string` Search by company name or domain. **page** `integer` Page number for pagination. Defaults to 1. **limit** `integer` Results per page. Defaults to 10, max 50. **Example** **Prompt:** "What companies have been visiting our site?" **Tool call:** ```json theme={"system"} { "tool": "get_signal_visitors", "arguments": { "limit": 20 } } ``` Returns companies with visit counts, intent scores, and activity dates. *** ### `get_email_thread` Get the full email thread conversation by thread ID. **Parameters** **thread_id** `string` *required* The email thread ID. Get this from `search_emails` results. *** ### `get_notes` Search and retrieve notes linked to a deal, contact, or account. Supports lookup by name, email, or domain. No ID required. **Parameters** **entity_id** `string` Direct entity UUID (deal, contact, or account). **account_name** `string` Find notes by company name. **account_domain** `string` Find notes by company domain. **contact_name** `string` Find notes by contact name. **contact_email** `string` Find notes by contact email. **limit** `integer` Maximum results. Defaults to 10, max 50. **offset** `integer` Zero-based row offset, default 0. Increase by the number returned until the reported total is reached. **Example** **Prompt:** "Show me all notes on the Stripe account" **Tool call:** ```json theme={"system"} { "tool": "get_notes", "arguments": { "account_name": "Stripe" } } ``` *** ### `get_tasks` Get tasks assigned to you or linked to a specific deal, contact, or account. **Parameters** **scope** `string` `self` or `team`. Defaults to your tasks unless a linked record is supplied. Team results follow workspace permissions. **assignee_id** `string` User UUID from `list_workspace_members`. Do not combine another user with `scope: self`. **status** `string` `open`, `completed`, or `all`. Overrides `include_completed` when provided. **due_before** `string` Exclusive upper bound as a UTC ISO timestamp. **due_on_or_after** `string` Inclusive lower bound as a UTC ISO timestamp. **entity_id** `string` Get tasks linked to this entity UUID. **entity_type** `string` Type of entity: `account`, `contact`, or `opportunity`. Required when `entity_id` is provided. **include_completed** `boolean` Include completed tasks. Defaults to false. **limit** `integer` Maximum results. Defaults to 15, max 50. **offset** `integer` Zero-based row offset, default 0. Increase by the number returned until the reported total is reached. **Example** **Prompt:** "What are my open tasks?" **Tool call:** ```json theme={"system"} { "tool": "get_tasks", "arguments": {} } ``` *** ### `get_current_user` Get your identity, workspace role, and subscription details. Returns name, email, organization, role, and billing info. **Parameters** No parameters required. *** ## Create & Update Tools for writing data to your CRM. Writes can apply directly and do not necessarily enter the in-app approval queue. Enrichment and follow-up workflows depend on workspace configuration, plan entitlements, and remaining usage. ### `create_deal` Create a new deal in the CRM and assign it to a pipeline stage. The associated account and contacts must already exist. Create them first if needed. **Parameters** **pipeline_id** `string` *required* Pipeline UUID. Use `get_pipeline_overview` to find it. **name** `string` Deal name. Auto-generated from account/contact if omitted. **stage_id** `string` Stage UUID within the pipeline. Defaults to first stage. Use `list_pipeline_stages` to find it. **deal_size** `number` Deal value in dollars. **close_date** `string` Expected close date (ISO 8601). **next_action_date** `string` Next follow-up date (ISO 8601). **next_steps** `string` Description of next steps for this deal. **account_domain** `string` Domain of the associated company (must already exist in CRM). **primary_contact_email** `string` Email of the primary contact (must already exist in CRM). **additional_contact_emails** `array` Emails of additional contacts (must already exist in CRM). **owner_email** `string` Email of the deal owner (org member). Defaults to current user. **Example** **Prompt:** "Create a deal for Stripe, \$120K enterprise plan" The AI assistant will chain tools: `get_pipeline_overview` → `create_account` (if needed) → `create_contact` (if needed) → `create_deal`: ```json theme={"system"} { "tool": "create_deal", "arguments": { "pipeline_id": "22222222-2222-4222-8222-222222222222", "name": "Stripe - Enterprise Plan", "deal_size": 120000, "account_domain": "stripe.com", "primary_contact_email": "sarah@stripe.com", "close_date": "2026-04-30" } } ``` **What happens next:** Verify the new deal and its relationships. Enrichment and follow-up workflows run according to workspace configuration and remaining plan usage. *** ### `create_contact` Create a new contact from an email address. Work-email domains can be linked to company accounts; personal email domains do not identify a company. Enrichment is subject to your plan and available credits. **Parameters** **email** `string` *required* Contact's email address. **first_name** `string` Contact's first name. **last_name** `string` Contact's last name. **Example** **Prompt:** "Add Sarah Chen from Stripe to our CRM" **Tool call:** ```json theme={"system"} { "tool": "create_contact", "arguments": { "email": "sarah@stripe.com", "first_name": "Sarah", "last_name": "Chen" } } ``` *** ### `create_account` Create a new account (company) from a domain. Enrichment follows your plan and available credits. **Parameters** **domain** `string` *required* Company domain (e.g., "stripe.com", "linear.app"). **Example** **Tool call:** ```json theme={"system"} { "tool": "create_account", "arguments": { "domain": "linear.app" } } ``` *** ### `create_note` Create a note and link it to a deal, contact, or account. **Parameters** **title** `string` *required* Short title for the note. **content** `string` Full note content (plain text). **entity_id** `string` *required* UUID of the entity to link this note to. Use a search tool first to find the ID. **entity_type** `string` *required* Type of the linked entity: `account`, `contact`, or `opportunity`. **Example** **Prompt:** "Add a note to the Stripe deal: spoke with Sarah, they want SOC 2 before signing" The AI assistant will call `search_deals` first to get the deal ID, then: ```json theme={"system"} { "tool": "create_note", "arguments": { "title": "Call with Sarah Chen", "content": "Spoke with Sarah - they want SOC 2 report before procurement can sign off. Timeline is end of Q1.", "entity_id": "11111111-1111-4111-8111-111111111111", "entity_type": "opportunity" } } ``` *** ### `create_task` Create a task and optionally link it to a deal, contact, or account. Use for reminders, follow-ups, action items, or next steps. For several tasks, the server also accepts a `tasks` array of 1–50 items with optional `defaults`. Do not mix a batch with single-task fields. Inspect each result and check unknown outcomes before retrying; replaying a batch can create duplicates. **Parameters** **assignee_id** `string` One active member’s user UUID from `list_workspace_members`. Omit to assign yourself on create or preserve assignments on update. Null cannot clear assignments. **title** `string` *required* Short title for the task. **content** `string` *required* Nonempty description containing the request, context, and work to do. **due_date** `string` Due date (ISO 8601). **priority** `string` Priority level: `Low`, `Medium`, `High`, or `Urgent`. **is_urgent** `boolean` Mark as urgent. Defaults to false. **entity_id** `string` UUID of the entity to link this task to. **entity_type** `string` Type of the linked entity: `account`, `contact`, or `opportunity`. Required when `entity_id` is provided. **Example** **Prompt:** "Remind me to send SOC 2 report to Stripe by Friday" ```json theme={"system"} { "tool": "create_task", "arguments": { "title": "Send Stripe SOC 2 report", "content": "Send the SOC 2 report to the Stripe deal contact for their security review.", "due_date": "2026-04-17", "priority": "High", "entity_id": "11111111-1111-4111-8111-111111111111", "entity_type": "opportunity" } } ``` *** ### `update_deal_stage` Move a deal to a specific stage by stage ID. **Parameters** **opportunity_id** `string` *required* The deal/opportunity ID. Use `search_deals` to find it. **stage_id** `string` *required* Target stage ID. Use `list_pipeline_stages` to find available stages. *** ### `move_deal_to_next_stage` Automatically advance a deal to the next stage in its pipeline based on stage order. **Parameters** **opportunity_id** `string` *required* The deal/opportunity ID. Use `search_deals` to find it. **Example** **Prompt:** "Move the Stripe deal to the next stage" ```json theme={"system"} { "tool": "move_deal_to_next_stage", "arguments": { "opportunity_id": "11111111-1111-4111-8111-111111111111" } } ``` *** ### `update_note` Update an existing note's title or content. **Parameters** **note_id** `string` *required* UUID of the note to update. **title** `string` New title for the note. **content** `string` New content for the note. *** ### `update_task` Update an existing task. Change title, due date, priority, or mark as complete. **Parameters** **assignee_id** `string` One active member’s user UUID from `list_workspace_members`. Omit to assign yourself on create or preserve assignments on update. Null cannot clear assignments. **task_id** `string` *required* UUID of the task to update. **title** `string` New title. **content** `string` New description. **due_date** `string` New due date (ISO 8601). Set to null to remove. **priority** `string` New priority: `Low`, `Medium`, `High`, or `Urgent`. **is_urgent** `boolean` Set or unset urgent flag. **completed** `boolean` Set to true to mark as done, false to reopen. **Example** **Prompt:** "Mark my SOC 2 task as done" ```json theme={"system"} { "tool": "update_task", "arguments": { "task_id": "33333333-3333-4333-8333-333333333333", "completed": true } } ``` *** ## Pipeline Management Tools for configuring and navigating your pipeline structure. ### `list_pipeline_stages` List all stages for a pipeline, showing name, order, type (won/lost/default), and win probability. **Parameters** **pipeline_name** `string` Name or partial name of the pipeline. Omit to list stages for all pipelines. **pipeline_id** `string` Pipeline ID, if already known. *** ### `rename_pipeline` Rename a sales pipeline. **Parameters** **pipeline_id** `string` *required* UUID of the pipeline to rename. Use `get_pipeline_overview` to find it. **new_name** `string` *required* The new name for the pipeline. **description** `string` New description for the pipeline. *** ## Field Discovery Tools for discovering available fields and custom properties on your CRM records. Useful before creating or updating records to check what fields are available. ### `get_account_fields` Discover available fields and custom properties for accounts (companies). Returns field names, types, and valid dropdown options. **Parameters** No parameters required. *** ### `get_contact_fields` Discover available fields and custom properties for contacts. Returns field names, types, and valid dropdown options. **Parameters** No parameters required. *** ### `get_deal_fields` Discover available fields and custom properties for deals in a specific pipeline. Each pipeline can have different custom fields. **Parameters** **pipeline_name** `string` Name or partial name of the pipeline. **pipeline_id** `string` Pipeline ID, if already known. *** ## Signal ### `get_signal_script` Get the Octolane Signal tracking script tag for your website. Returns an HTML snippet with your organization's unique public key to install in your website's ``. **Parameters** No parameters required. *** ## Workspace Tools for managing your workspace and team. ### `list_workspace_members` List all members in the workspace with their name, email, role, and avatar. **Parameters** **search_name** `string` Filter by name to find a specific member. *** ### `invite_team_member` Invite one or more people to your workspace by email. Requires admin or owner role. **Parameters** **members** `array` *required* List of people to invite (max 10). Each entry has: * `email` (string, required). Email address of the person to invite * `role` (string). `member` (default), `admin`, or `owner` **Example** **Prompt:** "Invite [sarah@company.com](mailto:sarah@company.com) as an admin" **Tool call:** ```json theme={"system"} { "tool": "invite_team_member", "arguments": { "members": [ { "email": "sarah@company.com", "role": "admin" } ] } } ``` *** ## Stale deals ### `find_stale_deals` Find open deals that have not moved for at least `days` days. `stale_by: "activity"` measures the linked account’s last email or meeting; `"stage"` measures the last stage change. A deal is never counted as older than its creation date. Won and lost deals are excluded. | Parameter | Meaning | | - | - | | `days` | Required positive integer, such as `14`. Let the server calculate the cutoff. | | `stale_by` | `activity` (default) or `stage` | | `pipeline_name` | Optional pipeline name; omit to search all pipelines | | `limit` | Page size, 1–50; default 10 | | `offset` | Zero-based offset; default 0 | ```json theme={"system"} { "tool": "find_stale_deals", "arguments": { "days": 14, "stale_by": "activity", "limit": 50, "offset": 0 } } ``` Continue through the returned pagination before describing all matching deals. Use `days_stale` and `stale_since_source` to explain why a deal is included. An omitted deal may be too new to qualify; absence does not prove recent activity. ## Company brain Knowledge is accessible through the following memory tools. Read the connected server's schemas before calling them. A read request does not authorize changing knowledge. ### `memory_list` List accessible memory blocks. `scope` can be `org` (shared workspace), `user` (your private knowledge), or `both` (default). Optional `category` filters a category such as `sales_icp`, `sales_process`, `product_info`, `pricing`, `writing_style`, or `custom`. Use `entity_type` (`account`, `contact`, or `opportunity`) together with `entity_id` to select knowledge linked to a record. `include_pending` defaults to false; proposed learnings awaiting review should not be presented as approved knowledge. ```json theme={"system"} { "tool": "memory_list", "arguments": { "scope": "both", "include_pending": false } } ``` ### `memory_get` Read a block using its required `id` UUID from `memory_list`. The response includes content, scope, category, source, version, review state, and update time. Read the applicable blocks before answering and distinguish their evidence from your own suggestions. ```json theme={"system"} { "tool": "memory_get", "arguments": { "id": "44444444-4444-4444-8444-444444444444" } } ``` ### `memory_upsert` Create or update a knowledge block when the user requests that change. Required fields are `scope`, `category`, and `content`; content is limited to 8,000 characters. Supply `id` to update an existing block. On update, scope and category remain those of the stored block. Shared `org` writes require administrator privileges; `user` blocks are private to the connected user. Use `category: "custom"` for a free-form block, with a nonempty `title` of at most 80 characters. Creating a fixed-category block replaces that category’s system block, so read it before replacing its content. Check the returned scope, category, title, and content instead of assuming every requested field changed. Optional `activation_tags` describe when knowledge applies; they do not automatically inject or enforce instructions in an external MCP client. The client must read applicable knowledge using `memory_list` and `memory_get`. ### `memory_delete` Delete a block by its required `id`. Confirm the target from a prior read, respect the connected member’s permissions, and verify the result. Do not delete knowledge as part of a query-only request. ## Additional workflows Discover these tools with `tools/list` for their full argument schemas. Availability follows the connected server and permissions. | Workflow | Tools | | - | - | | Read account/contact details | `get_account_details`, `get_contact_details` | | Inspect record changes | `get_record_history` | | Batch create records | `bulk_create_accounts`, `bulk_create_contacts`, `bulk_create_deals` | | Patch record fields | `bulk_update_accounts`, `bulk_update_contacts`, `bulk_update_deals` | | Configure pipelines | `list_pipelines`, `create_pipeline`, `delete_pipeline`, `bulk_upsert_stages`, `bulk_delete_stages` | | Schedule or revise outbound email | `schedule_bulk_emails`, `update_scheduled_email` | | Read meeting details | `get_meeting_details` | Batch record creates accept at most 50 items; direct batch updates accept at most 25 records per call. Use IDs and property names from searches and field-discovery tools. Review per-record failures before retrying, especially for operations that create new records. Scheduled email calls can send messages to people: establish the intended sender, recipients, content, and send time before making an authorized call. Scheduling accepts at most 10 drafts per call with an explicit timezone, at least 30 seconds in the future and no more than a year out. Editing and cancelling a scheduled email are separate alternatives in `update_scheduled_email`. ## Rate limits Handle `429` responses, honor `Retry-After` when provided, and back off before retrying. MCP discovery does not publish a numeric quota; do not assume REST route limits apply to every tool. See [Authentication](/docs/mcp/authentication#rate-limits). # Use Octolane with ChatGPT Source: https://octolane.com/docs/mcp/use-with-chatgpt Connect ChatGPT to Octolane with OAuth to query CRM records and company knowledge and perform authorized updates. Every Octolane plan includes MCP. ChatGPT workspace permissions and security policies also govern whether you can add a custom MCP connection. ## Setup 1. In ChatGPT on the web, open **Plugins**, select the plus button, and choose **Add custom MCP server**. 2. Name it **Octolane** and enter `https://mcp.octolane.com/mcp` as the server URL. 3. Select **OAuth**. Review the connection warning, create the plugin, and enter your personal Octolane API key on the Octolane authorization page when prompted. 4. Install the resulting plugin. In a new conversation, type `@` and select Octolane. 5. Ask which Octolane tools are available and confirm the connected workspace before working with records. These steps follow [OpenAI's custom MCP setup guide](https://developers.openai.com/api/docs/guides/custom-mcp-server). Use that guide for current interface and access requirements. ChatGPT does not send custom API-key headers for this connection. Choose OAuth in ChatGPT; enter the key only in the Octolane authorization form it opens, never in the conversation. See [OpenAI's authentication documentation](https://developers.openai.com/plugins/build/auth) and [Octolane authentication](/docs/mcp/authentication). ## Try a request * “Use Octolane to summarize open pipeline value by stage.” * “Find the Acme deal and summarize its latest meeting and next step.” * “What has our company brain learned about common buyer objections?” * “Draft a follow-up for Acme for me to review.” For updates, identify the record and requested change. Review any client confirmation, then check the result in Octolane. Do not assume every external tool call enters Octolane's in-app approval queue. ## Troubleshooting If the connection is unavailable, check workspace policy. If authentication expires, reconnect through the plugin. If tools change, refresh the connection's metadata and start a new conversation; see [OpenAI's connection guide](https://developers.openai.com/plugins/deploy/connect-chatgpt). # Use Octolane with Claude Source: https://octolane.com/docs/mcp/use-with-claude Connect Claude web or Desktop to Octolane with a remote MCP connector for CRM records and company knowledge. Use a remote connector to work with Octolane in Claude web or Desktop. Every Octolane plan includes MCP; Claude account and organization policies also apply. ## Setup 1. Open Claude's **Connectors** settings and add a custom remote connector. Organization administrators may need to add it first. 2. Name it **Octolane** and use `https://mcp.octolane.com/mcp` as the server URL. 3. Complete the detected OAuth flow. On Octolane’s authorization page, review the access and enter a personal key from [Settings → API keys](https://www.octolane.com/settings/api-keys). If you choose API-key authentication and your connector exposes request headers, send `Authorization: Bearer YOUR_OCTOLANE_API_KEY` using a personal key from [Settings → API keys](https://www.octolane.com/settings/api-keys). 4. Enable the connector in your conversation. Ask which Octolane tools are available and confirm the connected workspace. Follow [Anthropic's remote connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for current menus and account requirements. The hosted Octolane connection does not require a local server entry in `claude_desktop_config.json`. New Octolane users can [start the 7-day Founder trial](https://www.octolane.com/auth/sign-up). There is no ongoing free Octolane plan. See [Pricing](/docs/account/plans-pricing). You can also ask: “What does our company brain say about objections in recent deals?” Discover the currently available tools instead of guessing a knowledge-tool name. ## Example prompts Here are prompts that work well with Claude + Octolane. Copy and paste any of these to get started. ### Pipeline summary ``` What's my pipeline summary on Octolane? ``` ### Deal deep-dive ``` Can you tell me about the Acme deal? ``` ### Draft a follow-up ``` Write me a follow-up email for the Acme deal for our next meeting. ``` ## Tips for best results > [accordion] Be specific about what you want > > Instead of "Show me deals," try "Show me open deals worth more than \$50K in the negotiation stage." The more specific your query, the more useful the response. > [accordion] Ask follow-up questions > > Claude remembers context within a conversation. Start with "Show me stale deals" then follow up with "Draft a summary of the top 3 for my team standup" without repeating the original query. > [accordion] Combine data sources > > Ask Claude to cross-reference Signal visitors with your existing pipeline: "Are any of this week's website visitors already in our pipeline? What about visitors from companies similar to our best customers?" > [accordion] Use natural dates > > Claude handles relative dates well. Say "deals closing this month," "last week's website visitors," or "meetings scheduled for tomorrow" instead of specific dates. > [accordion] Request specific formats > > Ask for the output format you want: "Show me this as a table," "Give me bullet points," or "Summarize in 2 sentences." Claude adapts to your preferred format. # Use Octolane with Cursor Source: https://octolane.com/docs/mcp/use-with-cursor Connect Octolane to Cursor so you can query your CRM, manage deals, and trigger agents while you code. Query your CRM, check deal status, and log notes without leaving your editor. Useful for developers who manage customer relationships, founders who code and sell, or anyone who wants CRM access in their development workflow. ## Setup **1. Create the config file** Create `.cursor/mcp.json` in your project root or your global Cursor config directory: ```json theme={"system"} { "mcpServers": { "octolane": { "url": "https://mcp.octolane.com/mcp", "headers": { "Authorization": "Bearer YOUR_OCTOLANE_API_KEY" } } } } ``` Replace `YOUR_OCTOLANE_API_KEY` with a personal key from [Settings → API keys](https://www.octolane.com/settings/api-keys). Requests use the creator's current workspace access. Every Octolane plan includes MCP. Cursor also supports OAuth for remote MCP servers. To use it, omit the `headers` object and enter a personal Octolane key in the connection's authorization page. See [Cursor's MCP documentation](https://cursor.com/docs/mcp) and [Octolane authentication](/docs/mcp/authentication). > [!WARNING] > > Add `.cursor/mcp.json` to your `.gitignore` so your API key doesn't end up in version control. **2. Restart Cursor** Restart Cursor to pick up the new MCP configuration. The Octolane tools will be available in Cursor's AI chat. **3. Verify** Open Cursor's AI chat and ask: ``` What Octolane tools are available? ``` You should see the tools advertised by the connected server. Confirm your workspace with `get_current_user` when available. Also try asking what your [company brain](/docs/ai/company-brain) has learned about a recurring sales objection. ## Why use Octolane in Cursor ### Check customer context while building When you're working on a feature request from a specific customer, pull up their deal to see the full context without switching to a browser: ``` Pull up the deal with Linear. What did they ask for in our last meeting? What are their action items? ``` ### Log notes without context-switching Just finished a customer call? Log it from Cursor: ``` Add a note to the Stripe deal: "Call with Sarah - they want to proceed with enterprise plan. Need SOC 2 report before procurement. Timeline is end of Q1. Budget approved by CFO." ``` ### Morning pipeline check during standup Run a quick pipeline check before your team standup: ``` Show me all my deals that changed stage this week. What's stale? What meetings do I have today? ``` ### Check Signal between deploys While waiting for a deploy, check who's been visiting your site: ``` Any interesting companies visit our site today? Show me ones that match our ICP and aren't already in our pipeline. ``` ### Quick data lookups Need a customer's email or company details while writing code? ``` What's the email for our main contact at Notion? ``` ``` How big is Ramp? What's their tech stack? ``` ## Example workflows for developers > [accordion] Pre-standup pipeline review > > ``` > Show me pipeline changes from this week: > - New deals created > - Deals that changed stage > - Stale deals (no activity in 14+ days) > - Deals closing this month > > Keep it brief - just names, values, and what changed. > ``` > [accordion] Customer debugging context > > ``` > A customer at acme-corp.com reported a bug. Pull up everything we > know about them - their deal, contacts, recent conversations, and > what plan they're on. > ``` > [accordion] Quick deal creation after a call > > ``` > Just had a call with the CTO of newstartup.io. Create a deal - > $30K annual, they're interested in the Pro plan. Stage is > "Meeting Scheduled". Main contact is alex@newstartup.io. > Add a note: "Inbound via website. Evaluating us vs HubSpot. > Decision in 2 weeks." > ``` > [accordion] End-of-day deal update > > ``` > Move the Stripe deal to the Negotiation stage. Also add a note: > "They want to add 20 more seats, new value ~$150K. Close date > pushed to April 30." > ``` > [accordion] Task and email check > > ``` > What tasks do I have due today? And show me any unanswered > emails from this week. > ``` > [accordion] Signal check for prospecting > > ``` > Show me companies that visited our docs this week with 50+ employees. > Are any of them already in our CRM? For the ones that aren't, show me > their ICP score and company details. > ``` ## Tips * Use Cursor's Agent mode for multi-step CRM workflows (pipeline review + deal updates + note creation in one go) * Keep queries focused - "Show me stale deals" works better than "Give me a full analysis of our entire pipeline health" * You can reference CRM data in your code comments: ask about a customer's requirements, then use the context while building their feature