> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/salesforce-package.md). # Salesforce package and trigger readiness Use this guide when your Salesforce setup shows a package or trigger-readiness check. ## Before installing Confirm the target Salesforce organization, the Distro workspace and the connected user's permissions. Use the install URL supplied by Distro when the deployment provides one. Ask Distro support if the setup screen does not provide a package URL. Read the package version and installation permissions in Salesforce before accepting the installation. Keep your Salesforce admin involved when changing organization-wide configuration. ## Check readiness Return to Distro and run the available package-readiness checks. These checks inspect the installed setup; a successful read does not perform a test write or enroll a Salesforce record into a workflow. Next, configure the workflow's Salesforce source, object, conditions and mapped fields. Publish the workflow and confirm it is On and live execution is available. ## Test a trigger Make a controlled change to a test record that matches the source. Allow for polling, then inspect the resulting workflow run and source values. Optional CDC acts as a wake-up for polling. Configure CDC in Salesforce deliberately when instructed; Distro does not automatically turn it on for all objects. If there is no run, distinguish authorization, package readiness, trigger conditions, polling delay and workspace activation. See [Workflow triggers](/workflows/triggers.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/salesforce-package.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.