Current won time Not Equal to Previous

For Pipedrive, this automated workflow triggers on deal updates, ensuring the current won time is different from the previous. It retrieves organization details and checks for existing customers in Stripe. If no customer exists, it creates a new customer with relevant address information, streamlining the process of managing deals and customer data efficiently.

7/8/2025
7 nodes
Medium
manualmediumpipedrivetriggerpipedrivestripelogicconditionalapiintegration
Categories:
Manual TriggeredMedium WorkflowCRM & Sales
Integrations:
PipedriveTriggerPipedriveStripe

Target Audience

Target Audience


- Sales Teams: Those who manage deals in Pipedrive and want to ensure their records are up-to-date with real-time changes.
- Customer Support Teams: Professionals who need to create or update customer information based on sales activities.
- Finance Teams: Individuals who track customer payments and billing through Stripe, ensuring accurate records.
- Integrators and Developers: Users who want to automate processes between Pipedrive and Stripe, enhancing workflow efficiency.

Problem Solved

Problem Solved


This workflow addresses the issue of ensuring that when a deal's status is updated in Pipedrive, the system checks if the 'won time' has changed compared to the previous record. If the 'won time' is different, it triggers further actions to gather organization details, search for the customer in Stripe, and create a new customer entry if they do not exist. This approach minimizes data discrepancies and ensures that customer records are always current.

Workflow Steps

Workflow Steps


1. Trigger on Deal Update: The workflow starts when a deal is updated in Pipedrive.
2. Check Won Time Change: It checks if the current 'won time' is different from the previous one using a conditional node.
3. Retrieve Organization Details: If the 'won time' has changed, it fetches the organization details associated with the deal from Pipedrive.
4. Search for Customer in Stripe: The workflow then searches for the customer in Stripe using the organization's name.
5. Check Customer Existence: It checks if the customer exists in Stripe. If they do not exist, the workflow continues to the next step.
6. Merge Data: It merges the organization data with the workflow data to prepare for customer creation.
7. Create Customer in Stripe: Lastly, if the customer does not exist, it creates a new customer record in Stripe with the relevant address details.

Customization Guide

Customization Guide


- Change Trigger Conditions: Modify the conditions in the 'Current won time Not Equal to Previous' node to check for different fields or criteria based on your business needs.
- Modify Customer Search Query: Adjust the search query in the 'Search customer' node to include additional parameters or filters that suit your customer identification process.
- Update Customer Creation Fields: In the 'Create customer' node, customize the fields such as address or additional customer information as per your requirements.
- Integrate Additional Services: You can add more nodes to integrate with other services or APIs that your organization uses, expanding the functionality of this workflow.