Overview of Salesforce connector for Jitterbit Integration Studio
Overview
This topic provides information about using Jitterbit Integration Studio to connect to Salesforce. Typically, this is done using the Salesforce connector (though standards-based connectors for Rest and SOAP APIs are also available).
This topic covers information on connecting to Salesforce organized into three types of documentation:
- Salesforce Connector Configuration: These pages cover reference information on the basics of Salesforce connector configuration:
- Connection: Establishes access with a specific Salesforce endpoint.
- Query Activity: Queries data from a Salesforce endpoint and is intended to be used as a source in an operation.
- Insert Activity: Inserts new data in a Salesforce endpoint and is intended to be used as a target in an operation.
- Update Activity: Updates existing data in a Salesforce endpoint and is intended to be used as a target in an operation.
- Upsert Activity: Both updates existing data and inserts new data in a Salesforce endpoint and is intended to be used as a target in an operation.
- Delete Activity: Deletes data in a Salesforce endpoint and is intended to be used as a target in an operation.
- Bulk Query Activity: Queries a large number of records from a Salesforce endpoint and is intended to be used as a source in an operation.
- Bulk Insert Activity: Inserts a large number of new records in a Salesforce endpoint and is intended to be used as a target in an operation.
- Bulk Update Activity: Updates a large number of existing records in a Salesforce endpoint and is intended to be used as a target in an operation.
- Bulk Upsert Activity: Both updates a large number of existing records and inserts a large number of new records in a Salesforce endpoint and is intended to be used as a target in an operation.
- Bulk Delete Activity: Deletes a large number of records from a Salesforce endpoint and is intended to be used as a target in an operation. Deleted records are stored in the Salesforce Recycle Bin prior to being permanently deleted.
- Bulk Hard Delete Activity: Hard deletes a large number of records from a Salesforce endpoint and is intended to be used as a target in an operation. Hard deleted records automatically become eligible for deletion.
- Salesforce How-tos: These pages provide instructions on how to accomplish certain tasks with Salesforce integration projects:
- Create a Salesforce External ID for Jitterbit: How to create a custom field in Salesforce to associate records with an external ID for use with Jitterbit.
- Create Users in Salesforce: How to create additional front-end users in Salesforce.
- Deploy a Custom Fields Package in Salesforce: How to import a pre-existing Salesforce custom fields package, verify the deployment of the custom fields package, and define custom field and security and accessibility.
- Manually Add Custom Fields in Salesforce: How to manually add custom fields and define their accessibility in Salesforce.
- Update Salesforce Picklist Values and Labels: How to use the Salesforce Tooling API to update picklist values and labels.
- Use Salesforce Functions: How to use a Salesforce connection with Salesforce functions.
- Use Salesforce Jitterbit variables:** How to use Salesforce Jitterbit variables.
- Salesforce troubleshooting: These pages provide troubleshooting details for overcoming challenges with Salesforce integration projects:
- Record limits: Recommendations on enabling chunking if you run into Salesforce API record limits.
Additional resources
The following Jitterbit microlearning tutorials are available through our Jitterbit basics video series, created by Jitterbit University: