3

The queue is empty, you've just exceeded your daily limit. Those emails are so that you manually input the leads if you want to. You'll get a new 500 lead limit within 24 hours.


2

You put the web to lead or case HTML generated in Salesforce on your external facing websites. Now where you place that HTML, if that’s authenticated or not totally depends how you are implementing it at your web layer. It does not have any relation with any data in Salesforce. From documentation: After enabling and setting up Web-to-Case, generate the ...


1

There are 48 Event Types which can be monitored from EventLog. Here are they, but Web-to-Lead is not tracked under this. Event types


1

I don't believe so. There are about 50 Supported Event Types that you can see here, and w2l are not explicitly called out. Since W2L records are created by the Default Lead Owner, you can set the log on for that user and get some data. Also, if you use encryption, you can encrypt custom fields using the Platform Encryption. To read up more, here is the ...


1

Salesforce doesn't allow custom lookup fields on web-to-lead forms, even as hidden fields. You could try passing the ID in a hidden text field instead and using Process Builder + Flow or an Apex trigger to populate the lookup field from this,


1

I figured it out, stupid mistake on my part I read the document wrong. I just needed to enable the web to case. Cases are coming in now and emails are being sent out!


1

Web to lead forms do not expose any Salesforce data at any time. There's also no inherent security in web to lead forms; it is up to you to decide which security measure(s) to implement, if any. However, web to lead is also not "hackable" in any real sense, because it can only consume data, not expose data. The only thing you might want to worry about is an ...


1

Reason behind that, you have defined queue and activated Web-to-Case. But, you have not configured any assignment rules where web-to-case to be assigned to WebToCase queue. Refer Assign Cases documentation It is coming to your name, may be in the Support Settings, Automated Case User is you or Default Case Owner is you. Automated Case User - The user ...


1

With your requirement, it seems you need to write a trigger on case object, and check "Case Origin". Sample trigger code would be trigger CaseTrg on Case (after Insert) { List<FeedItem> FeedItems = new List<FeedItem>(); for(Case c: trigger.new) { // don't check other stuff if the origin is Email-to-Case as it is already ...


Only top voted, non community-wiki answers of a minimum length are eligible