Skip to content

Commit 3a98ac9

Browse files
authored
Add redirect for consolidated Salesforce tiles (#3729)
* Add redirect for consolidated Salesforce tiles * Update index.md * Update index.md
1 parent 9dd9ef3 commit 3a98ac9

File tree

1 file changed

+11
-6
lines changed
  • src/connections/destinations/catalog/actions-salesforce

1 file changed

+11
-6
lines changed

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

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,16 @@ hide-boilerplate: true
44
hide-dossier: false
55
strat: salesforce
66
id: 61957755c4d820be968457de
7+
versions:
8+
- name: "Salesforce (Classic)"
9+
link: '/docs/connections/destinations/catalog/salesforce/'
10+
redirect_from:
11+
- '/connections/destinations/catalog/vendor-salesforce/'
712
---
8-
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"}.
913

10-
> success "Good to know"
11-
> 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.
14+
{% include content/plan-grid.md name="actions" %}
15+
16+
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"}.
1217

1318
## Benefits of Salesforce (Actions) Destination vs Salesforce Destination Classic
1419

@@ -23,9 +28,9 @@ The Salesforce (Actions) destination provides the following benefits over the cl
2328
Before you connect Segment to Salesforce, please ensure you have a Salesforce account with REST API access.
2429

2530
1. From the Segment web app, click **Catalog**, then click **Destinations**.
26-
2. Search for **Salesforce (Actions)** in the Destinations Catalog, and select the destination.
27-
3. Click **Configure Salesforce (Actions)** in the top-right corner of the screen.
28-
4. Select the source that will send data to Salesforce (Actions) and follow the steps to name your destination.
31+
2. Search for **Salesforce** in the Destinations Catalog, and select the destination.
32+
3. Click **Configure Salesforce** in the top-right corner of the screen.
33+
4. Select the source that will send data to Salesforce, follow the steps to name your destination, and select **Actions** as the destination framework.
2934
5. On the **Settings** tab, authenticate with Salesforce using OAuth.
3035
6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). You must select which Event Types and/or Event Names will trigger each mapping.
3136
7. Enable the destination and configured mappings.

0 commit comments

Comments
 (0)