Data mapping
The table below shows what the integration reads from and writes to your Salesforce, object by object.
uman object | Salesforce object | What uman reads | What uman writes |
Account | Account | Name and record type | Creates Accounts (name, record type + any other required field) |
Contact | Contact | First name, last name, email, phone, title and the linked Account | Creates or updates Contacts (first name, last name, email, phone, title, the linked Account + any other required field) |
Deal | Opportunity | Name, stage, pipeline, close date and the linked Account | Creates Opportunities (name, stage, pipeline, the linked Account) and updates the stage + any other required field |
Pipeline | Record Type | Active Opportunity pipelines and their stages | Read only |
Note | Content Note | Content Notes attached to an Account, Contact or Opportunity | Creates or updates Content Notes (title and content). Every note is linked to an Account, Contact or Opportunity |
Custom object | Any object | Fields required to create an Account, Contact or Opportunity | Objects required to create an Account, Contact or Opportunity, with any field those objects require |
Setup Instructions
An administrator can install the package by clicking this link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWV0000004l8PYAQ
If you are installing the package in a sandbox environment, use:
After the package is installed, users can connect their Salesforce account in the uman platform (using an OAuth2.0 user integration).
Used OAuth scopes
Access unique user identifiers (openid)
Manage user data via APIs (api)
Perform requests at any time (refresh_token, offline_access)
For further assistance, please contact our support team or visit our comprehensive knowledge base.
FAQ
Which Salesforce note type is used?
uman will read/write to enhanced notes. This is a newer version compared to classic notes and allow for rich text, linking the note to multiple records, ...
Enhanced note vs classic (old) note comparision