docs(salesforce): add Create+Update two-step workaround for bypassing assignment rules on new records - #2394
Merged
Conversation
…t rules on Create Record
Contributor
george-dilthey
marked this pull request as ready for review
August 28, 2026 18:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a two-step Create Record + Update Record workaround to
docs/salesforce-integration-faqs.mdin the "Why is the owner on a new Salesforce lead or contact set to the Clay integration user?" section. The existing Note already correctly stated that Create Record has no built-in option to suppress assignment rules, but was missing the Clay-side workaround: create the record (assignment rules fire), then immediately update it with Disable auto-assignment rules enabled and Owner ID mapped — which reassigns to the intended owner without triggering rules a second time.Why
An enterprise customer (DigitalOcean) asked in Intercom conversation #215475688398993 why the "bypass auto-assignment rules" option was absent from the Create Record UI when creating Salesforce leads. Support engineer Peter Johnston confirmed the toggle has never existed in Create Record (only in Update Record), then provided the two-step workaround. Fin couldn't resolve this independently because the docs didn't document the Clay-side workaround for when assignment rules fire on all new records regardless of owner.
Source link(s)
disableAutoAssignmentRulesconfirmed in Update Record (/workspace/public-actions/apps/salesforce-new-ui/actions/update-object/input-parameter-schema.ts:130-140); absent from Create Record (/workspace/public-actions/apps/salesforce-new-ui/actions/create-object/input-parameter-schema.ts:74). No gating. Feature is live for all customers.Uncertainties
None. All claims verified by the Docsbot Verifier sub-agent (PASS). The two-step workaround uses two already-documented, fully-shipped features.
Related observations
Six other open PRs also touch
salesforce-integration-faqs.md(#2369, #2344, #2329, #2304, #2268, #2241), but none of them modify the "Why is the owner on a new Salesforce lead or contact set to the Clay integration user?" section. Reviewer should confirm there are no merge conflicts with those PRs at merge time.Closes DOC-2165