Need a reportable dataset?
Open Data Export, select an object and fields, compose or refine a SOQL query, then review and export the results.
See Data Export →Guide & support
Get connected. Work with intent.
A practical starting point for installing Lightning Connect, choosing a workflow, and solving common session or access issues.
Get help on GitHubInstallation
Start in three simple steps.
- 1
Install the extension
When the Chrome Web Store listing is available, install Lightning Connect from the listing. For local development, build the project and load its generated extension directory through
chrome://extensions. - 2
Sign in to Salesforce
Open a supported Salesforce domain in Chrome and sign in with the account and org you intend to work with.
- 3
Open the launcher
Use the Salesforce Connect launcher from the Salesforce page, then select a workflow such as Data Export, Data Import, Download Metadata, or Developer Console.
A good first session
Find the tool that matches your next task.
Every workflow begins from your current Salesforce context, while its own focused view gives you room to review details and decide the next action.
Need to update records?
Use Data Import to upload, paste, or enter records. Map columns, correct validation issues, then confirm the permitted operation.
See Data Import →Need source or metadata?
Build a metadata package for retrieval, or open Developer Console to explore, compare, edit, and deploy supported source resources.
See metadata tools →Troubleshooting
Common questions
Why does Lightning Connect say there is no Salesforce session?
Sign in to Salesforce in the same Chrome profile, then return to a supported Salesforce page. The extension uses the active Salesforce session cookie; it does not accept a separate Salesforce password or API token.
Why can’t I query an object or update a field?
Lightning Connect respects the Salesforce org, user permissions, object permissions, field-level security, session state, and API limits available to the signed-in user. Confirm access in Salesforce and try again.
Where are my query history, mappings, and saved packages stored?
These workspace items are stored locally in your browser using extension storage. They are not saved as Salesforce records by the extension.
Are Local Files automatically uploaded to Salesforce?
No. Local Files are optional scratch files held in the extension cache. They are not automatically synchronized; import, export, or deploy them deliberately.
What should I do before bulk edits or metadata actions in production?
Review the staged rows or selected components carefully, validate your permissions and intended target org, and follow your organization’s change-management process. Testing in a non-production org is recommended.
Still need help?
Share enough context for a useful answer.
When opening an issue, include the workflow you were using, the Salesforce domain type, the action you attempted, and non-sensitive error details. Do not post session IDs, customer data, or credentials.