You can use the HTTP Integration to integrate to a variety of API Endpoints. An example of where you can do is with the Salesforce Web-to-Lead endpoint.
If you are unable to integrate directly into a Salesforce instance using the direct Integrate to Salesforce job, then you may be able to do this using HTTP Integration.
While the integration mentioned above is the best way to submit leads into Salesforce securely and provides more transparency on a lead's status when being submitted, you may need to use the HTTP integration for the following reasons:
- Your client is unable to provide you access to the Salesforce instance required for direct integration
- Your client has provided you with a web-to-lead endpoint to submit to, which cannot be achieved with the direct integrations
In general, you will be able to tell which integration you need by the data you've been provided:
- Username, Password, Security Token, Client ID, Client Secret: Direct
- Organisation ID: HTTP Integration
Below we will go through how to set up the HTTP Integration.
- HTML Field Names
- Organisation ID (oid)
1. Within your HTTP Integration configuration, you need to input your API URL at the very top.
For Salesforce, the API URL is always the same:
Also ensure that your method is set to 'post'.
2. The next area you need to populate is the mapping section. The first field you should map is the Organisation ID.
On a Web-to-Lead endpoint, their field name is oid. You will need to add this to the mapping as below:
You can then add your usual field mappings directly underneath these two using the HTML field names.
After completion, your integration should resemble the below:
This will complete your HTTP Integration to a Salesforce instance! Please ensure to test and confirm with your client before beginning delivery through this integration.
For more information on how you can use the HTTP Integration, see here.