Hello! I am very interested in using the COQL search action that is now available for Bigin by Zoho, but after spending most of the day going back and forth through the API and Authorization and COQL Query documents, I have absolutely no idea where to start or how to get the action to do anything. All of the syntaxes I have tried in my zap have received some kind of error regarding scope or url or something and I'm at a loss. Can someone just give me a guide of how to approach this action and how to authorize it or whatever I need to do? And would that process be the same or similar for using the API request action? I also kind of tried to play with that one but was just as lost.
For one use case just to use for teaching purposes, I'm trying to set up a zap where when a bigin deal reaches a certain stage, a new draft invoice is created in zoho books. However the create invoice action for Zoho Books requires a product and the search records in bigin does not show the products associated to the deal. I would love to use one of these features to retrieve the associated products and turn them into line items to then input into the draft invoice.
Honestly any guidance with using either of these features would be greatly appreciated! Thank you for your time.
Page 1 / 1
Hi @Jordan Butler
The only documentation I could find was this Get records using COQL query guide from Bigin’s API documentation. It outlines the sort of syntax that’s expected for COQL queries.
Can you share a screenshot of the query you’re using in that Get Records Using COQL Query action, along with any errors you’re seeing? That’ll help us to better see what might be causing some trouble with it. Make sure to blur/remove any personal info (names, emails etc.) before sharing - you can use a tool like Zappy for that.
Looking forward to hearing from you!
Yeah I went through all that documentation and did the metadata and got the field names and everything. I guess the main thing I'm confused about is the scope. Where does that go? My zapier account and bigin account are already connected and should have full scope availability as far as I can remember when I set it up. But I'm not sure where in the syntax to put the scope or if it even needs to be included in the Zap? Or is that something to do with the URL and correct data center and access tokens and stuff? In which case, where does all that information go?
Ah I see, @Jordan Butler! The scopes should be handled automatically by the app connection used in the Get Records Using COQL Query action. You wouldn’t be able to add additional scopes via the Zap itself.
When you connected your Bigin account, was that before or after they added the new Get Records Using COQL Query action? I’m wondering if they may have increased the scopes requested when connecting. If that’s the case, and your previous account connection has an older set of scopes granted, that might be why it’s erroring. In which case, creating a new Bigin app account connection may do the trick.
Can you give that a try and let me know if that sorts it?
Okay you were definitely right about that, there was a new version of the connection which included the COQL, so I got the scope part figured out. However, I'm still getting errors on the zap setup. Here are some screenshots of what I'm trying now, can you help me with what is wrong in this?
When I used the API to get the field api names for the associated products module, I didn’t see any field that specified what deal it was searching (deal name or id) so I'm wondering if that is why it can’t recognize that “column”, because it doesn’t exist? There is an api field name called “parent ID” which seems promising, but when I search the pipeline record in the step above, there is no parent ID field that I could use to search by. So I'm stuck now.
@SamB any idea on how to correct my syntax here?
Sorry for the delay in replying here, @Jordan Butler! Glad to hear that creating a new Bigin account connection did the trick
That “column given seems to be invalid” error suggests that there may be an issue with one of the column field names used in the query. I wonder if the problem could be with the Layout_id field
The lowercase ‘i’ might be causing trouble, as the same field selected from the trigger shows it as Layout_Id with a capital ‘I’:
Can you try updating it to Layout_Id (with a capital ‘I’) and see if that helps?
Keep me posted on how it goes!
No that didn’t work. It’s giving me the same error. I’ve tried it with several different search fields, deal name, deal id, layout id, and also several different SELECT variations and it’s still giving me the error. While I was waiting I also tried the API request action instead to see if I could get that to work but I'm struggling with that as well. I just need the line items so I can build an invoice! Is there a better way to be doing this?? I feel like I can’t be the first person who needs line items from Bigin!!
