Skip to content

Start building

Integration · CRM

AI agents for SugarCRM

Find, read, create, update and delete records in any SugarCRM.

Actions
7
Read
3
Write
4

Actions

What your agents can do in SugarCRM

Find, read, create, update and delete records in any SugarCRM (SugarAI) module, such as accounts, contacts, leads, opportunities, cases, calls, meetings, tasks and notes, and list or link related records, on Sugar Cloud or your own server.

Read 3

Look things up. Nothing changes.

  • Find records

    Finds records of one module that match a Sugar filter.

  • Get a record

    Returns one record of a module by its ID, with every field or only the fields named.

  • List related records

    Lists the records linked to one record through a link field, like the contacts of an account (module Accounts, link contacts), the opportunities of a contact.

Write 4

Create, change or send.

  • Create a record

    Creates a record in a module from a map of field names to values, like {"first_name".

  • Update a record

    Changes the fields named on one record and leaves the rest as they are, like {"sales_stage": "Closed Won"} on an opportunity or {"status": "Converted"} on a lead.

  • Delete a recordDeletes data

    Deletes one record of a module by its ID (Sugar marks it deleted; an administrator can no longer open it).

  • Link two records

    Relates one record to another through a link field, like a contact to an opportunity (module Opportunities, link contacts, related ID the contact's ID).

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

Sign-in details

Enter the sign-in details SugarCRM gives you for its API.

What you enter

  • User name
  • Password

Settings

  • Sugar address

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your SugarCRM data

    Ask a question in plain words. The agent can find records, get a record or list related records in SugarCRM, then answers with what it found.

  • 02

    Let an agent update SugarCRM

    Have the agent create a record or update a record in SugarCRM as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent SugarCRM and Slack: it can find records in SugarCRM and post a summary to a Slack channel in the same run.

FAQ

SugarCRM and MyDeepAgents

Can MyDeepAgents connect to SugarCRM?

Yes. The SugarCRM connector has 7 actions: 3 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect SugarCRM?

Enter the sign-in details SugarCRM gives you for its API. You'll need: User name and Password. The connection also asks for: Sugar address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in SugarCRM without asking?

Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use SugarCRM in workflows as well as agents?

Yes. Every SugarCRM action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put SugarCRM to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.