Atlas B7oxwnqthoOutboundSync Help CenterEmail SupporticonLog Inicon
Help Center›Salesforce›How to bypass validation rules in Salesforce
Table of contents
  • Overview
  • Asking an admin
  • Recommended: Custom permission
  • Use case
  • Steps
  • Example
  • Alternative: Bypass by User Id
  • Use case
  • Steps
  • Finding the owner User Id
  • Testing and rollback
    • Related articles

    How to bypass validation rules in Salesforce

    Last updated December 30, 2025

    Overview

    A short how‑to for exempting the OutboundSync webhook owner from an Account validation rule (so API-created records from the webhook won’t be blocked when a required field is missing).

    This is designed for Account validation rules that must remain enforced for human users but should be bypassed for the OutboundSync integration user account that owns the webhook connection.

    Asking an admin

    This guide is written for Salesforce System Administrators. If that's you, skip ahead.

    If that's not you, but need help from your Salesforce admin implementing this, here's an example message you can send them:

    Hi System Administrator, Please exempt the OutboundSync webhook owner from the Account validation that requires [Industry / Billing Address]. For context, here's an article explaining what I'm trying to do:  https://help.outboundsync.com/articles/564774-bypass-validation-rules-when-syncing-to-salesforce  Either grant the user the Bypass_Account_Validations custom permission, or update the validation rule to skip this user id: 005XXXXXXXXXXXX. Once done, please validate with a test webhook payload. Here's how can test this with OutboundSync:  https://help.outboundsync.com/articles/668119-sending-test-webhook-payloads 

    Feel free to adapt this as-needed.

    Use case

    This approach is scalable and audit-friendly: create a Custom Permission, add it to a Permission Set, assign it to the webhook owner user, and update the validation rule to skip users with the permission. You can easily grant/revoke the bypass without editing formulas. Especially useful if you have multiple integration users.

    Steps

    1. Setup → Custom Permissions → New
    • Label: Bypass Account Validations
    • Name: Bypass_Account_Validations
    1. Setup → Permission Sets → New (e.g., Automation - Validation Bypass) → Save
    2. In the Permission Set: Custom Permissions → Add → select Bypass Account Validations → Save
    3. Assign the Permission Set to the OutboundSync webhook owner user
    4. Update the Account validation rule formula to include the permission check.

    Example

    In the example below, the Industry field is bypassed:

    AND( ISBLANK(TEXT(Industry)),      /* or ISPICKVAL(Industry, '') depending on your field */
  NOT($Permission.Bypass_Account_Validations)
)

    Alternative: Bypass by User Id

    Use case

    Use this when you only need to exempt a single known user and want a minimal change.

    Steps

    1. Find the webhook owner User Id (see below).
    2. Edit the validation rule formula to skip that Id. Example (Billing Address required except webhook owner):
    AND( OR(
    ISBLANK(BillingStreet),
    ISBLANK(BillingCity),
    ISBLANK(BillingState),
    ISBLANK(BillingPostalCode),
    ISBLANK(BillingCountry)
  ),
  $User.Id <> "005XXXXXXXXXXXX"  /* replace with webhook owner Id */
)
    💡

    Replace the 005... with the actual User Id (15- or 18-char).

    Finding the owner User Id

    1. In Salesforce: Setup → Users → Users.
    2. Locate the user (by Name, Email, or Username) that OutboundSync uses as the webhook owner.
    3. Click the user record and copy the Id from the URL. Example Lightning URL: /lightning/r/User/0053j00000A1b2C/view → Id is 0053j00000A1b2C.
    💡

    If you don’t know which Salesforce user is the webhook owner: check OutboundSync’s webhook configuration in OutboundSync (the connector settings typically show the connected user) or ask your OutboundSync admin, the connected user is the owner to exempt.

    Testing and rollback

    1. After changing the rule, run a test sync with a sample payload that would previously fail (missing Industry or Billing fields).
    2. Confirm the Account is created and subsequent Contact/activity inserts complete.
    3. If something goes wrong, revert the validation rule to its previous formula or remove the permission set assignment.

    Was this article helpful?