Creating a Salesforce lead
An enquiry becomes a lead in your Salesforce organisation.
This is written and tested against our own rules, but it has never exchanged a single request with the real Salesforce service. Treat it as ready to connect, not as proven.
What it is for
Sales teams work the lead list. A form that does not reach the lead list does not get worked.
When a person copies enquiries into the lead list by hand, some of them never make it.
Last name and company are required; email and phone come along if you collected them.
What you need
An access token and your organisation's host, both saved in Project secrets. With only one of the two, nothing starts.
The host is the one that ends in my.salesforce.com. Anything else is refused. It differs per organisation — it is the name in your address bar when you are signed in.
The order to do it in
Confirm your host and token in Salesforce first, then save both, then connect the form.
Ask for the last name and the company on the form. Without them the lead cannot be created.
How to check it worked
Submit one enquiry and find the lead in Salesforce. Only the lead id comes back to the app.
Salesforce reports success in the body, so we read that rather than trusting the status alone.
Sending the same enquiry twice with the same key does not create two leads.
What it will not do
- Only one host family is allowed. A saved value cannot redirect requests somewhere else.
- Leads only. Accounts, opportunities and cases are not created from here.
- Names and company are capped at 100 characters.
- Up to 2,000 calls per project per day across Slack, Notion, HubSpot and Salesforce together.
- It writes. It does not read your Salesforce records back into the app.