When Cases or Leads are created in Salesforce using a custom API integration (such as a custom web-to-case or web-to-lead implementation), the configured auto-response email rule does not trigger automatically. The Case or Lead record is created successfully, but the auto-response email is not sent to the person who submitted it — even when the Auto-Response Rule is active and correctly configured.
This is a common issue for organizations that have replaced the standard Salesforce Web-to-Case or Web-to-Lead form submission with a custom API-based integration. The standard Web-to-Case and Web-to-Lead forms automatically trigger auto-response rules. Custom API calls do not trigger them by default.
Example Scenario
Your organization has an auto-response rule that sends a confirmation email to all new case submitters. Cases are being created via a custom API integration connected to your company's website. Even though the rule is enabled and the submitter's email is populated on the Case, no confirmation email is sent. The auto-response rule never fires.
Why Auto-Response Rules Do Not Fire with API-Created Records
When Salesforce records are created via the API, auto-response email rules are not triggered by default. This is controlled by the triggerAutoResponseEmail field in the API request's EmailHeader. By default, this field is set to false for API calls, which is why auto-responses do not fire even when rules are configured and active.
How to Enable Auto-Response Rules for API-Created Cases and Leads
To enable auto-response emails when creating Cases or Leads via the Salesforce API, set the triggerAutoResponseEmail field to true in the EmailHeader of your API call.
triggerAutoResponseEmail = true in the EmailHeader of the API request.triggerAutoResponseEmail = true in the DmlOptions EmailHeader when performing the DML insert operation.Once this field is set to true, Salesforce evaluates the active auto-response rules for the created record and sends the appropriate email to the submitter, exactly as it would for a Web-to-Case or Web-to-Lead form submission.
000385323

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.