Skip to content

Commit af4e0b2

Browse files
authored
Update Salesforce docs ahead of Salesforce (Actions) GA Launch 6/15 (#3020)
1 parent f9b8c6f commit af4e0b2

File tree

2 files changed

+3
-8
lines changed
  • src/connections/destinations/catalog

2 files changed

+3
-8
lines changed

src/connections/destinations/catalog/actions-salesforce/index.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ id: 61957755c4d820be968457de
77
---
88
Segment’s Salesforce (Actions) destination allows you to create, update or upsert records for any object type. Segment sends data to the [Salesforce REST API](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm){:target="_blank"}.
99

10-
> info ""
11-
> The Salesforce (Actions) destination is in beta and is in active development. Some functionality may change before it becomes generally available.
12-
1310
> success "Good to know"
1411
> This page is about the [Actions-framework](/docs/connections/destinations/actions/) Salesforce destination. There's also a page about the [non-Actions Salesforce destination](/docs/connections/destinations/catalog/salesforce/). Both of these destinations receive data _from_ Segment.
1512

src/connections/destinations/catalog/salesforce/index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,14 @@
22
title: Salesforce Destination
33
strat: salesforce
44
id: 54521fda25e721e32a72eeef
5+
maintenance: true
56
---
67

7-
Segment's Salesforce destination allows you to identify leads without using SOAP APIs.
8+
Segment's Salesforce destination allows you to create and store leads and records for other objects in Salesforce Sales Cloud.
89

910
> info ""
1011
> Segment is aware of Salesforce's plans to enforce multi-factor authentication in 2022, and advises migrating to our new [Salesforce (Actions) destination](/docs/connections/destinations/catalog/actions-salesforce/) which supports OAuth 2.0.
1112
12-
> success "Good to know"
13-
> This page is about the classic Salesforce Segment destination. There's also a page about the new [Salesforce (Actions) destination](/docs/connections/destinations/catalog/actions-salesforce/). Both of these destinations receive data _from_ Segment. Use the new Salesforce (Actions) destination for additional functionality and flexibility.
14-
1513
### API Access
1614

1715
Segment uses the Salesforce SOAP API to connect. This API requires the following credentials of a registered Salesforce user:
@@ -27,7 +25,7 @@ Also make sure that IP Security is disabled in this Salesforce user account. Thi
2725

2826
## Identify
2927

30-
This destination supports the most important pain point for Salesforce users: getting your prospective customers into Salesforce as Leads from your website or mobile app. Creating/updating Leads is the default behavior of `identify` events. If you would like to customize this you can do so using [Actions](#custom-actions)
28+
This destination supports the most important pain point for Salesforce users: getting your prospective customers into Salesforce as Leads from your website or mobile app. Creating/updating Leads is the default behavior of `identify` events. If you would like to customize this you can do so using [Actions](#custom-actions).
3129

3230
### Identifying a Lead
3331

0 commit comments

Comments
 (0)