Since Salesforce recommended to update our integration users from "System Admin" users to the Salesforce Integration user, I have been trying unsuccessfully to get our integration user to trigger Auto-Response emails via Auto-Response Rules when cases are created from Form-to-Case. While this result can be achieved via flow, I did not want to have to manage Case Auto-Response Rules in 2 places ( Flow and Auto-response Rules)
Salesforce Support's final email said that this may be an oversight in the current design of the Salesforce Integration User license and a current product limitation.
I would love to see the permission to trigger the Case Auto-Response rule extend to the Salesforce Integration license so we can use out of the box functionality and not have to build custom processes. Unfortunately I will have to keep using a regular Salesforce License user as my integration user until that is resolved.
If anyone has found a better workaround, I would love to know!
Hey Charlotte,
Web-to-Lead/Web-to-Case auto-response rules not firing when records are created via the REST API (which is likely how your Form-to-Case integration inserts records). This is actually a REST API limitation, not specifically tied to the Salesforce Integration license itself, the SOAP API has an EmailHeader option to explicitly trigger auto-response, but REST API doesn't expose an equivalent.
Two documented workarounds:
Option 1: A Workflow Rule that fires on Case creation and sends the email directly, no code needed, simplest option, but as you noted, means managing logic in two places.
Option 2: A single Apex trigger using Database.DMLOptions to explicitly re-trigger the existing Auto-Response Rules:
```apex
trigger AfterCaseInsert on Case (after insert) {
if (trigger.isAfter && trigger.isInsert) {
List<Case> newlyInsertedCases = [SELECT Id From Case WHERE Id IN :trigger.new];
Database.DMLOptions autoResponseOptions = new Database.DMLOptions();
autoResponseOptions.EmailHeader.triggerAutoResponseEmail = true;
for (Case c : newlyInsertedCases) {
Database.update(c, autoResponseOptions);
}
}
}
```
This re-updates each new Case with a DML option that explicitly triggers your existing Auto-Response Rules, so you keep managing rules in one place (Setup > Auto-Response Rules) instead of duplicating logic in Flow. This runs regardless of which user/license created the record, since it's the DML option itself that flags the update to trigger auto-response, not something dependent on the inserting user's license type.
Worth testing in a sandbox first, and for high case volume, this should be refactored to Queueable/future to avoid governor limit issues on bulk inserts.
Reference:
https://help.salesforce.com/s/articleView?id=000386731&language=en_US&type=1