More than Salesforce web-to-lead

With Default, you keep the form already on your site: add it with Catalog forms, map its fields, and a Form Submission trigger starts a workflow whose Create Record node makes the Salesforce lead. Salesforce's own Web-to-Lead setup generates an HTML form that posts each submission to Salesforce.

Web-to-lead turns website form fills into Salesforce leads, and Default does it with a workflow: the Pixel captures the submit, Match Record checks for an existing lead or contact, and Create Record makes the lead with an owner. Salesforce's built-in Web-to-Lead feature creates a lead from each submission of a form it generates.

Default creates form leads with a workflow's Create Record node, which calls the Salesforce REST API, so those calls count toward your org's API request limits. Salesforce's own Web-to-Lead accepts up to 500 requests in 24 hours and holds the overflow in a pending queue.

In a Default workflow, a Rules of Engagement or Round-Robin node picks the owner and Create Record writes it as the Owner ID on the new lead. On leads from Salesforce's own Web-to-Lead forms, the active lead assignment rule picks the owner.

Add the Pardot form in Default with Catalog forms, and have your page send each submission with the Forms SDK's submitForm(), since the Pixel skips Pardot submissions. The workflow then routes the lead and can open the rep's calendar, and your submit handler keeps sending the submission to Pardot, because Default doesn't forward it.

The Default Pixel sends the email when the visitor leaves the email field, so Default can start the Salesforce lookup and enrichment early. Workflows start only on submit, so an unfinished form creates no lead and shows no calendar.