Reference guides for the CRM apps an AI agent can work with: every endpoint, the permission each one needs, and how to give agents safe, governed access.
The Close API is how an app or AI agent works with a Close CRM organization: creating and updating leads and their contacts, tracking opportunities through a pipeline, logging activities like calls, emails, and notes, and managing tasks.
The Copper API is how an app or AI agent works with a Copper account: searching people and companies, creating a lead, advancing an opportunity through a pipeline, or logging an activity against a record.
The Freshsales API is how an app or AI agent works with a Freshsales CRM account: creating and updating contacts, accounts, and deals, logging tasks, appointments, and sales activities, and adding notes to records.
The HubSpot API is how an app or AI agent works with a HubSpot account: reading and creating contacts, updating a deal's stage, opening a support ticket, or linking a contact to a company.
The Insightly API is how an app or AI agent works with an Insightly CRM account: reading and updating contacts and organisations, qualifying leads, moving opportunities through a pipeline, and logging tasks, events, and notes against them.
The Keap API is how an app or AI agent works with a Keap account: reading and creating contacts, applying tags that drive automation, tracking sales opportunities through a pipeline, and creating orders, products, and recurring subscriptions.
The Microsoft Dynamics 365 API is how an app or AI agent works with the Dataverse data behind the business apps: reading and updating accounts and contacts, qualifying a lead, creating an opportunity, or resolving a customer case.
The Nutshell API is how an app or AI agent works with a Nutshell CRM account: finding and creating leads, adding people and companies, logging activities, and reading the pipeline a sales team sells through.
The Pipedrive API is how an app or AI agent works with a sales pipeline: creating a deal, looking up the person or organization behind it, logging an activity, or converting a lead.
The Salesforce API is how an app or AI agent works with a Salesforce org: reading and writing records like accounts and contacts, running a SOQL query, searching across objects, or batching several changes into one call.
The SugarCRM API is how an app or AI agent works with a CRM instance: listing accounts, reading a contact, creating a lead, updating an opportunity, or filing a case.
The Zoho CRM API is how an app or AI agent works with a Zoho CRM org: reading and writing records in a module like Leads or Deals, searching and querying across modules, adding notes and tasks, and reading the modules, fields, and users that describe the account.
A CRM API is how an app or AI agent works with the record of a company’s customers and deals. The systems here, including Salesforce, HubSpot, Pipedrive, and Zoho CRM, store contacts, companies, deals, and the notes and emails attached to them, and their APIs let an agent read those records, create or update them, and react when one changes.
CRM data is among the most sensitive a business holds, so the permission attached to an agent’s access matters: a read permission returns contact and deal details, while a write permission can change a deal stage, edit a contact, or delete a record. Access runs on an access token, often scoped to particular objects like contacts or deals. A governed layer lets an agent that drafts follow-ups read deals without also being able to delete them.
Bollard AI sits between a team's AI agents and the apps it runs on. Grant each agent exactly the access it needs, read or write, app by app, and every call is checked and logged.