I’m working on connecting several forms to Pipedrive through Zapier automation. The challenge I’m facing is that I have two distinct types of forms that collect completely different information from users.
I want to organize these different data sets properly in Pipedrive, but I don’t want to create separate pipelines for each form type. I’m looking for a way to handle these various form submissions while keeping everything organized in the same pipeline.
Has anyone dealt with a similar situation? What would be the best approach to manage different form data structures without creating multiple pipelines in Pipedrive?
i’ve been using tags for this exact scenario! instead of custom fields, try tagging each deal based on which form it came from. zapier can automatically add tags during the zap creation process. this way you can still filter and sort your deals easily without cluttering up your pipeline with extra fields. works great for keeping things clean while maintaning organization.
I managed a similar issue when integrating multiple form types into Pipedrive. Instead of separate pipelines, I utilized custom fields to differentiate the data collected from each form. By setting conditional fields, you can ensure that data from each form populates appropriately without cluttering your setup. In Zapier, you can configure the mappings for each form submission to direct specific data to its corresponding custom fields. Additionally, incorporating a ‘Form Type’ field allows for easier segmentation in the future, maintaining organization without the need for multiple pipelines.
What worked for me was creating a standardized deal structure with universal fields that apply to both form types, then using Zapier’s conditional logic to handle the differences. I set up my Zap to check which form triggered it, then map the relevant data to the appropriate fields while leaving others blank. The key is designing your Pipedrive deal structure upfront to accommodate both data sets. I also found it helpful to use the deal notes section to capture form-specific details that don’t fit into standard fields. This approach keeps everything in one pipeline while preserving the unique information from each form type without making things too complex.