This topic was automatically generated from Slack. You can find the original thread here.
Hello , In a Pipedream workflow integrated with Close CRM, the Find Lead step successfully locates an existing lead based on the provided search criteria (e.g., Company Name). However, when the workflow proceeds to the Update Lead step using the Lead ID returned from the Find Lead step, Close does not update the existing lead. Instead, a new lead is created.
It sounds like you’re experiencing an issue where, after finding a lead in Close CRM using the Find Lead step, your workflow attempts to update that lead, but instead of updating, a new lead is created. This is not the expected behavior—using the Update Lead action with a valid Lead ID should update the existing lead, not create a new one. Let’s walk through some possible causes and solutions: — ## Common Causes and Solutions ### 1. Double-Check the Lead ID Passed to Update Lead - Ensure that the Lead ID output from the Find Lead step is being correctly mapped to the Update Lead step. - In the Update Lead action, the Lead ID field should reference the Lead ID from the previous step, e.g., ${steps.find_lead.$return_value.id} or similar. ### 2. Review the Update Lead Action Configuration - If you accidentally provide a new name or other required fields in a way that triggers lead creation (instead of update), or if the Lead ID is missing/incorrect, Close may interpret the request as a “create” instead of “update.” - Make sure you are not passing a blank or incorrect Lead ID. ### 3. Avoid Using the Create Lead Action - Only use the Update Lead action after finding the lead. If you use Create Lead with the same data, it will always create a new lead. ### 4. Confirm the Workflow Logic - The typical workflow should look like: 1. Find Lead (returns Lead ID) 2. Update Lead (uses Lead ID from previous step) - If you have conditional logic that falls back to Create Lead if a lead isn’t found, ensure that the condition is working as expected. — ## How to Use the Update Lead Action According to the Update Lead action documentation: 1. Search for the Close app from the step menu. 2. Select the Update Lead action. 3. Connect your Close account. 4. Select a Lead ID or pass a string from a previous step. 5. At the bottom of the step, click Test to run the action and test the configuration. — ## Troubleshooting Steps 1. Check the Data Passed: In the Update Lead step, confirm that the Lead ID field is mapped to the ID returned by the Find Lead step. 2. Inspect the Output: After running the workflow, inspect the output of both steps to ensure the correct Lead ID is being passed. 3. Remove Optional Fields: Try updating only one field (e.g., the name) to see if the issue persists. 4. Check for Duplicates: If your workflow logic includes both Create and Update actions, make sure the Create action is not being triggered unintentionally. — ## If the Issue Persists If you’ve checked all of the above and still see new leads being created instead of updates, this may be a bug or a misconfiguration in your workflow. Please reach out to Pipedream support for further help: Support - Pipedream — Summary: - Make sure the Update Lead action is receiving the correct Lead ID from the Find Lead step. - Double-check your workflow logic to ensure only the Update Lead action is triggered for existing leads. - If issues continue, contact Pipedream Support for assistance.
Is it happened because i am only using free version, no started with paid plan and hasn’t deploy my project?
You should visit Pricing - Pipedream for the latest pricing, but I’ll do my best to answer. No, the issue you described—where a new lead is created instead of updating an existing lead in Close CRM—is not caused by using the Free plan, not being on a paid plan, or not deploying your project. On the Free plan, you can use workflows, connect to apps like Close, and run/test your workflows (within daily credit and usage limits). There are some feature and usage restrictions, but basic workflow functionality—including updating records in connected apps—should work the same as on paid plans. Common causes for your issue are: - The Lead ID is not being passed correctly to the Update Lead step. - The Update Lead step is misconfigured (e.g., missing or incorrect Lead ID). - The workflow logic is triggering a Create Lead action instead of Update Lead. Next steps: - Double-check your workflow configuration to ensure the correct Lead ID is being used in the Update Lead step. - Make sure you are not accidentally using a Create Lead action. - If you continue to have issues, you can get more help at Support - Pipedream. Your plan type does not affect this specific workflow behavior.