Hi all,
I need to some expertise and recommendations on setting up a DEV to PROD environment for Pipedrive.
We are currently running a highly customized Pipedrive integration via the no-/low-code tool MAKE with a single PROD environment. This presents a significant risk since any change made in MAKE could potentially break the live system.
To mitigate this risk, I am exploring a DEV-PROD approach to introduce structured testing and ensure a more scalable and robust setup.
Let me give an overview of the situation:
The Deal Flow
- A deal is received via an external API.
- The deal is matched against existing deals using fuzzy name matching and additional properties such as ZIP code.
- Based on the matching outcome, custom notes are generated and stored in a designated custom field.
- The deal is enriched with additional data, such as closing probability, derived from a more sophisticated analysis.
- The enriched deal is then pushed to Pipedrive.
Since this process involves continuous enhancements (e.g., adding new fields, refining matching logic), we need a stable and testable setup.
Ideation with Google Cloud Platform (GCP)
I am considering a Google Cloud-based DEV/TEST and PROD setup while keeping Pipedrive as our CRM. The plan includes:
- DEV/TEST Project
- Define custom configurations for Pipedrive (custom fields, API setup, etc.).
- Implement logic using Google Cloud Functions, Pub/Sub, and BigQuery.
- Test with a sandbox Pipedrive instance.
- CI/CD Pipeline
- Ensure structured testing and controlled deployments.
- Push updates from DEV/TEST to PROD, which interacts with the live Pipedrive instance.
My main questions are the following:
- Has someone experience with similar DEV-PROD approach for Pipedrive?
- Would you recommend the Google Cloud approach, or do you think we should continue using MAKE?
- If there were no toolset limitations, what would be the ideal setup?
I would love to learn from you and get some more ideas 