Slack Export

To set up a **Zapier** integration that sends data from **Law Ruler CRM** to Salesforce's **Web-to-Lead** endpoint, follow these detailed steps: Step-by-Step Instructions: Step 1: Create a New Zap

Log in to your **Zapier** account.
Click **Create Zap** in the top-right corner.
Select the **Trigger** app, which will be **Law Ruler CRM** in your case. Step 2: Set Up the Trigger
Search for **Law Ruler CRM** and select it.
Choose a trigger event, such as **New Lead** or **New Contact**, depending on what you want to send to Salesforce.
Click **Continue**.
Connect your **Law Ruler CRM** account by entering your credentials, if this is the first time setting it up.
Once connected, select the appropriate trigger you need (e.g., New Lead).
Test the trigger to ensure Zapier pulls in data correctly. This will allow you to map data to Salesforce later. Step 3: Add the Webhooks by Zapier Action
Click **+ Add Action**.
In the action search bar, type **Webhooks by Zapier** and select it.
Choose the action event **POST** since you will be sending data via an HTTP POST request.
Click **Continue**. Step 4: Set Up Webhooks POST to Salesforce Web-to-Lead
**URL**: In the URL field, enter the Salesforce **Web-to-Lead** endpoint URL. For your setup, it would be:
arduino
https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8
**Payload Type**: Choose Form as the payload type, because Salesforce expects data in x-www-form-urlencoded format.
**Data**: In the **Data** section, map the fields from **Law Ruler CRM** to the corresponding Salesforce Web-to-Lead fields: • Example data mapping: • makefile • • • oid = 00Df4000004kL57 • firstname = {{Law Ruler CRM Field for First Name}} • lastname = {{Law Ruler CRM Field for Last Name}} • email = {{Law Ruler CRM Field for Email}} ◦ company = {{Law Ruler CRM Field for Company}} ◦ The oid is the unique Salesforce organization ID that ties the data to your specific Salesforce instance. Replace it with your actual Org ID. ◦ You can map as many fields as needed for your lead submission based on the available fields in your CRM and Salesforce's Web-to-Lead configuration.
**Headers**: Set the following header to ensure proper data formatting:
bash
Content-Type: application/x-www-form-urlencoded Step 5: Test the Zap
Click **Test & Continue** to send a test request from **Law Ruler CRM** to the Salesforce Web-to-Lead endpoint.
Go into Salesforce and check your Leads object to verify that the lead has been created. Step 6: Turn on the Zap
Once testing is successful, turn on the Zap to make sure it runs every time a new lead is created in **Law Ruler CRM**. Additional Notes: • **Mapping Fields**: Ensure that all fields you map from **Law Ruler CRM** match Salesforce's expected field names for Web-to-Lead (e.g., first_name, last_name, email, etc.). You can adjust the Web-to-Lead settings in Salesforce if needed to accommodate additional fields. • **OID (Organization ID)**: This is essential for the lead data to be routed to the correct Salesforce instance. You can find this under **Setup** → **Company Information** in Salesforce. • **Error Handling**: If something goes wrong, Zapier will provide an error log in the task history. Check for any mismatches in field names or payload formatting. This process allows you to automatically post new leads or contacts from **Law Ruler CRM** directly into Salesforce using the Web-to-Lead functionality via Zapier's Webhooks action.

Darrell (darrell@shield-legal.com)

2024-09-09 12:31:07

apparently thats to zap

👍:skin_tone_5: Dwight Thomas

Dwight Thomas (dwight@shield-legal.com)

2024-09-11 11:07:24

Failed with error: 'Test connection failed. Details: Test connection has failed. Please check connector documentation and verify that your Salesforce instance meets connector limitations. clientRequestId: e1cf721e-7a6a-a891-70d2-d0ca38b97fa4'. Please sign in again.

Darrell (darrell@shield-legal.com)

2024-09-11 11:13:14

https://learn.microsoft.com/en-us/connectors/salesforce/

learn.microsoft.com

Salesforce - Connectors

Original URL: https://learn.microsoft.com/en-us/connectors/salesforce/

Dwight Thomas (dwight@shield-legal.com)

2024-09-11 15:26:18

Darrell (darrell@shield-legal.com)

2024-09-11 15:31:17

image.png

Darrell (darrell@shield-legal.com)

2024-09-11 15:57:25

image.png

Dwight Thomas (dwight@shield-legal.com)

2024-09-11 15:58:29

Salesforce Test Account Credentials

Darrell (darrell@shield-legal.com)

2024-09-11 16:10:51

should be ready to test when you are

Dwight Thomas (dwight@shield-legal.com)

2024-09-11 16:31:11

{ "error": { "code": 400, "message": "API path is not valid. Please refer https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm.", "source": "flow-apim-unitedstates-002-westus-01.azure-apim.net", "path": "choose[5]\when[1]", "policyId": "", "clientRequestId": "bed9ea13-3cb7-4ef7-805b-140ef5d97b32", "dreeSet": "true" } }

developer.salesforce.com

Reference | REST API Developer Guide | Salesforce Developers

The following table lists supported REST resources in the API and provides a brief description for each.

Original URL: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm

Darrell (darrell@shield-legal.com)

2024-09-11 16:40:21

API version 58

Darrell (darrell@shield-legal.com)

2024-09-11 16:43:39

so would look like this...

/services/data/v58.0/sobjects/Lead/

Darrell (darrell@shield-legal.com)

2024-09-11 16:49:42

{ "LastName": "Doe", "Company": "Acme Corp" }

is a good minimum test

Dwight Thomas (dwight@shield-legal.com)

2024-09-11 16:51:55

00Df4000004kL57

Darrell (darrell@shield-legal.com)

2024-09-11 16:58:03

https://dooganmarshawn-dev-ed.salesforce.com/services/data/v58.0/sobjects/Lead/

Darrell (darrell@shield-legal.com)

2024-09-11 17:02:26

Consumer Key3MVG95jctIhbyCpqAnrBNa721.oUx2o.cUU5Xu7r42vPTw2dd3z2Bn6Z_T5VvXFgX8nYSyOYExDIr5V7pbtcI Consumer Secret6E667A12D50685B7C5C38AD536BAD6DC1B714AAF7CF93D54FAF413B69964F606

Darrell (darrell@shield-legal.com)

2024-09-11 17:02:39

key on top secret on bottom

Darrell (darrell@shield-legal.com)

2024-09-16 18:07:29

an http request should work as well but do you know why power automate gives me an error here?

Screenshot 2024-09-16 at 4.05.47 PM.png

Darrell (darrell@shield-legal.com)

2024-09-16 18:30:36

Actually ... Good news! I just got it to successfully send David a test. Here's the body I sent him.

firstname=ShieldLegal&lastname=Test&email=ShieldLegalTest@example.com&street=123+Main+St&city=San+Francisco

I didn't email him to ask. 9/16/2024, 4:25:40 PM (Local time) 9/16/2024, 4:25:40 PM (Local time) Succeeded Client Tracking - 08584750777449408419888068473CU112 Action tracking ID - a4250db4-42e2-422b-8ad5-b353b790557e

👏:skin_tone_5: Dwight Thomas

Darrell (darrell@shield-legal.com)

2024-09-16 18:32:30

Here's the code.

{ "type": "Http", "inputs": { "uri": "https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8&orgId=00Df4000004kL57", "method": "POST", "headers": { "Content-Type: ": "application/x-www-form-urlencoded" }, "body": "firstname=ShieldLegal&lastname=Test&email=ShieldLegalTest@example.com&street=123+Main+St&city=San+Francisco\n" }, "runAfter": {}, "runtimeConfiguration": { "contentTransfer": { "transferMode": "Chunked" } } }

Dwight Thomas (dwight@shield-legal.com)

2024-09-16 19:11:28

That is absolutely awesome. Tomorrow will have to take a look at it together.