SugarAI, automatic contact export

Swopi leads are created in SugarAI as a Lead or a Contact. Connect with a service user, deduplication by email, mapping into your own fields (_c).

The integration with SugarAI (formerly SugarCRM) sends every new contact from Swopi straight into your instance. A lead from a business card or a contact added manually in the dashboard is created as a Lead, or as a Contact, whichever you choose.

One-way push via the SugarAI REST API v11. Swopi never deletes anything in Sugar. Deduplication by email: an existing record is updated instead of creating a duplicate.

#Overview
Target CRM SugarAI Sell, Serve and Enterprise (cloud and self hosted)
Connection Service user (Sugar has no OAuth for outside apps)
What gets created Lead, optionally Contact
Trigger Automatically on a new contact, or manual sending of selected contacts
Deduplication By email, an existing record is updated
Availability Swopi Teams plan, configured by the administrator

#Why a service user and not a one-click sign in

SugarAI has no authorize endpoint, so there is no screen where a customer could grant an outside app access. Its API only knows sign in with a user name and password (and a token refresh afterwards). We therefore recommend creating a service user for Swopi in Sugar rather than using a personal account: you can see what the integration wrote, and a colleague leaving the company does not break the export. The password stays on the Swopi server and is never sent back to the browser.

#Prerequisites

  • the Swopi Teams plan and the administrator role,
  • the instance address, for example https://company.sugarondemand.com,
  • a user allowed to create Leads and Contacts.

#How to connect

Dashboard → Integrations → SugarAI:

  1. Instance address (domain only, no path).
  2. User name of the service user.
  3. Password.
  4. Test connection → Save.

Swopi signs in to Sugar under its own platform, swopi. That is on purpose: Sugar keeps one session per user and platform, so using the default base would sign your colleague out of their browser on every write. If the instance has disable_unknown_platforms turned on, an administrator has to allow the swopi platform.

#Sync settings

Option Description
Automatic sync The contact is written as soon as it is captured. Turn it off to send manually.
Primary object Write as a Lead, or as a Contact.

#Field mapping

Field in Swopi SugarAI
Name first_name / last_name
Email email1 plus the email collection (primary address)
Phone phone_work
Job title title
Company account_name
Website website
City primary_address_city
Country primary_address_country
Note description
Source lead_source = Swopi

last_name is required in Sugar. When a lead has no surname, Swopi uses the full name, and if there is none, the email address.

Email twice. Sugar keeps addresses in the email_addresses relation but also knows the email1 shorthand. Swopi sends both, so the address lands as the primary one on older instances too.

#Custom fields

Custom fields in Sugar end in _c. In the Field mapping tab pick Custom field (enter key) and type the exact name, for example swopi_source_c. The field has to exist in Sugar first, Swopi does not create it. See Field mapping.

#How it works

  • A new lead from a card or a manually added contact → Swopi finds or creates the record (dedup by email).
  • Use Create test lead to verify the connection.
  • The result of every export is in Lead export status and in the sync log.

Need help? Email support@swopi.co.