[BIGIN by Zoho CRM] Move Contact from one pipeline to the other

How To
1

Hello. I’m creating an automation in which a contact has to be moved from one pipeline to the other in Bigin.

I’ve tried all the possible ways, still I cannot manage to understand how to do so. I try with the module “Search Pipeline”, but it cannot find the name of the contact, and therefore I cannot manage to update it.

Is there anyone who can help me in this? Thanks!

2

Hello everyone,

I’m posting an update and the solution to the problem I was facing. After some more digging and experimenting with the API, I managed to figure it out, and I hope this explanation helps anyone else who runs into the same issue.

The correct workflow involves using the contact information to find the associated deal, and then updating that deal.

Here is the step-by-step logic that I implemented in my scenario, which now works perfectly:

  1. Find the Contact: The first step in the Bigin part of my workflow is to find the correct contact. I use the “Search Contacts” module. I take the phone number from my Airtable trigger, parse it into the standard E.164 format, and use that to search for the contact in Bigin. This step gives me the unique Contact ID.

  2. Find the Associated Deal (The “Aha!” Moment): This was the crucial part I was missing. Instead of trying to update the contact, I needed to find the Deal that was linked to them. I used the “Make an API Call” module to perform a custom search.

    • Method: GET

    • URL: I used the search endpoint for deals: /v2/Pipelines/search

    • Query String: I set a search criterion to find the deal where the Contact_Name field in the Deal module exactly matches the Contact ID I got from the “Search Contacts” step. This successfully finds the specific deal for that contact.

  3. Update the Deal’s Stage: Now that my scenario had successfully found the Deal ID from the previous API call, I could finally update it. I used another “Make an API Call” module to do this.

    • Method: PUT

    • URL: The URL for this call points directly to the deal I want to update: /v2/Pipelines/{{Deal ID from the previous step}}

    • Body: In the request body, I sent the data I wanted to change. In my case, I updated the Stage to “Booked Tryout lesson,” set the Closing_Date, and updated the deal Amount. This action is what effectively “moves” the deal to the desired stage in the pipeline.

The scenario I uploaded demonstrates this exact working logic. The flow searches for the contact, uses the contact’s ID to find the deal, and then updates that deal.

I hope this helps :slight_smile:

2 Likes