Skip to main content
Skip table of contents

Salesforce

Overview

Ingest Salesforce into Alli by leveraging Amazon AppFlow's capabilities.

Vendor/Partner

Salesforce

Version

n/a

API Documentation

https://aws.amazon.com/appflow/

Sunset Date

Channel(s)

All

Refresh Time (CST)

Default backfill

Alli Data Library

(error)

Getting Started

Once you have read through the requirements and are ready to ingest Salesforce data into Alli create a support ticket here.

Requirements

  • Your Salesforce account must be enabled for API access. API access is enabled by default for the Enterprise, Unlimited, Developer, and Performance editions.

  • Your Salesforce account must allow you to install connected apps. If this functionality is disabled, contact your Salesforce administrator. After you create a Salesforce connection in Amazon AppFlow, verify that the connected app named Amazon AppFlow Embedded Login App is installed in your Salesforce account.

  • The refresh token policy for the Amazon AppFlow Embedded Login App must be set to Refresh token is valid until revoked. Otherwise, your flows will fail when your refresh token expires. For more information on how to check and edit the refresh token policy, see Manage OAuth Access Policies for a Connected App in the Salesforce documentation.

  • You must enable change data capture in Salesforce to use event-driven flow triggers. For more information on how to enable this, see Select Objects for Change Notifications in the User Interface in the Salesforce documentation.

  • If your Salesforce app enforces IP address restrictions, you must grant access to the addresses used by Amazon AppFlow. For more information, see AWS IP address ranges in the Amazon Web Services General Reference.

  • To create private connections using AWS PrivateLink, you must enable both Manager Metadata and Manage External Connections user permissions in your Salesforce account. Private connections are currently available in the us-east-1, us-west-2, ap-northeast-1, ap-south-1, ap-southeast-2, ca-central-1, and eu-central-1 AWS Regions.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.