Objective: Integrate ServiceM8 and Pipedrive for Job and Client Management
- Monitor ServiceM8 for New Jobs:
- Regularly check ServiceM8 for any new job entries.
- Verify Against Pipedrive Records:
- For each new job in ServiceM8, search Pipedrive to confirm if:
- The job already exists (using the ServiceM8 job number).
- The client is already in Pipedrive.
- Client Management in Pipedrive:
- If it’s a new client, create a new customer record in Pipedrive.
- Ensure the client’s details include:
- First Name, Last Name
- Address (Note: This may differ from the job address)
- Email, Phone, Mobile
- Label as ‘customer’
- Marketing status set to ‘Subscribed’
- Job/Deal Creation in Pipedrive:
- If it’s a new job, create a new deal in the ‘Pest Control’ pipeline, under the ‘New Job’ stage.
- Capture the following job details from ServiceM8:
- Job Address
- ServiceM8 Job Number
- Job Category (to be used as the Deal Title)
- Job Value (Invoice Total)
- Job Completion Date
- Scheduled Job Date
- Job Notes
- Avoiding Duplicates:
- Ensure no duplicate records are created. If a record already exists, update it instead.
- Handling Multiple Jobs for a Single Customer:
- Since a customer may have multiple jobs, always search for the customer first.
- Then, search for the deal using the ServiceM8 job number as the key identifier.
Current Problem: Data Inconsistency and Misalignment
- Issue Description:
- We are encountering a problem where data is getting mixed up during the integration process.
- Specifically, the system is not correctly pulling through individual records. Instead, it seems to be aggregating or confusing data from different entries.
- Another critical issue is that the data integration is using the job owner’s details instead of the actual customer’s details.
Welcome to the Make community!
1. Screenshots of module fields and filters
Please share screenshots of relevant module fields and filters in question? It would really help other community members to see what you’re looking at.
You can upload images here using the Upload icon in the text editor:
2. Scenario blueprint
Please export the scenario blueprint file to allow others to view the mappings and settings. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
(Note: Exporting your scenario will not include private information or keys to your connections)
Uploading it here will look like this:
blueprint.json (12.3 KB)
3. And most importantly, Output bundles
Please provide the output bundles of the modules by running the scenario, then click the white speech bubble on the top-right of each module, save the bundle contents in your text editor as a bundle.txt file, and upload it here into this discussion thread.
Providing the output bundles will allow others to replicate what is going on in the scenario even if they do not use the external service.
Following these steps will allow others to assist you here. Thanks!
2 Likes
Hi Ray. Welcome to the Community!
Make should be a perfect solution for your use-case, but from the description of your scenario and the problems you’re getting, it looks like there is some misconfiguration within the scenario.
Although you’ve provided some background, as @samliew suggested we’d need a lot more detail on how you’ve configured each module and filter.
As this scenario has a lot of steps, that could take some time to get to the bottom of through this Community.
If time is of the essence, you might want to consider enlisting the help of a local Make Service Partner. There will almost certainly be a fee, but you’d get to the solution much more quickly.
All Silver and Gold tier partners are required to have staff who have passed our technical certification exams. Gold tier partners are also required to have staff who have gained expert certification.
Take a look at our Service Partner directory and select your location. I’m sure you’ll be able to find someone who can help!
3 Likes
