Can AI agents automate Sage Intacct?

Sage Intacct is Sage's cloud financial-management product, not Sage 50. The practical automation path is the public APIs. Sage recommends the REST API at api.intacct.com for new client applications and continues to support XML Web Services for create, update, read, and delete of standard and custom objects. REST uses OAuth 2.0 authorization-code (with optional PKCE) and client-credentials grants that issue JWT bearer tokens. XML requests require a Web Services sender ID and password plus company login or session credentials. Both surfaces require an active Web Services developer license, whose sender ID Sage provisions through an account manager, plus company-side authorization of that sender ID and a Web Services subscription on the target company. Official PHP, .NET, and Node.js SDKs wrap the XML gateway; as of 2025 Release 1 those XML SDKs are no longer enhanced, and new objects and features ship on REST. Platform Services HTTP POST triggers can deliver webhooks with automatic retries, Customization Services Smart Events can POST to external URLs, and Data Delivery Service can export bulk CSV to cloud storage as a paid subscription. First-party MCP, a general CLI, named iPaaS connectors, and computer-use viability were not established. XML gateway concurrency and timeout limits, paid DDS and Platform Services subscriptions, and the REST-versus-XML object split remain material operating constraints.

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