> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorbitcrm.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build your CRM

> Have an AI agent set up your pipelines, custom fields, settings and saved views, then keep the CRM in shape as your process changes.

Setting up a CRM used to take days in settings screens. With Orbit's MCP server you tell an agent how you sell. It builds the structure, tells you what it did, and changes it later the same way.

**1. Connect an agent**

Connect Claude, ChatGPT, Claude Code or Cursor to Orbit ([how](https://docs.useorbitcrm.ai/mcp/overview.md)). On the consent screen, approve `crm:write` for the setup itself, plus `contacts:write`, `companies:write` and `deals:write` for the records it will work with.

**2. Describe how you sell**

Explain your sales process in plain words. The agent turns it into pipelines, stages, custom fields, settings and saved views.

**3. Check and adjust**

Ask the agent to read the setup back to you. Change anything later the same way: split a stage, add a field, save a new view.

## Set up the structure

Start with how your team actually sells:

> "We sell annual contracts. SDRs book demos, then AEs run discovery, send a proposal and negotiate. Set up a New business pipeline for that, plus a Renewals pipeline. On deals we track contract value, seats, renewal date and lead source. Require a lost reason, and flag deals that sit in a stage for more than 14 days."

What the agent does:

| Step | Tools |
| - | - |
| Reads your current setup so it doesn't duplicate anything | `get_crm_schema` |
| Creates pipelines and stages, with win probabilities and won / lost stages | `create_pipeline`, `create_pipeline_stage`, `reorder_pipeline_stages` |
| Adds custom fields on contacts, companies, deals and tasks (text, long text, number, currency, percent, yes/no, date, date and time, link, email, phone, dropdown, multi-select, teammate) | `create_crm_field` |
| Groups fields into sections on record pages and sets their order | `create_crm_field_group`, `update_crm_field` |
| Turns on your rules: lost reasons, stale-deal threshold, default currency, task defaults, linking contacts to companies by email domain | `update_crm_settings` |
| Saves views of the Contacts table for each team or workflow | `create_contact_view` |

> [!TIP]
>
> Give each custom field a description. Agents read field descriptions through `get_crm_schema` before they write data, so write them the way you would explain the field to a new rep.

## Check the agent's work

> "Read back the pipelines, their stages and probabilities, and every custom field on deals."

The agent reads the setup with `get_crm_schema` and `list_pipelines`, and its own result messages name what it created, so nothing happens silently.

## Keep shaping it

The same agent keeps the CRM in shape as your process changes:

> "Split Proposal into Proposal sent and Verbal yes, and move the deals that are waiting on a signature."

> "Add an Industry select field on companies with SaaS, Agency, Ecommerce and Other, and fill it in for every company."

> "Save a contacts view of qualified leads with no meeting yet, sorted by last activity."

## Work the records

Once the structure is there, the agent works the data the same way: it opens companies and deals for qualified leads, fills in fields it has researched, logs calls and meetings with `log_activity`, adds notes and tasks, and moves deals between stages. A lead list from a spreadsheet goes in with `import_contacts`, up to 1,000 rows per call, with tags, owners and companies in the same call and any rows with a problem listed back. [Available tools](https://docs.useorbitcrm.ai/mcp/tools.md) lists everything it can do.

> [!NOTE]
>
> Moving from another CRM? That is a job for Orbit, not for the agent. From HubSpot, **Settings → Integrations → HubSpot → Import from HubSpot** brings contacts, companies, deals, pipelines, custom properties and history across in the background, with HubSpot ids kept ([how it works](https://docs.useorbitcrm.ai/integrations/hubspot.md#import-from-hubspot)). From any CRM, developers can load records through the API's bulk imports: see [Migrating from another CRM](https://docs.useorbitcrm.ai/developers/migrating-from-another-crm.md).

Agents connected over MCP can't delete contacts, companies or deals. That needs the `:delete` scopes, which only API keys and OAuth apps registered in the Developer Portal can hold on the [REST API](https://docs.useorbitcrm.ai/developers/api/crm.md); assistants that register themselves over MCP never get them. See [Available Tools](https://docs.useorbitcrm.ai/mcp/tools.md) for everything an agent can do.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.