Salesforce.

CRM·IN DEVELOPMENT·CSV IMPORT AND API TODAY

Current status.

Atlas lists a Salesforce connector in Settings, then Integrations, and our team is building it now. Until it is finished there is no Connect button. Atlas cannot read from or write to a Salesforce org today, and nothing on this page should be read as a working Salesforce integration.

If Salesforce matters to your team, tell us. Until then, the options below work now.

What the listing describes.

When Atlas enables it, the listing describes a connector you link with OAuth 2.0 to a production org or a sandbox. It would run record queries, read how objects are built, search records, and read, create, and change accounts, contacts, leads, opportunities, and cases when someone starts an action. It would not be a continuous background sync. None of this works yet, and the details may change before it ships.

What works today.

Option 01

CSV import into Atlas CRM.

Export contacts from Salesforce as a CSV file and import them into the Atlas CRM module. This is a one-time file import, not a live sync.

Option 02

The REST API.

Create and update Atlas CRM contacts, accounts, and deals from your own script, for example one that reads from the Salesforce API on a schedule.

Option 03

Webhooks out of Atlas.

Register a signed webhook so a change in Atlas reaches your own receiver, which can then update Salesforce through its API.

Option 04

Gmail for email.

The Gmail connector is available now. Each person connects their own mailbox, so customer threads sit next to Atlas work.

Option 05

Atlas CRM on its own.

Atlas has its own CRM module with contacts, accounts, deals, and pipelines, if you want to run the pipeline in Atlas.

Example: import a Salesforce contact export into Atlas CRM

# Send the CSV text from a Salesforce export. Columns and values are samples.
curl -X POST https://api-atlas.wrxstack.com/v1/crm/import/contacts \
  -H "Authorization: Bearer $ATLAS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "csv": "firstName,lastName,email\nSample,Contact,contact@example.com",
    "hasHeader": true
  }'

Example: create one contact from your own sync script

# Sample values. Run this from a script that reads Salesforce.
curl -X POST https://api-atlas.wrxstack.com/v1/crm/contacts \
  -H "Authorization: Bearer $ATLAS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "firstName": "Sample",
    "lastName": "Contact",
    "email": "contact@example.com",
    "source": "other"
  }'

Today versus listed.

Need	Direction	Today	Notes
Contacts	Salesforce → Atlas	CSV import or API	One-time import, or your own script calling the API.
Accounts, deals	Salesforce → Atlas	REST API	Your own script creates and updates Atlas CRM records.
Changes in Atlas	Atlas → Salesforce	Webhooks	Your receiver gets signed events and updates Salesforce itself.
Leads, cases, queries	Both	In development	Needs the Salesforce connector, which is in development.

Security model.

Because the Salesforce connector is still in development, Atlas holds no Salesforce credentials and reads nothing from your org. Data reaches Atlas only through a file you import or an API call you make with your own token. Atlas signs each webhook delivery, so your receiver can check that it came from Atlas.

Questions.

There is no Connect button for Salesforce.The connector is in development for every workspace. There is nothing for you to configure.
When will it be available?There is no date. This page will change when the connector ships.
Is HubSpot any different?No. The HubSpot connector is also in development. CSV import into Atlas CRM works for HubSpot exports too.