Can AI agents automate Close?

Close is automatable today through its REST API at https://api.close.com/api/v1. This record is Close CRM pipeline, communications, and organization data. It is not HubSpot, Salesforce Sales Cloud, Pipedrive, or SuperOffice CRM. The API uses JSON over HTTPS with leads, contacts, opportunities, activities, custom fields, sequences, bulk actions, reporting, and an experimental OpenAPI spec. Scripts authenticate with HTTP Basic using an API key as the username and an empty password. User-facing apps use OAuth 2.0 authorization code tokens as Bearer access tokens, with refresh via offline_access. Signed webhooks POST Event Log changes, with HMAC verification and a 40-subscription limit per organization. Close maintains an official Python client (closeio on PyPI). The hosted MCP at https://mcp.close.com/mcp uses HTTP Streamable transport and OAuth 2.0 Dynamic Client Registration, or Close-API-Key plus Close-Scope headers. mcp.read is read-only, mcp.write_safe adds creates, and mcp.write_destructive is required for updates and deletes. n8n's documented MCP setup is read-only. iPaaS connector catalogs and a first-party CLI were not opened. Computer-use viability is unassessed. API and MCP both score 8. API is the best path because webhooks, bulk work, and ordinary updates do not require the destructive MCP scope.

Best path today: api · Overall automatability: 8/10