CRM automation settings
Choose which new conversations create deals, where they start in your workspace pipeline, and who may change those shared settings.
Where it lives
One settings record belongs to each workspace and is edited in CRM → Settings. A workspace that has never opened the page still behaves predictably: unset settings resolve to the defaults below, and saving is what makes them explicit.
Conversation automation
| Setting | Default | Values | Effect |
|---|---|---|---|
| Enabled | On | On / Off | Master switch for creating deals from conversations. Off still records conversation references |
| Trigger | First message | First message | Which moment in a conversation is considered |
| Directions | Inbound and outbound | Inbound, outbound, or both | Whether a conversation the customer started, your team started, or either can create a deal |
| Inbox scope | All inboxes | All / only selected / all except selected | Which inboxes participate |
| Starting stage | New | Any stage in this workspace's pipeline | The stage a created deal opens in |
| Skip when a deal is already open | On | On / Off | Prevents a second deal for a contact who already has one open |
Set up or change the available stages in Opportunities and pipeline. CRM shows stage labels your team recognizes and will not save a starting stage that is outside the shared pipeline.
Defaults are chosen so a connected workspace is useful before anyone configures anything, and narrowing is the deliberate act.
Who can change them
| Capability | Requirement |
|---|---|
| View settings | CRM read access in that workspace |
| Change settings | CRM write access, and an administrator or manager seat, or an explicit settings-management permission |
A member seat can see the rules that govern their pipeline without being able to change them. Every change is recorded with its actor and time.
Reading and writing over the API
| Operation | Endpoint |
|---|---|
| Read current settings | GET /v1/crm/settings |
| Save pipeline or conversation automation | PUT /v1/crm/settings |
Both are scoped to one organization and workspace, and use the same permissions as the interface. Values are validated rather than trusted: an unknown direction, a non-numeric inbox id, or a stage outside the workspace pipeline is rejected without partially applying the change. See the CRM API for authentication.